Jenkins - passing variables between jobs

Question

I have two jobs in jenkins  both of which need the same parameter    How can I run the first job with a parameter so that when it triggers the second job  the same parameter is used

User · Answer

for fellow googlers   If you are building a serious pipeline with the Build Flow Plugin  you can pass parameters between jobs with the DSL like this    Supposing an available string parameter  CVS TAG   in order to pass it to other jobs    build  pipeline begin   CVS TAG  params  CVS TAG    parallel         will be scheduled in parallel       build  pipeline static analysis   CVS TAG  params  CVS TAG            build  pipeline nonreg   CVS TAG  params  CVS TAG           will be triggered after previous jobs complete build  pipeline end   CVS TAG  params  CVS TAG      Hint for displaying available variables   params       output values out println  ------------------------------------  out println  Triggered Parameters Map   out println params out println  ------------------------------------  out println  Build Object Properties   build properties each   out println   it key - gt   it value    out println  ------------------------------------

User · Answer

Just add my answer in addition to Nigel Kirby s as I can t comment yet   In order to pass a dynamically created parameter  you can also export the variable in  Execute Shell  tile and then pass it through  Trigger parameterized build on other projects      Predefined parameters     give   YOUR VAR  YOUR VAR   My team use this feature to pass npm package version from build job to deployment jobs  UPDATE  above only works for Jenkins injected parameters  parameter created from shell still need to use same method  eg   echo YOUR VAR   YOUR VAR    variable properties and pass that file downstream

User · Answer

Reading through the answers  I don t see another option that I like so will offer it as well   I love the parameterization of jobs  but it doesn t always scale well   If you have jobs which are not directly downstream of the first job but farther down the pipeline  you don t really want to parameterize every job in the pipeline so as to be able to pass the parameters all the way through   Or if you have a large number of parameters used by a variety of other jobs  especially those not necessarily tied to one parent or master job   again parameterization doesn t work   In these cases  I favor outputting the values to a properties file and then injecting that in whatever job I need using the EnvInject plugin   This can be done dynamically  which is another way to solve the issue from another answer above where parameterized jobs were still used   This solution scales very well in many scenarios

User · Answer

You can use Hudson Groovy builder to do this   First Job in pipeline    Second job in pipeline

User · Answer

1 Post-Build Actions   Select    Trigger parameterized build on other projects     2 Enter the environment variable with value Value can also be Jenkins Build Parameters   Detailed steps can be seen here  -  https   itisatechiesworld wordpress com jenkins-related-articles jenkins-configuration jenkins-passing-a-parameter-from-one-job-to-another   Hope it s helpful

User · Answer

You can use Parameterized Trigger Plugin which will let you pass parameters from one task to another   You need also add this parameter you passed from upstream in downstream

User · Answer

The accepted answer here does not work for my use case  I needed to be able to dynamically create parameters in one job and pass them into another  As Mark McKenna mentions there is seemingly no way to export a variable from a shell build step to the post build actions   I achieved a workaround using the Parameterized Trigger Plugin by writing the values to a file and using that file as the parameters to import via  Add post-build action  -   Trigger parameterized build     then selecting  Add Parameters  -   Parameters from properties file

User · Answer

I figured it out  With almost 2 hours worth of trial and error  i figured it out  This WORKS and is what you do to pass variables to remote job      def handle   triggerRemoteJob remoteJenkinsName   remoteJenkins   job   RemoteJob  paramters   quot param1   env PARAM1  nparam2   env param2  quot    Use  n to separate two parameters  no spaces   As opposed to parameters     someparams    we use paramters   quot someparams quot  the  quot       quot  is what gets us the values of the desired variables   These are double quotes  not two single quotes  the             or         will not get us those values   Three single quotes or just single quotes  All parameters here are defined in environment   block at the start of the pipeline and are modified in stages gt steps gt scripts wherever necessary  I also tested and found that when you use  quot       quot  you cannot use something like          quot     quot      or  quot             quot  or any combination of it    The catch here is that when you are using  quot     quot  in parameters section  you cannot pass a string parameter  for example This WILL NOT WORK      def handle   triggerRemoteJob remoteJenkinsName   remoteJenkins   job   RemoteJob  paramters   quot param1   env PARAM1  nparam2  param2  quot    if you want to pass something like the one above  you will need to set an environment variable param2  param2  and then use   env param2  in the parameters section of remote trigger plugin step

User · Answer

I think the answer above needs some update   I was trying to create a dynamic directory to store my upstream build artifacts so I wanted to pass my upstream job build number to downstream job I tried the above steps but couldn t make it work  Here is how it worked    I copied the artifacts from my current job using copy artifacts plugin  In post build action of upstream job I added the variable like  SOURCE BUILD NUMBER   BUILD NUMBER   and configured it to trigger the downstream job  Everything worked except that my downstream job was not able to get  SOURCE BUILD NUMBER to create the directory  So I found out that to use this variable I have to define the same variable in down stream job as a parameter variable like in this picture below         This is because the new version of jenkins require s you to define the variable in the downstream job as well  I hope it s helpful

User · Answer

I faced the same issue when I had to pass a pom version to a downstream Rundeck job   What I did  was using parameters injection via a properties file as such   1  Creating properties in properties file via shell    Build actions    Execute a shell script Inject environment variables   E g   properties definition  2  Passing defined properties to the downstream job   Post Build Actions      Trigger parameterized build on other project Add parameters   Current build parameters Add parameters   predefined parameters   E g   properties sending  3  It was then possible to use  POM VERSION as such in the downstream Rundeck job        Jenkins Version   1 636      For some reason when creating the triggered build  it was necessary to add the option  Current build parameters  to pass the properties

[continuous-integration] Jenkins - passing variables between jobs?

Examples related to continuous-integration

Examples related to hudson

Examples related to jenkins