-
Bug
-
Resolution: Fixed
-
Critical
-
-
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
-
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
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).
- 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-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-57801 Execution of post stage block is based on pipeline status, not stage result which docs says it should
-
- Open
-
-
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
I'm failing to understand how this issue is any less than Critical. It completely invalidates the result of any and every pipeline job run that has even the smallest subset of stage failures. The problem even propagates outside of Jenkins and Blue Ocean as it leads to other plugins such as the Pipeline Githubnotify Step Plugin incorrectly setting FAILURE status on GitHub PR commit statuses set from stages in the pipeline.
This issue leads to developers having to waste time and drive up frustration having to hunt through the stages of their pipeline job runs to figure out which stage actually did fail.
Additionally, it's really disheartening to see that this issue is only as far as Planned on the Blue Ocean Roadmap. Surely the 116 (or more) votes and 143 (or more) watchers on this issue demonstrates how important it is for a lot of people. Other items on the roadmap that are In Progress even, such as JENKINS-44699 don't have anywhere near as many votes and/or watchers.
Is there any ETA, no matter how much of guesstimate it is, available as to how long this issue will take to be fixed?