blocks|key|409691|text|您可以使用Parameterized+Trigger+Plugin，它允许您将参数从一个任务传递到另一个任务。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|409692|您还需要将从上游传入的此参数添加到下游。|409693|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.jenkins-ci.org/display/JENKINS/Parameterized%2BTrigger%2BPlugin^0|5|S|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You can use <a href="https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin" rel="noreferrer">Parameterized Trigger Plugin</a> which will let you pass parameters from one task to another.

You need also add this parameter you passed from upstream in downstream.

blocks|key|409960|text|1.构建后操作>选择“在其他项目上触发参数化构建”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|409961|2.输入带有value.Value的环境变量也可以是Jenkins构建参数。|409962|详细步骤可在此处查看：|409963|https://itisatechiesworld.wordpress.com/jenkins-related-articles/jenkins-configuration/jenkins-passing-a-parameter-from-one-job-to-another/|offset|length|409964|希望对您有所帮助:)|409965|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|3V|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@$H|W|I|X|1|Y]]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|G]]]]

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 :-

<a href="https://itisatechiesworld.wordpress.com/jenkins-related-articles/jenkins-configuration/jenkins-passing-a-parameter-from-one-job-to-another/" rel="noreferrer">https://itisatechiesworld.wordpress.com/jenkins-related-articles/jenkins-configuration/jenkins-passing-a-parameter-from-one-job-to-another/</a>

Hope it's helpful :)

blocks|key|410015|text|这里的accepted+answer不适用于我的用例。我需要能够在一个作业中动态创建参数，并将它们传递给另一个作业。正如Mark+McKenna提到的，似乎没有办法将变量从shell构建步骤导出到构建后操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|410016|我使用Parameterized+Trigger+Plugin实现了一个变通方法，方法是将值写到一个文件中，并使用该文件作为参数，通过'Add+post-build+action‘->+'Trigger+parameterized+build...’导入。然后选择'Add+Parameters‘->+'Parameters+from+properties+file’。|410017|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/9704755/6204803|1|https://stackoverflow.com/users/584585/mark-mckenna|2|https://wiki.jenkins-ci.org/display/JENKINS/Parameterized%2BTrigger%2BPlugin^0|3|F|0|1O|C|1|0|3|S|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

The <a href="https://stackoverflow.com/a/9704755/6204803">accepted answer</a> 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 <a href="https://stackoverflow.com/users/584585/mark-mckenna">Mark McKenna</a> 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 <a href="https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin" rel="noreferrer">Parameterized Trigger Plugin</a> 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'.

blocks|key|409930|text|(供谷歌同事使用)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|409931|如果你正在使用Build+Flow+Plugin构建一个重要的管道，你可以像这样在作业之间传递参数：|offset|length|409932|假设有一个可用的字符串参数"CVS_TAG"，为了将其传递给其他作业：|409933|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'])|code-block|syntax|javascript|409934|显示可用变量/参数的提示：|409935|//+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+->+$it.value"+}
out.println+'------------------------------------'|409936|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.jenkins-ci.org/display/JENKINS/Build%2BFlow%2BPlugin^0|0|7|H|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|16|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

(for fellow googlers)

If you are building a serious pipeline with the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin" rel="noreferrer">Build Flow Plugin</a>, 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 :

<pre><code>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'])
</code></pre>

Hint for displaying available variables / params :

<pre><code>// 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 '------------------------------------'
</code></pre>

blocks|key|625152|text|只需将我的答案添加到Nigel+Kirby的答案之外，因为我还不能评论：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|625153|为了传递动态创建的参数，您还可以将变量导出到'Execute+Shell‘磁贴中，然后通过'Trigger+parameterized+build+on+other+projects’=>‘预定义参数“npm+use+'YOUR_VAR=$YOUR_VAR’。我的团队使用此功能将npm包版本从一个构建作业传递到部署作业|625154|更新:上面只适用于Jenkins注入的参数，从shell创建的参数仍然需要使用相同的方法。例如：回显YOUR_VAR=${YOUR_VAR}+>+variable.properties并将该文件向下传递|625155|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

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

blocks|key|625208|text|通读答案，我没有看到另一个我喜欢的选择，所以也会提供它。我喜欢作业的参数化，但它的伸缩性并不总是很好。如果您的作业不是直接位于第一个作业的下游，而是流水线中更远的位置，那么您并不是真的想将流水线中的每个作业都参数化，以便能够将参数一直传递下去。或者，如果您有许多其他作业使用的大量参数(特别是那些不一定绑定到一个父作业或主作业的作业)，同样，参数化也不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|625209|在这些情况下，我倾向于将值输出到属性文件，然后使用EnvInject插件将其注入到我需要的任何工作中。这可以动态完成，这是另一种解决问题的方法，来自上面的另一个答案，其中仍然使用参数化作业。此解决方案在许多情况下都具有很好的伸缩性。|offset|length|625210|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.jenkins.io/display/JENKINS/EnvInject%2BPlugin^0|0|P|9|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

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 <a href="https://wiki.jenkins.io/display/JENKINS/EnvInject+Plugin" rel="nofollow noreferrer">EnvInject</a> 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.

blocks|key|409870|text|您可以使用Hudson+Groovy+builder来完成此操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|409871|流水线中的第一个作业|409872|​|409873|📷|atomic|409874|409875|管道中的第二个工作|409876|409877|409878|409879|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.jenkins-ci.org/display/JENKINS/Groovy%2Bplugin|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c12ccadf07acd6361c91c1bcc33e9131.png|imageAlt|2|https://ask.qcloudimg.com/http-save/yehe-900000/87d217bd1f1f829ed4882ab301b2bf77.png^0|5|L|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]]|C|$]]|$1|K|3|G|5|6|7|1G|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1H|8|@]|9|@]|C|$]]|$1|N|3|G|5|6|7|1I|8|@]|9|@]|C|$]]|$1|O|3|I|5|J|7|1J|8|@]|9|@$A|1K|B|1L|1|1M]]|C|$]]|$1|P|3|G|5|6|7|1N|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1O|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|Z|U|10|C|$11|12|13|-4]]|14|$5|Z|U|10|C|$11|15|13|-4]]]]

You can use <a href="http://wiki.jenkins-ci.org/display/JENKINS/Groovy+plugin" rel="nofollow noreferrer">Hudson Groovy builder</a> to do this.

First Job in pipeline

<img src="https://i.stack.imgur.com/MTFU6.png" alt="enter image description here">

Second job in pipeline

<img src="https://i.stack.imgur.com/5ZMYU.png" alt="enter image description here">

blocks|key|625331|text|我想通了！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|625332|经过近两个小时的反复试验，我终于找到了答案。|625333|这是您将变量传递到远程作业时所做的工作：|625334|++++def+handle+=+triggerRemoteJob(remoteJenkinsName:+'remoteJenkins',+job:+'RemoteJob'+paramters:+"param1=${env.PARAM1}\nparam2=${env.param2}")|code-block|syntax|javascript|625335|使用\n分隔两个参数，无空格..|625336|与参数相反：‘someparams’|625337|我们使用参数："someparams“|625338|“...”是让我们得到所需变量的值的方法。(这些是双引号，而不是两个单引号)|625339|“”...“”或者“...”不会给我们带来这些值。(三个单引号或只有单引号)|625340|此处的所有参数都在管道开始处的环境{}块中定义，并在必要时在stages>steps>scripts中进行修改。|625341|我还测试并发现当你使用“...”你不能使用像‘’这样的东西...+"...“‘或"...+'..'...“或者它的任何组合。|625342|这里的问题是，当你使用"...“在parameters部分，您不能传递字符串参数；例如，这将不起作用：|625343|++++def+handle+=+triggerRemoteJob(remoteJenkinsName:+'remoteJenkins',+job:+'RemoteJob'+paramters:+"param1=${env.PARAM1}\nparam2='param2'")|625344|如果要传递类似上面的内容，则需要设置环境变量param2='param2‘，然后在远程触发器插件步骤的parameters部分中使用${env.param2|625345|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|19|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1E|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1F|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1H|8|@]|9|@]|A|$]]|$1|10|3|11|5|H|7|1I|8|@]|9|@]|A|$I|J]]|$1|12|3|13|5|6|7|1J|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|15|$]]

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:
<pre><code> def handle = triggerRemoteJob(remoteJenkinsName: 'remoteJenkins', job: 'RemoteJob' paramters: &quot;param1=${env.PARAM1}\nparam2=${env.param2}&quot;)
</code></pre>
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:
<pre><code> def handle = triggerRemoteJob(remoteJenkinsName: 'remoteJenkins', job: 'RemoteJob' paramters: &quot;param1=${env.PARAM1}\nparam2='param2'&quot;)
</code></pre>
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

blocks|key|625386|text|您还可以将一个作业写入某个属性文件中，并让另一个作业读取该文件。其中一种方法是通过EnvInject插件注入变量。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|625387|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can also make a job write into a properties file somewhere and have another job read it. One of the way to do that is to inject variables via EnvInject plugin.

blocks|key|410346|text|这可以通过groovy函数来完成：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410347|上行Jenkinsfile+-参数CREDENTIALS_ID向下传递|offset|length|style|CODE|410348|pipeline+{
++++stage+{
++++++++steps+{
++++++++++++build+job:+"my_downsteam_job_name",
++++++++++++parameters+[string(name:+'CREDENTIALS_ID',+value:+'other_credentials_id')]
++++++++}
++++}
}|code-block|syntax|javascript|410349|下游Jenkinsfile+-如果参数CREDENTIALS_ID未从上行传递，则函数返回默认值|410350|def+getCredentialsId()+{
++++if(params.CREDENTIALS_ID)+{
++++++++return+params.CREDENTIALS_ID;
++++}+else+{
++++++++return+"default_credentials_id";
++++}
}
pipeline+{
++++environment{
++++++++TEST_PASSWORD+=+credentials("${getCredentialsId()}")
++++}
}|410351|entityMap^0|0|H|E|0|0|J|E|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|W|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

This could be done via groovy function:
<h5>upstream Jenkinsfile - param <code>CREDENTIALS_ID</code> is passed downsteam</h5>
<pre><code>pipeline {
 stage {
 steps {
 build job: &quot;my_downsteam_job_name&quot;,
 parameters [string(name: 'CREDENTIALS_ID', value: 'other_credentials_id')]
 }
 }
}
</code></pre>
<h5>downstream Jenkinsfile - if param <code>CREDENTIALS_ID</code> not passed from upsteam, function returns default value</h5>
<pre><code>def getCredentialsId() {
 if(params.CREDENTIALS_ID) {
 return params.CREDENTIALS_ID;
 } else {
 return &quot;default_credentials_id&quot;;
 }
}
pipeline {
 environment{
 TEST_PASSWORD = credentials(&quot;${getCredentialsId()}&quot;)
 }
}
</code></pre>

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?

Jenkins - passing variables between jobs?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我在jenkins中有两个工作，它们都需要相同的参数。如何使用参数运行第一个作业，以便在触发第二个作业时使用相同的参数？

问Jenkins -在作业之间传递变量？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins -在作业之间传递变量？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins -在作业之间传递变量？
EN