JenkinsIcon indicating the project type

Jenkins

Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39203

All stages show up as UNSTABLE when only one stage should

    Details

    • 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

      1. Build the multibranch pipeline "kzantow/failure-project" from github
      2. Look at the "michaelneale" branch
      3. 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

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-26522 Annotated block/stage status

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-43995 Individual Pipeline steps and stages/blocks should have Result statuses

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-45871 Failed test sets all steps to unstable

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Reopened

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-48673 Nodes status are not displayed correctly after aborting an input step

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-48771 blue ocean not recognizing status change from test evaluation

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-49778 If one stage in the pipeline fails, all the states are marked/color with the same status color

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-56683 Declarative Pipeline: set the build result when tests fail without a script block

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-53889 Support post conditions that accept a range of stage statuses

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-53889 Support post conditions that accept a range of stage statuses

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-58783 Update pipeline stage-view-plugin to use the new WarningAction API

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-26523 Allow yellow "unstable" state from a step

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-60426 All stages show up as UNSTABLE when one stage is unstable

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-58554 Workflow parse exception with new approach for unstable stages

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-43292 The failed parallel build step should be focused and aborted when failFast

          • Major - Major loss of function.
          • Fixed but Unreleased

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-45579 Step to set stage or parallel status

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          links to

          Web Link CloudBees Internal UX-663

          Web Link CloudBees Internal UX-663

          Web Link jenkinsci/blueocean-plugin#1954

          Web Link jenkinsci/junit-plugin#118

          Web Link jenkinsci/pipeline-graph-analysis-plugin#25

          Web Link jenkinsci/warnings-ng-plugin#58

          Web Link jenkinsci/workflow-api-plugin#91

          Web Link jenkinsci/workflow-basic-steps-plugin#83

            Activity

            Ascending order - Click to sort in descending order
            83 older comments
            Hide
            Permalink
            cburroughs Chris Burroughs added a comment -

            The visualization provided by Pipeline: Stage View Plugin has not been integrated with the new API added in Pipeline: API 2.34, and so that visualization is not currently affected by these changes.

            I looked but could not find one; is the intention to have a separate ticket for the Stage View plugin integration?

            Show
            cburroughs Chris Burroughs added a comment - The visualization provided by Pipeline: Stage View Plugin has not been integrated with the new API added in Pipeline: API 2.34, and so that visualization is not currently affected by these changes. I looked but could not find one; is the intention to have a separate ticket for the Stage View plugin integration?
            Hide
            Permalink
            dnusbaum Devin Nusbaum added a comment -

            I just published a blog post with an overview of this issue and how to take advantage of the recent changes in your Pipeline to improve the way it is visualized in Blue Ocean: https://jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/. 

            Chris Burroughs Yes, feel free to open a new issue for Stage View integration and link it to this one.

            Show
            dnusbaum Devin Nusbaum added a comment - I just published a blog post with an overview of this issue and how to take advantage of the recent changes in your Pipeline to improve the way it is visualized in Blue Ocean:  https://jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/ .  Chris Burroughs Yes, feel free to open a new issue for Stage View integration and link it to this one.
            Hide
            Permalink
            dnusbaum Devin Nusbaum added a comment -

            Given the core changes have been released, I am closing this issue. As noted in my blog post, if you are still having problems with a Pipeline step from specific please file a new issue with the component set to that plugin (after checking for duplicates), clearly describing which step has the problem and under what circumstances it occurs, and link to the developers section of the post as a reference for how the maintainer might be able to address the problem.
             

            Show
            dnusbaum Devin Nusbaum added a comment - Given the core changes have been released, I am closing this issue. As noted in my blog post, if you are still having problems with a Pipeline step from specific please  file a new issue  with the component set to that plugin (after checking for duplicates), clearly describing which step has the problem and under what circumstances it occurs, and link to the developers section of the post  as a reference for how the maintainer might be able to address the problem.  
            Hide
            Permalink
            jonhattan Jonathan Araña Cruz added a comment -

            Just created the issue for Pipeline: Stage View Plugin -> https://issues.jenkins-ci.org/browse/JENKINS-58783

            Show
            jonhattan Jonathan Araña Cruz added a comment - Just created the issue for Pipeline: Stage View Plugin -> https://issues.jenkins-ci.org/browse/JENKINS-58783
            Hide
            Permalink
            v3vinvin Vincent Yan added a comment - - edited

            Thanks for the hard work. I've just recently started to use Jenkins but on a older version. Then came along this issue while I was googling about the stage result issue. Glad there's already a solution in the recent version!  Appreciate it!

            Show
            v3vinvin Vincent Yan added a comment - - edited Thanks for the hard work. I've just recently started to use Jenkins but on a older version. Then came along this issue while I was googling about the stage result issue. Glad there's already a solution in the recent version!   Appreciate it!

              People

              • Assignee:
                dnusbaum Devin Nusbaum
                Reporter:
                michaelneale Michael Neale
              • Votes:
                233 Vote for this issue
                Watchers:
                237 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: