[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true

[dp...@luxoft.com (JIRA)]

Title: Message Title

Daniel Puiu created an issue   Jenkins / JENKINS-60239 Aborted catchError sets build result to ABORTED if fail fast is true Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2019-11-21 10:56 Environment: Jenkins: 2.164.3 Pipeline: Basic Steps: 2.16 Labels: pipeline Priority: Critical Reporter: Daniel Puiu If I have a stage with a step in it:   ...   catchError(buildResult: hudson.model.Result.SUCCESS, message: 'RPM build failed, but allowing job to continue', stageResult: hudson.model.Result.FAILURE) { sh label: env.STAGE_NAME, script: 'exit 2' } With a post block for the stage: post { always { archiveArtifacts artifacts: 'artifacts/**' } success { println "${env.STAGE_NAME}: SUCCESS" } unstable { println "${env.STAGE_NAME}: UNSTABLE" } failure { println "${env.STAGE_NAME}: FAILED" } }  I actually get the: My Test Stage: SUCCESS telling me that the stage was a SUCCESS, not a FAILURE like the: catchError(..., stageResult: hudson.model.Result.FAILURE) is supposed to be making it. In both the stage view and the Blue Ocean view, it does show as a failed stage. The post processing block just doesn't see it that way. As an aside, is there a variable set for the stage that I could use in my println above so that I could just do a single println in the always block rather than having to repeat it through the success, unstable and failure blocks? Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203219.1574333797000.4902.1574333820348%40Atlassian.JIRA.