Once you install this plugin, you will find the option of “Triggering parameterized builds on other
projects” in your build job configuration page (see Figure 10.16, “Adding a parameterized trigger to a
build job”). This lets you start another build job in a number of ways. In particular, it lets you kick off
a subsequent build job, passing the current parameters to this new build job, which is impossible to do
with a normal triggered build. The best way to see how this works is through an example.
In Figure 10.15, “Jenkins stores what parameter values where used for each build” we have an initial
build job. This build job takes a single parameter, DATABASE, which specifies the database to be used
for the tests. As we have seen, the user will be prompted to enter this value whenever the build is started.
Figure 10.15. Jenkins stores what parameter values where used for each build
Now suppose we want to trigger a second build job to run more comprehensive integration tests once
this first build job has finished. However we need it to run the tests against the same database. We can
do this by setting up a parameterized trigger to start this second build job (see Figure 10.16, “Adding
a parameterized trigger to a build job”).
Figure 10.16. Adding a parameterized trigger to a build job