2017-03-10 201 views
0

我正在尝试使用Jenkins管道sh命令的returnStdout功能。这里https://jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#code-sh-code-shell-scriptJenkins管道sh returnstdout不工作

定义从以前的问题和答案拉:Is it possible to capture the stdout from the sh DSL command in the pipeline

我的原代码:

node{ 
def output = sh(returnStdout: true, script: 'pwd') 
println "output = ${output}" 
} 

和它的结果。你可以看到,我正在退出代码,而不是传递到我的变量结果:

[Pipeline] node { 
[Pipeline] sh 
[Update_Stageing_DB] Running shell script 
+ pwd 
/mnt/storage/jenkins/workspace/Update_Stageing_DB 
[Pipeline] echo 
output = 0 
[Pipeline] } //node 
[Pipeline] Allocate node : End 
[Pipeline] End of Pipeline 
Finished: SUCCESS 

基础上我想我可能需要添加.trim(),所以我更新的代码看起来像这样的例子:

node{ 
def output = sh(returnStdout: true, script: 'pwd').trim() 
println "output = ${output}" 
} 

但是,这会导致整个任务失败:

[Pipeline] node { 
[Pipeline] sh 
[Update_Stageing_DB] Running shell script 
+ pwd 
/mnt/storage/jenkins/workspace/Update_Stageing_DB 
[Pipeline] } //node 
[Pipeline] Allocate node : End 
[Pipeline] End of Pipeline 
hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: java.lang.Integer.trim() is applicable for argument types:() values: [] 
Possible solutions: wait(), grep(), wait(long), times(groovy.lang.Closure), div(java.lang.Character), print(java.io.PrintWriter) 
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:15) 
at WorkflowScript.run(WorkflowScript:3) 
at ___cps.transform___(Native Method) 
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55) 
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) 
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixName(FunctionCallBlock.java:74) 
at sun.reflect.GeneratedMethodAccessor771.invoke(Unknown Source) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:606) 
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) 
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) 
at com.cloudbees.groovy.cps.Next.step(Next.java:58) 
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) 
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) 
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:277) 
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:77) 
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:186) 
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:184) 
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) 
at java.util.concurrent.FutureTask.run(FutureTask.java:262) 
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) 
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
at java.util.concurrent.FutureTask.run(FutureTask.java:262) 
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at java.lang.Thread.run(Thread.java:745) 
Finished: FAILURE 

我敢肯定,我失去了一些基本的东西,但对我的生活我不能看到什么是错用这个简单的代码。任何帮助,将不胜感激。

Jenkins ver。 2.32.2

回答

1

方法的无签名:java.lang.Integer.trim()是适用

该错误消息表示sh步骤返回一个数值。
对我而言,只有在sh步骤调用中使用returnStatus参数而不是returnStdout时才会发生这种情况。

确保您的插件是最新的,并且您使用的是正确的参数;例如,如果您正在从远程SCM加载管道,则可以使用任何生成页上边栏中的“重播”链接来查看确切加载了哪些管道脚本。另外,如果您真的只需要在shell步骤中运行pwd,则可以使用“管道”步骤简化一点。

+0

感谢您的回答。你钉了它。我的插件需要更新,我将Pipeline更新为2.5及其依赖项,现在我的第二个代码片段使用.trim(),按预期工作。 –