当body()方法在管道常规脚本中调用时,出现“无签名”错误
我正在使用Jenkins共享库进行管道项目。我已经在本地Jenkins中配置了共享库。当我尝试访问共享库时,它会被正确调用,但是我无法解析共享库call()
方法中出现的参数值。
我的共享库代码(myDeliveryPipeline.groovy
)
def call(body) {
println(body)
// evaluate the body block, and collect configuration into the object
def pipelineParams= [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = pipelineParams
body()
println (pipelineParams.BRANCH)
println 'Map'
println body
println 'pipelineParams'
println pipelineParams
println 'Start pipeline steps'
// our complete declarative pipeline can go in here
pipeline {
agent any
// Stage checkout git
stages {
stage('checkout git') {
steps{
git branch: 'master', url:'MY_GIT_HUB_URL'
}
}
//checkout git ends
// stage build
stage('build') {
steps{
script{
if(isUnix()){
sh 'mvn clean package -Dmaven.test.skip=true'
}
else{
bat('mvn clean install -Dmaven.test.skip=true')
}
}
}
}
// stage build ends
// stage Test
stage ('test') {
steps{
script{
if('yes' == 'yes'){
if(isUnix()){
parallel (
"unit tests": { sh 'mvn test' },
"integration tests": { sh 'mvn integration-test' }
)
}
else{
parallel (
"unit tests": { bat('mvn test')},
"integration tests": { bat('mvn integration-test')}
)
}
}
}
}
}
// stage Test Ends
}
post {
failure {
mail to: 'MAIL_ID@gmail.com', subject: 'Pipeline failed', body: "${env.BUILD_URL}"
}
success{
println "SUCCESS"
}
}
}
}
我的Jenkins文件
properties ([
parameters([
string(name: 'BRANCH', defaultValue: 'master', description: 'Branch to build'),
choice(name: 'RUN_TEST', choices: ['yes', 'no'], description: 'Run test while build'),
booleanParam(name: 'MAIL_TRIGGER', defaultValue: true, description: 'mail to be triggred'),
string(name: 'EMAIL', defaultValue: 'MY_EMAIL@gmail.com', description: 'Mail to be notified')
])
])
@Library('my-pipeline-library') _
myDeliveryPipeline(BRANCH:params.BRANCH, RUN_TEST:params.RUN_TEST, MAIL_TRIGGER:params.MAIL_TRIGGER, EMAIL:params.EMAIL)
我的工作日志
> C:\Program Files\Git\bin\git.exe rev-list --no-walk 2fdeb821e0ecec40e53b2e0bdd6608840914422b # timeout=10
[Pipeline] properties
[Pipeline] echo
{BRANCH=master, RUN_TEST=yes, MAIL_TRIGGER=true, EMAIL=MAIL_ID@gmail.com}
[Pipeline] End of Pipeline
hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: java.util.LinkedHashMap.call() is applicable for argument types: () values: []
Possible solutions: wait(), any(), wait(long), any(groovy.lang.Closure), take(int), any(groovy.lang.Closure)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:58)
at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:49)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)
at myDeliveryPipeline.call(C:\Program Files (x86)\Jenkins\jobs\TestJenkinsFile\builds\43\libs\my-pipeline-library\vars\myDeliveryPipeline.groovy:10)
at WorkflowScript.run(WorkflowScript:14)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixName(FunctionCallBlock.java:77)
at sun.reflect.GeneratedMethodAccessor255.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
答案 0 :(得分:0)
在共享库文件vars/myDeliveryPipeline.groovy
中,call
的签名为call(<Closure>)
。
但是,我看到您正在按call(<Map>)
的名称来调用它。
因此,将其命名为:
myDeliveryPipeline {
BRANCH=params.BRANCH
RUN_TEST=params.RUN_TEST
MAIL_TRIGGER=params.MAIL_TRIGGER
EMAIL=params.EMAIL
}
代替:myDeliveryPipeline(BRANCH:params.BRANCH, RUN_TEST:params.RUN_TEST, MAIL_TRIGGER:params.MAIL_TRIGGER, EMAIL:params.EMAIL)
。
现在,签名已修复,但是我可以看到您覆盖了从詹金斯到Map的闭包(主体)的DELEGATION。因此,params
未定义。
因此,我建议将call(<Closure>)
重载call(<Map>, <Closure>)
。
def call(body) {
call([:], body)
}
def call(pipelineParams, body) {
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = pipelineParams
body()
//...
}
现在,呼叫可以是:
myDeliveryPipeline(
BRANCH:params.BRANCH,
RUN_TEST:params.RUN_TEST,
MAIL_TRIGGER:params.MAIL_TRIGGER,
EMAIL:params.EMAIL
) {}
不要忘记最后一个{}
。
简短地:
如果要注入管道变量(即params,...),即使闭包为空,也应使用签名Map
将它们注入myDeliveryPipeline(Map,Closure)
中。
如果您不依赖于管道变量,则可以通过使用签名Closure
myDeliveryPipeline(Closure)
。