Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: pipeline
-
Labels:
-
Similar Issues:
-
Epic Link:
-
Sprint:Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean 1.3, Blue Ocean 1.4 - beta 1
-
Released As:Blue Ocean 1.17.0, Pipeline: API 2.34, Pipeline: Basic Steps 2.18, Pipeline: Graph Analysis 1.10, Pipeline: Groovy 2.70, Pipeline: Declarative 1.3.9, JUnit: 1.28, Warnings Next Generation 5.2.0
Description
Problem
When there is a build which has a stage that marks the build as unstable, all the stages, parallels and steps are marked incorrectly as unstable than just the unstable stage, parallel and step that caused the Pipeline to be unstable.
To reproduce
- Build the multibranch pipeline "kzantow/failure-project" from github
- Look at the "michaelneale" branch
- Note that all stages are unstable (check the api json, all stages are UNSTABLE but should not be, only the final stage should be).
Attachments
Issue Links
- is blocked by
-
JENKINS-26522 Annotated block/stage status
-
- Closed
-
-
JENKINS-43995 Individual Pipeline steps and stages/blocks should have Result statuses
-
- Resolved
-
- is duplicated by
-
JENKINS-48673 Nodes status are not displayed correctly after aborting an input step
-
- Closed
-
-
JENKINS-45871 Failed test sets all steps to unstable
-
- Closed
-
-
JENKINS-48771 blue ocean not recognizing status change from test evaluation
-
- Closed
-
-
JENKINS-49778 If one stage in the pipeline fails, all the states are marked/color with the same status color
-
- Closed
-
-
JENKINS-56683 Declarative Pipeline: set the build result when tests fail without a script block
-
- Closed
-
- is related to
-
JENKINS-53889 Support post conditions that accept a range of stage statuses
-
- Open
-
-
JENKINS-27092 create a step to abort the build with a NOT_BUILT status
-
- Reopened
-
-
JENKINS-53889 Support post conditions that accept a range of stage statuses
-
- Open
-
-
JENKINS-58783 Update pipeline stage-view-plugin to use the new WarningAction API
-
- Open
-
- relates to
-
JENKINS-26523 Allow yellow "unstable" state from a step
-
- Resolved
-
-
JENKINS-60426 All stages show up as UNSTABLE when one stage is unstable
-
- Resolved
-
-
JENKINS-58554 Workflow parse exception with new approach for unstable stages
-
- Closed
-
-
JENKINS-45579 Step to set stage or parallel status
-
- Resolved
-
-
JENKINS-43292 The failed parallel build step should be focused and aborted when failFast
-
- Resolved
-
- links to
Was this more than just a visualisation problem or was this actually making stage B run it's post->unstable steps if stage A was UNSTABLE and set the overall build status to UNSTABLE? Because that would be very bad/wrong.