UPDATE:这似乎是在Pipeline: Declarative插件版本1.3.5中引入的一个bug --降级到1.3.4.1解决了这个问题。票证创建于:
在远程执行程序上使用时,如何获得构建的真实状态?
进退两难:
currentBuild.result为NULL,currentBuild.currentResult为成功当在远程执行程序上执行生成时,如何访问实际的失败?
代码视图:
pipeline {
agent any
stages {
stage("test run") {
steps {
sh "exit 1"
}
}
}
post {
always {
echo "I always run: ${currentBuild.result} <> ${currentBuild.currentResult}"
}
success {
echo "I'm successful: ${currentBuild.result} <> ${currentBuild.currentResult}"
}
failure {
echo "I failed: ${currentBuild.result} <> ${currentBuild.currentResult}"
}
fixed {
echo "I'm fixed!: ${currentBuild.result} <> ${currentBuild.currentResult}"
}
}
}以及产出:
[Pipeline] Start of Pipeline
[Pipeline] node
Running on build-096575a3-e6af-4fff-9ca1-84cc46ba4b86-f9b8d29c in /var/vcap/data/jenkins-slave/workspace/test-job
[Pipeline] {
[Pipeline] stage
[Pipeline] { (test run)
[Pipeline] sh
+ exit 1
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] echo
I always run: null <> SUCCESS
[Pipeline] echo
I failed: null <> SUCCESS
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE发布于 2019-03-08 16:18:19
(就我的问题发表“正式答复”):
这是在Pipeline: Declarative插件版本1.3.5中引入的"bug“--降级到1.3.4.1解决了这个问题。票证创建于:
对于这是否真的是一个bug,用户和开发人员之间还有四分之一的问题。devs建议不要再使用currentBuild.result了,但是很多人都指出这是BC中断,造成了很多问题。
问题已标记为Critical --可能会被回滚或重新开发以更好地实现。
如果您依赖这个特性,无论是currentBuild.result还是currentBuild.currentResult,我建议您在这个bug上发表评论。
发布于 2020-01-21 08:31:18
您可以使用“尝试捕捉”:
try {
sh "exit 1"
currentBuild.result = 'SUCCESS'
}catch (Exception err) {
currentBuild.result = 'FAILURE'
}https://stackoverflow.com/questions/54992368
复制相似问题