You can also use the “Promotion Status” menu entry (or click on the colored star in the build history)
to view the details of a particular build promotion, and even to rerun a promotion manually (see
Figure 10.45, “Viewing the details of a build promotion”). Any build promotion can be triggered
manually, by clicking on “Force promotion” (if this build job has never been promoted) or “Re-execute
promotion” (if it has).
10.7.4. Aggregating Test Results
When distributing different types of tests across different build jobs, it is easy to loose a global vision
about the overall test results. Test results are scattered among the various build jobs, without a central
place to see the total number of executed and failing tests.
A good way to avoid this problem is to use the Aggregated Test Results feature of Jenkins. This will
retrieve any test results recorded in the downstream jobs, and aggregate them in the upstream build job.
You can configure this in the initial (upstream) build job by ticking the “Aggregate downstream test
results” option (see Figure 10.53, “Reporting on aggregate test results”).
Figure 10.53. Reporting on aggregate test results
The aggregate test results can be seen in the build details page (see Figure 10.54, “Viewing aggregate
test results”). Unfortunately, these aggregate test results do not appear in the overall test results, but you
can display the full list of tests executed by clicking on the Aggregate Test Result link on the individual
build page.