Figure 10.54. Viewing aggregate test results
For this to work correctly, you need to ensure that you have configured fingerprinting for the binary
files you use at each stage. Jenkins will only aggregate downstream test results from builds containing
an artifact with the same fingerprint.
10.7.5. Build Pipelines
The final plugin we will be looking at in this section is the Build Pipeline plugin. The Build Pipelines
plugin takes the idea of build promotion further, and helps you design and monitor deployment pipelines.
A deployment pipeline is a way of orchestrating your build through a series of quality gates, with
automated or manual approval processes at each stage, culminating with deployment into production.
The Build Pipeline plugin provides an alternative way to define downstream build jobs. A build pipeline,
unlike conventional downstream dependencies, is considered to be a linear process, a series of build
jobs executed in sequence.
To use this plugin, start by configuring the downstream build jobs for each build job in the pipeline,
using the “Build other projects” field just as you would normally do. The Build Pipelines plugin uses
the standard upstream and downstream build configurations, and for automatic steps this is all you need
to do. However the Build Pipeline plugin also supports manual build steps, where a user has to manually
approve the next step. For manual steps, you also need to configure In the Post-build Actions of
your upstream build job: just tick the “Build Pipeline Plugin -> Specify Downstream Project” box, select