To ignore a failed step in declarative pipeline you basically have two options:
- Use
script
step and try-catch
block (similar to previous proposition by R_K but in declarative style)
stage('someStage') {
steps {
script {
try {
build job: 'system-check-flow'
} catch (err) {
echo err.getMessage()
}
}
echo currentBuild.result
}
}
- Use
catchError
stage('someStage') {
steps {
catchError {
build job: 'system-check-flow'
}
echo currentBuild.result
}
}
In both cases the build won't be aborted upon exception in build job: 'system-check-flow'
. In both cases the echo
step (and any other following) will be executed.
But there's one important difference between these two options. In first case if the try
section raises an exception the overall build status won't be changed (so echo currentBuild.result
=> SUCCESS
). In the second case you overall build will fail (so echo currentBuild.result
=> FAILURE
).
This is important, because you can always fail the overall build in first case (by setting currentBuild.result = 'FAILURE'
) but you can't repair build in second option (currentBuild.result = 'SUCCESS'
won't work).
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…