This plugin lets you trigger new builds when your build has completed, with various ways of specifying parameters for the new build.
There is also a Parameterized Remote Trigger Plugin in case you want to trigger a build on a different/remote Jenkins Master.
The parameters section can contain a combination of one or more of the following:
The parameter section is itself pluggable, and other plugins can contribute other sources of parameters.
This triggering mechanism can be used both as a post-build step or as a build step, in which case you can also block for the completion of the triggered builds. This lets you create a "function call" like semantics.
When using the "Trigger/Call builds on another project" item.
Env variables for future build steps
Please submit bugs and feature requests to the issue tracker and not (only) in the comments.
When using the trigger parameterized build as a post build task for a matrix job the triggering will be be done
Environment variables that should be available are the the default shell ones (<yourserver:port>/env-vars.html) and ones defined as Parameters.
When using the trigger parameterized build as a buildstep it will be called for every different configuration, so if triggering another project with no parameters it will be done the same number of times as you have configurations, possible causing the triggered job to run more than once.
However this also allows you to trigger other jobs with parameters relating to the current configuration, i.e. triggering a build on the same node with the same JDK.
Major refactoring. Now supports any combination of projects to build, result condition and set of parameter sources.
Should be backward compatible for configuration, except the 'batch condition' which was removed.
Skip to end of metadata Go to start of metadata