如何解决Jenkins Pipeline无法触发具有Maven存储库工件的参数化作业
当尝试触发参数类型为Maven Repository Artifact的本地作业时,由于工作流支持未正确映射到VersionParameterValue类,因此作业无法触发。查看repository-connector类中的代码,尝试从冒号分隔的字符串实例化。
[VersionParameterValue@[name=deploy_number,groupid=com/****/database,artifactid=DB_xya,propertyName=deploy_number,version=1.2.3]]
[Pipeline] build (Building jobname)
Scheduling project: jobname
The parameter 'deploy_number' did not have the type expected by jobname. Converting to Maven Repository Artifact.
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.lang.ArrayIndexOutOfBoundsException: 1
at org.jvnet.hudson.plugins.repositoryconnector.VersionParameterDefinition.createValue(VersionParameterDefinition.java:140)
at org.jenkinsci.plugins.workflow.support.steps.build.BuildTriggerStepExecution.completeDefaultParameters(BuildTriggerStepExecution.java:193)
at org.jenkinsci.plugins.workflow.support.steps.build.BuildTriggerStepExecution.start(BuildTriggerStepExecution.java:101)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
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:163)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:157)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:161)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:165)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:135)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at WorkflowScript.run(WorkflowScript:22)
We are using the jenkins 2.222.3 and build step 2.13,all required dependencies met. Running the job on its own works without issue. Looking for clues/workarounds
Which shows us from source in [git hub][1]
@Override
public ParameterValue createValue(String input) {
final String[] tokens = input.split(":");
return new VersionParameterValue(tokens[0],tokens[1],tokens[2],tokens[3]);
}
[1]: https://github.com/jenkinsci/repository-connector-plugin/blob/master/src/main/java/org/jvnet/hudson/plugins/repositoryconnector/VersionParameterDefinition.java
解决方法
是的,遇到了同样的问题,并通过构建以下内容解决了管道构建工作
/admin
在上面
-
string(name:'ARTIFACT_PARAM_ID',value: "<groupId>:<artifactId>:ARTIFACT_PARAM_ID:${pomVersion}")
-是我们要触发的作业中参数的名称 -
ARTIFACT_PARAM_ID
是我们之前在管道中设置的环境变量,您可以将其替换为要传递参数的版本 -
${pomVersion}
替换为工件的组ID(我们将其选择为与尝试触发的工作中的参数相同) -
<groupId>
-替换为工件ID(我们选择它与要触发的作业中的参数相同)
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。