Jenkins - pass parameters to downstream

Posted:   August 14, 2018

Edited:   August 10, 2018

Status:   Completed

Tags :   Python

Categories :   Python

Were equations, pictures or diagrams not properly rendered, please refresh the page. If the problem persists, you can contact me.


After Jenkins is upgraded from 1.0 to 2.0, our master job stops to pass parameter values to its downstream jobs.

When in Jenkins 1.0, we have a master-slave job definitions, where a BUILD_PATH parameter is defined in master job, and its value will be passed directly to the slaves at runtime. On the slave machines, no additional work is needed except referencing it in the build steps, e.g. %BUILD_PATH % a windows batch command step.

But this stopped working in Jenkins 2.0


In Jenkins 2.0, with Parameterized Trigger plugin, when you want to pass a parameter to downstream,

* YOU MUST DEFINE THE PARAMETER IN DOWNSTREAM JOBS VIA “This project is parameterized”. For example, if job1 passes ABC=123 to job2 then in job2 mark the job as “This project is parameterized” and “Add Parameter” named “ABC”. ***

So modification is needed on the downstream jobs as well.


Two places to take care and be modified:

  • On the master job,
    • define the parameter in the Parameterized section
    • Add “Current Build Parameter” in the Trigger Build Step section
  • On the slave job, add a parameter with the same name as the one on master job

Now it should ok to go.


Be the first one to comment on this page!
You can use extended GitHub flavored markdown in your comment. Commenting FAQs & Guidelines