groovy.lang.MissingPropertyException:否此类属性:类groovy.lang.Binding的管道

时间:2018-09-06 00:10:09

标签: jenkins groovy jenkins-pipeline

我有一个简单的jenkinsfile,如下所示:

pipeline { 
agent any 
stages {
    stage('Build') { 
        steps { 
            sh './mvnw compile' 
        }
    }
    stage('Test'){
        steps {
            sh './mvnw test'
        }
    }
  }
}

和带有存储库URL和凭证的简单Jenkins管道(我可以确认凭证是正确的,因为否则jenkins会立即产生错误)。

但是当我运行此管道时,出现如下错误:

groovy.lang.MissingPropertyException: No such property: pipeline for class: 
groovy.lang.Binding
at groovy.lang.Binding.getVariable(Binding.java:63)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.
SandboxInterceptor.onMethodCall(SandboxInterceptor.java:130)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155)
    at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159)
    at 
com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall
(SandboxInvoker.java:17)
    at WorkflowScript.run(WorkflowScript:1)
    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.
fixArg(FunctionCallBlock.java:82)
    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 
 com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive
 (ContinuationPtr.java:72)
    at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46)
    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:122)
     at org.codehaus.groovy.runtime.GroovyCategorySupport.use
(GroovyCategorySupport.java:261)
    at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101
(SandboxContinuable.java:34)
    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.
 lambda$run0$0(SandboxContinuable.java:59)
    at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.
runInSandbox(GroovySandbox.java:108)
    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0
(SandboxContinuable.java:58)
    at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk
(CpsThread.java:174)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run
(CpsThreadGroup.java:332)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200
(CpsThreadGroup.java:83)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call
(CpsThreadGroup.java:244)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call
(CpsThreadGroup.java:232)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call
(CpsVmExecutorService.java:64)
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

我对groovy并不陌生,但这似乎很奇怪。我试图遵循有关stackoverflow的其他问题,但没有帮助。

如果以前有人遇到过,您的指导会有所帮助,我们将不胜感激。

非常感谢, -潘卡吉

2 个答案:

答案 0 :(得分:3)

这似乎是“脚本安全插件1.45”的插件问题。 就我而言,该问题已通过将其更新为1.46得以解决。

答案 1 :(得分:0)

通过降级脚本安全性插件来修复此问题。您可以在“管理插件”中找到它。正如野原美彦子的回答。