entityMap|blocks|key|355m6|text|基于c3st7n的技巧，我测试了以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8c00u|build+job:+"NameOfTheJob"",+parameters:
++[
++++[$class:+'StringParameterValue',+name:+'BRANCH',+value:+"${BRANCH}"],
++++[$class:+'StringParameterValue',+name:+'WHERE',+value:+"F3"],

++]|code-block|syntax|javascript|av4ef|这是可行的。|fo54h^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|K|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|L|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|M|9|@]|A|@]|B|$]]|$2|J|4|-4|6|7|8|N|9|@]|A|@]|B|$]]]]

Based on the tip of c3st7n I have tested the following:

<pre><code>build job: "NameOfTheJob"", parameters:
 [
 [$class: 'StringParameterValue', name: 'BRANCH', value: "${BRANCH}"],
 [$class: 'StringParameterValue', name: 'WHERE', value: "F3"],

 ]
</code></pre>

This works.

entityMap|blocks|key|eb1su|text|我见过一个使用以下语法的工作示例：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8hls5|build+job:'NameOfTheJob',+parameters:+[
++++++string(name:+'FirstOption',+value:+"test"),
++++++string(name:+'AnotherOption',+value:+"test12")
]|code-block|syntax|javascript|5v0jk|基本上，不要以特殊的方式对待choice参数，只是将它们当作常规的字符串参数。|5lqbc^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|K|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|L|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|M|9|@]|A|@]|B|$]]|$2|J|4|-4|6|7|8|N|9|@]|A|@]|B|$]]]]

I have seen a working example that uses the below syntax:

<pre><code>build job:'NameOfTheJob', parameters: [
 string(name: 'FirstOption', value: "test"),
 string(name: 'AnotherOption', value: "test12")
]
</code></pre>

Basically, don't treat the choice parameters in a special manner, just treat them as regular string parameters.

entityMap|blocks|key|35g61|text|在脚本模式下，你也可以这样做，在它被you的时候，它希望选择参数是换行符分隔的字符串，而不是数组。在脚本模式下使用管道和JenkinsFile时，可以执行快速修复，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|a5opg|properties(
++++[parameters([choice(choices:+["A",+"B",+"C"].join("\n"),
++++description:+'Some+choice+parameter',+
++++name:+'SOME_CHOICE')])])|code-block|syntax|javascript|2ghu9|您可以将其放在第一个node语句之前，以便向构建中添加参数。|9qape|更新:+Jenkins管道文件中带有扩展选择参数插件的示例多选：|fukf6|com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition+extendedChoiceParameterDefinition+=+new+com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition(
++++"OPTION_NAME",+//+name
++++"PT_CHECKBOX",+//+type
++++"option1,option2,option3",+//+values
++++null,+//+projectName
++++null,+//+propertyFile
++++null,+//+groovyScript
++++null,+//+groovyScriptFile
++++null,+//+bindings
++++null,+//+groovyClasspath
++++null,+//+propertyKey
++++"option1,option2",+//+defaultValue
++++null,+//+defaultPropertyFile
++++null,+//+defaultGroovyScript
++++null,+//+defaultGroovyScriptFile
++++null,+//+defaultBindings
++++null,+//+defaultGroovyClasspath
++++null,+//+defaultPropertyKey
++++null,+//+descriptionPropertyValue
++++null,+//+descriptionPropertyFile
++++null,+//+descriptionGroovyScript
++++null,+//+descriptionGroovyScriptFile
++++null,+//+descriptionBindings
++++null,+//+descriptionGroovyClasspath
++++null,+//+descriptionPropertyKey
++++null,+//+javascriptFile
++++null,+//+javascript
++++false,+//+saveJSONParameterToFile
++++false,+//+quoteValue
++++10,+//+visible+item+count
++++"Select+your+options",+//+description
++++","+//multiSelectDelimiter
)

normalChoiceOptions+=+["option1","option2"]

properties([
++++++++parameters([
++++++++++++++++choice(choices:+normalChoiceOptions.join("\n"),+description:+'Single+select+option',+name:+'SOME_OPTION'),++++++++++++++++
++++++++++++++++extendedChoiceParameterDefinition
++++++++])
])|cjqa7^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|O|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|P|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|Q|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|R|9|@]|A|@]|B|$]]|$2|L|4|M|6|E|8|S|9|@]|A|@]|B|$F|G]]|$2|N|4|-4|6|7|8|T|9|@]|A|@]|B|$]]]]

In script mode you can also do it like this, at the moment it is bugged and it expects the choice parameters as a newline delimited string instead of an array. 
When using the Pipeline and JenkinsFile in script mode you can do a quick fix like follows:

<pre><code>properties(
 [parameters([choice(choices: ["A", "B", "C"].join("\n"),
 description: 'Some choice parameter', 
 name: 'SOME_CHOICE')])])
</code></pre>

You can put this before your first node statement to add parameters to your builds.

Update: example multi select with extended choice parameter plugin in Jenkins pipeline file:

<pre><code>com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition extendedChoiceParameterDefinition = new com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition(
 "OPTION_NAME", // name
 "PT_CHECKBOX", // type
 "option1,option2,option3", // values
 null, // projectName
 null, // propertyFile
 null, // groovyScript
 null, // groovyScriptFile
 null, // bindings
 null, // groovyClasspath
 null, // propertyKey
 "option1,option2", // defaultValue
 null, // defaultPropertyFile
 null, // defaultGroovyScript
 null, // defaultGroovyScriptFile
 null, // defaultBindings
 null, // defaultGroovyClasspath
 null, // defaultPropertyKey
 null, // descriptionPropertyValue
 null, // descriptionPropertyFile
 null, // descriptionGroovyScript
 null, // descriptionGroovyScriptFile
 null, // descriptionBindings
 null, // descriptionGroovyClasspath
 null, // descriptionPropertyKey
 null, // javascriptFile
 null, // javascript
 false, // saveJSONParameterToFile
 false, // quoteValue
 10, // visible item count
 "Select your options", // description
 "," //multiSelectDelimiter
)

normalChoiceOptions = ["option1","option2"]

properties([
 parameters([
 choice(choices: normalChoiceOptions.join("\n"), description: 'Single select option', name: 'SOME_OPTION'), 
 extendedChoiceParameterDefinition
 ])
])
</code></pre>

entityMap|blocks|key|e435d|text|使用ExtendedChoiceParameterValue而不是ChoiceParameterValue|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|bbm94|例如：|2mu0g|[$class:+'ExtendedChoiceParameterValue',+name:+'param_name',+value:+'param_value']|code-block|syntax|javascript|1c9c3^0|2|S|X|K|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|O|9|@$A|P|B|Q|C|D]|$A|R|B|S|C|D]]|E|@]|F|$]]|$2|G|4|H|6|7|8|T|9|@]|E|@]|F|$]]|$2|I|4|J|6|K|8|U|9|@]|E|@]|F|$L|M]]|$2|N|4|-4|6|7|8|V|9|@]|E|@]|F|$]]]]

Use <code>ExtendedChoiceParameterValue</code> instead of <code>ChoiceParameterValue</code>
e.g.
<pre><code>[$class: 'ExtendedChoiceParameterValue', name: 'param_name', value: 'param_value']
</code></pre>

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://www.jenkins.io/doc/book/pipeline/syntax/#parameters|blocks|key|9rtto|text|正如2020年9月在https://www.jenkins.io/doc/book/pipeline/syntax/#parameters上记录的那样，在管道中使用choice参数的文档化语法是：|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|amtlr|pipeline+{
++++agent+any
++++parameters+{
++++++++choice(
++++++++++++name:+'CHOICE',
++++++++++++choices:+['one',+'two',+'three'],
++++++++++++description:+''
++++++++)
++++}
++++stages+{
++++++++stage('Example')+{
++++++++++++steps+{
++++++++++++++++echo+"Choice:+${params.CHOICE}"
++++++++++++++++sh+"echo+Choice:+${params.CHOICE}"
++++++++++++++++sh+'echo+Choice:+$CHOICE'
++++++++++++}
++++++++}
++++}
}|code-block|syntax|javascript|dr04c|在测试中，默认选择列表中的第一个参数，我没有查看是否有可能出现其他情况。|2ns0e|任务的所有三个版本执行相同的操作。注意使用的特定引号。|84nco^0|A|1N|0|0|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|U|G|@]|H|@$I|V|J|W|A|X]]|6|$]]|$A|K|C|L|2|M|F|Y|G|@]|H|@]|6|$N|O]]|$A|P|C|Q|2|E|F|Z|G|@]|H|@]|6|$]]|$A|R|C|S|2|E|F|10|G|@]|H|@]|6|$]]|$A|T|C|-4|2|E|F|11|G|@]|H|@]|6|$]]]]

As documented at <a href="https://www.jenkins.io/doc/book/pipeline/syntax/#parameters" rel="nofollow noreferrer">https://www.jenkins.io/doc/book/pipeline/syntax/#parameters</a> in September 2020, the documented syntax to use a choice parameter in a pipeline is:
<pre><code>pipeline {
 agent any
 parameters {
 choice(
 name: 'CHOICE',
 choices: ['one', 'two', 'three'],
 description: ''
 )
 }
 stages {
 stage('Example') {
 steps {
 echo &quot;Choice: ${params.CHOICE}&quot;
 sh &quot;echo Choice: ${params.CHOICE}&quot;
 sh 'echo Choice: $CHOICE'
 }
 }
 }
}
</code></pre>
In testing, the choice defaults to the first parameter in the list, I have not looked into if this has potential to be otherwise.
All three versions of the task perform the same. Note the specific quotes used.

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/|blocks|key|9u82q|text|您可以使用extendedChoice而不是ChoiceParameterValue，如下所示：|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|9k2ic|build+job:+'NameOfTheJob',+parameters:+[extendedChoice(name:+'WHERE',+value:+'F3')]|code-block|syntax|javascript|4mqpg|詹金斯文档：https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/|323m^0|5|E|M|K|0|0|6|1Q|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|U|G|@$H|V|I|W|J|K]|$H|X|I|Y|J|K]]|L|@]|6|$]]|$A|M|C|N|2|O|F|Z|G|@]|L|@]|6|$P|Q]]|$A|R|C|S|2|E|F|10|G|@]|L|@$H|11|I|12|A|13]]|6|$]]|$A|T|C|-4|2|E|F|14|G|@]|L|@]|6|$]]]]

You can use <code>extendedChoice</code> instead of <code>ChoiceParameterValue</code>
like:
<pre><code>build job: 'NameOfTheJob', parameters: [extendedChoice(name: 'WHERE', value: 'F3')]
</code></pre>
Jenkins docs:
<a href="https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/" rel="nofollow noreferrer">https://www.jenkins.io/doc/pipeline/steps/pipeline-build-step/</a>

Currently I have a pipeline job which has different paramters where one of this parameters is a Choice parameter. Here is the config.xml output of that job parameter:

<pre class="lang-xml prettyprint-override"><code>&lt;hudson.model.ChoiceParameterDefinition&gt;
 &lt;choices class="java.util.Arrays$ArrayList"&gt;
 &lt;a class="string-array"&gt;
 &lt;string&gt;f1&lt;/string&gt;
 &lt;string&gt;f2&lt;/string&gt;
 &lt;string&gt;f3&lt;/string&gt;
 &lt;string&gt;f4&lt;/string&gt;
 &lt;/a&gt;
 &lt;/choices&gt;
 &lt;name&gt;WHERE&lt;/name&gt;
 &lt;description&gt;Something&lt;/description&gt;
&lt;/hudson.model.ChoiceParameterDefinition&gt;
</code></pre>

Now I can call this job from a pipeline via by passing a string parameter:

<pre><code>build job: "NameOfTheJob"", parameters:
 [
 [$class: 'StringParameterValue', name: 'BRANCH', value: "${BRANCH}"],
 ]
</code></pre>

But I couldn't get a way to define the parameters for a choice parameter:

I have tried the following:

<pre><code>build job: "NameOfTheJob"", parameters:
 [
 [$class: 'StringParameterValue', name: 'BRANCH', value: "${BRANCH}"],
 [$class: 'ChoiceParameterValue', name: 'WHERE', value: 'F3'],
 ]
</code></pre>

But this failed with the following error:

<pre><code>java.lang.UnsupportedOperationException: no known implementation of class hudson.model.ParameterValue is named ChoiceParameterValue
</code></pre>

So the question is: How to define a choice parameters in calling an other pipeline job:

<pre><code>build job: "NameOfTheJob"", parameters:
 [
 [$class: 'StringParameterValue', name: 'BRANCH', value: "${BRANCH}"],
 [$class: '??????', ????],
 ]
</code></pre>

Does someone has an example of such thing?

Jenkins Choice parameter Passing to a pipeline Job

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

目前我有一个管道作业，它有不同的参数，其中一个参数是Choice参数。以下是该作业参数的config.xml输出： <hudson.model.ChoiceParameterDefinition> <choices class="java.util.Arrays$ArrayList"> <a cl...

问Jenkins Choice参数传递给管道作业
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins Choice参数传递给管道作业EN