Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: pipeline-model-definition-plugin
-
Labels:
-
Environment:Jenkins: 2.164.3
Pipeline: Basic Steps: 2.16
-
Similar Issues:
Description
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?
Attachments
Issue Links
- relates to
-
JENKINS-45579 Step to set stage or parallel status
-
- Resolved
-
- links to
Activity
Brian J Murrell
created issue -
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue relates to |
| Labels | pipeline |
| Component/s | pipeline-model-definition-plugin [ 21706 ] | |
| Component/s | pipeline [ 21692 ] |
| Assignee | Andrew Bayer [ abayer ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | In Review [ 10005 ] |
| Remote Link | This issue links to "PR #330 (Web Link)" [ 23053 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Review [ 10005 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |