Kalle Niemitalo added a comment - 2022-04-19 05:58 I unsuccessfully tried to reproduce the problem with this pipeline: pipeline { agent none stages { stage( 'First' ) { steps { unstable 'Excuse' script { currentBuild.result = 'SUCCESS' echo "got ${currentBuild.result}" } } post { unstable { echo 'First post unstable' } } } stage( 'Second' ) { steps { echo 'Second main' } post { success { echo 'Second post success' } unstable { echo 'Second post unstable' } } } } } I expected that the first stage would set the stage result as UNSTABLE but the build result as SUCCESS, and the bug would cause BuildCondition.meetsCondition to consider only the build result and not the stage result. It would then return false, ModelInterpreter.runPostConditions would not be called, and "First post unstable" would not be output. However, the log from this pipeline was: [Pipeline] Start of Pipeline [Pipeline] stage [Pipeline] { (First) [Pipeline] unstable WARNING: Excuse [Pipeline] script [Pipeline] { [Pipeline] echo got UNSTABLE [Pipeline] } [Pipeline] // script Post stage [Pipeline] echo First post unstable [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Second) [Pipeline] echo Second main Post stage [Pipeline] echo Second post unstable [Pipeline] } [Pipeline] // stage [Pipeline] End of Pipeline Finished: UNSTABLE Somehow, the currentBuild.result = 'SUCCESS' assignment did not seem to take effect.