我的管道中的一个步骤将.tar上传到artifactory服务器.传入env.BUILD_NUMBER时收到错误的替换错误,但是当数字被硬编码时,相同的命令也会起作用.该脚本通过jenkins以groovy编写,并在jenkins工作区中运行.
sh 'curl -v --user user:password --data-binary ${buildDir}package${env.BUILD_NUMBER}.tar -X PUT "http://artifactory.mydomain.com/artifactory/release-packages/package${env.BUILD_NUMBER}.tar"'
返回错误:
[Pipeline] sh
[Package_Deploy_Pipeline] Running shell script
/var/lib/jenkins/workspace/Package_Deploy_Pipeline@tmp/durable-4c8b7958/script.sh: 2:
/var/lib/jenkins/workspace/Package_Deploy_Pipeline@tmp/durable-4c8b7958/script.sh: Bad substitution
[Pipeline] } //node
[Pipeline] Allocate node : End
[Pipeline] End of Pipeline
ERROR: script returned exit code 2
如果构建号中的硬代码和换出${env.BUILD_NUMBER}我没有错误,代码运行成功.
sh 'curl -v --user user:password --data-binary ${buildDir}package113.tar -X PUT "http://artifactory.mydomain.com/artifactory/release-packages/package113.tar"'
我在同一个脚本中的其他sh命令中使用$ {env.BUILD_NUMBER},并且在任何其他地方都没有问题.
我有一个管道,我的团队正在使用它来启动云VM并为它们部署软件堆栈.此过程的一部分是将工件与他们选择的构建捆绑在一起.现在我只是抓住上面列出的工作的最后成功,但是我已经遇到了在管道可以创建其捆绑包之前在另一个流程中再次构建该工作的问题,使得捆绑包抓住了使用错误的依赖关系构建的工件.
def DeployModule(jobName, jobBranch, serverHostName, database){
build job: jobName, parameters: [[$class: 'StringParameterValue', name: 'Branch', value: jobBranch], [$class: 'StringParameterValue', name: 'DatabaseAction', value: database], [$class: 'StringParameterValue', name: 'Profile', value: serverHostName]]
println "$jobName Succesfull"
}
有没有办法改变我的简单构建作业方法来拉出触发的实际构建号？管道控制台打印创建的构建号,我不知道如何在我的groovy代码中获取它.
[Pipeline] build (Building tms-auto-build)
Scheduling project: tms-auto-build
Starting building: tms-auto-build #298
我正在尝试使用 Jenkins 管道 sh 命令的 returnStdout 功能。此处定义https://jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#code-sh-code-shell-script
从之前的问题和答案中提取：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: …我正在使用Jenkins v:1.647和Pipeline插件v:1.14.我的管道工作提取了一个运行我的业务流程的groovy脚本.我的问题是我有一个可执行jar,它将执行一些Scalr API操作并返回一个新的服务器主机名,在标准输出中传递.我有一个在Jenkins之外工作的工作片段.
def serverHostName = "java -jar scalr-api.jar testing654 n1-standard-8".execute().text
这段代码在Jenkins之外工作正常,但我的问题是在运行我的管道时遇到了令人烦恼的RejectedAccessException.But与其他脚本安全例外不同,我没有选择批准相关方法.
我正在寻找任何可以通过脚本安全性的解决方案,并允许我运行该jar并获得标准,以便稍后在我的脚本中使用
谢谢
詹金斯错误:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.UNIXProcess getText
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:74)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15)
at WorkflowScript.run(WorkflowScript:97)
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.GeneratedMethodAccessor291.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.SandboxContinuable.access$001(SandboxContinuable.java:19)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:106)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)
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) …