您好，我正在尝试获得 Jenknis-Declarative-Pipeline-Job 工作。
用例应该非常简单:
我想使用相同的 Jenkins 管道构建多个插件。为此，我编写了一个“JenkinsLibrary”，其中包含插件可用于参数的接口(interface)。该参数之一是轴值。
我遇到的问题与 this reddist post 非常相似。
我想从变量设置矩阵构建的“轴”的“值”。 我没有想法，这可能吗？
这是我的例子:
带有文件 my_library.groovy 的“JenkinsLibrary”
def call(Map i_options)
{
// later I will parse the options to set the values, but currently the step before already crashes ...
def axis_1_values = "axis_1_value_A"
// already tried the following alternatives ...
// def axis_1_values = 'axis_1_value_A'
// def axis_1_values = '''axis_1_value_A'''
// def axis_1_values = ["axis_1_value_A", "axis_2_value_A"]
pipeline
{
agent any
stages { stage("stage A") { matrix {
axes {
axis {
name "axis_1"
// values "axis_1_value_A" // <- of course this works ...
// but I want to read it from a variable
values "${axis_1_values}"
// I already tried more variants
// values ${axis_1_values}
// values axis_1_values
}
axis {
name "axis_2"
values "axis_2_value_A", "axis_2_value_B"
}
}
stages {
stage("another stage") { steps {
echo "hello world from ${axis_1} && ${axis_2}"
} }
}
} } }
}
}
带有文件“Jenkinsfile”的插件:
@Library("JenkinsLibrary") _
def options = [
axis_values: "a_axis_value"
]
my_library(options)
我收到以下错误:
[...] Expected string literal but got "${axis_1_values}"
完整日志:
19: Expected string literal but got "${axis_1_values}" @ line 19, column 28.
values "${axis_1_values}"
^
1 error
at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:254)
at groovy.lang.GroovyClassLoader.recompile(GroovyClassLoader.java:761)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:718)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:787)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:775)
at org.jenkinsci.plugins.workflow.cps.global.UserDefinedGlobalVariable.getValue(UserDefinedGlobalVariable.java:57)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113)
at sun.reflect.GeneratedMethodAccessor729.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:160)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:157)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:142)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:158)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:162)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at WorkflowScript.run(WorkflowScript:21)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)
at sun.reflect.GeneratedMethodAccessor500.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:39)
at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
at com.cloudbees.groovy.cps.impl.LocalVariableBlock.evalLValue(LocalVariableBlock.java:28)
at com.cloudbees.groovy.cps.LValueBlock$BlockImpl.eval(LValueBlock.java:55)
at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java:16)
at com.cloudbees.groovy.cps.Next.step(Next.java:83)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:185)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:405)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:96)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:317)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:281)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE
我的系统:
Jenkins 版本:Jenkins 版本。 2.190.1
声明式插件版本 1.5.0
声明式代理 API:1.1.1
声明式扩展点 API:1.5.0
(还有很多其他插件，我认为这是重要的)
更新
我仍然没有解决办法。但是当我定义这样的变量时，我知道我尝试向其中插入一个“GStringImpl”。但我无法将其转换为 java-string。
def _str_1 = "a string"
def _str_2 = "${_str_1}"
println _str_1.class // -> class java.lang.String
println _str_2.class // -> class org.codehaus.groovy.runtime.GStringImpl
def _str_3 = "${_str_1}" as java.lang.String
println _str_3.class // -> class java.lang.String
但我仍然不知道如何添加单个值，因为如果我这样做
values "${axis_1_values}" as as java.lang.String // error-msg: Expected string literal but got ${as}
values ("${axis_1_values}" as java.lang.String) // error-msg: Expected string literal but got ${"${axis_1_values}"
values axis_1_values.toString() // error-msg: Method calls on objects not allowed outside "script" blocks.
values "${axis_1_values}".toString() // error-msg: Expected a symbol @ line 26, column 28.
此转换内容可能适用于单个值，但我希望能够添加值列表，就像在默认示例中可能的那样...
值“axis_2_value_A”、“axis_2_value_B”
我想知道，这是否适用于声明性管道的“docker-agent”部分。
agent {
docker {
image "${_image}:latest"
label "${_label}"
}
}
但是我在代码中，我意识到docker-label的解析是单独实现的...
我仍然不知道如何在声明性管道的矩阵/轴特征中实现该目标。
(funfact:即使这样做的主要原因之一是脚本管道的蓝海 View 中的可视化仍然存在错误，并且该问题似乎被忽略了......
https://issues.jenkins-ci.org/browse/JENKINS-53751 )
最佳答案
自插件 v1.6.0 起，声明式管道不支持动态轴值。错误消息表明它需要一个“文字字符串”值。也许该消息还应该说:“不允许使用模板字符串、数组、变量或函数调用。”
这是设计使然，旨在防止管道作者受到管道引擎的某些内部假设的影响。可能会改变，但需要仔细规划和测试。
请通过 https://issues.jenkins.io/ 提交 JIRA和/或加入Jenkins Pipeline Authoring SIG并帮助实现此功能。
关于jenkins - 具有动态矩阵轴值的声明式管道，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/59844846/