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
Activity
Field | Original Value | New Value |
---|---|---|
Priority | Major [ 3 ] | Minor [ 4 ] |
Assignee | Vivek Pandey [ vivek ] |
Epic Link | JENKINS-35759 [ 171771 ] |
Description |
When there is a build which has a stage that marks the build as unstable, all the stages are marked incorrectly as unstable vs just the unstable stage. Expected action: only the stage that marked the build is unstable should return as such. 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). This is the same in stage view as well as stage graph incidentally. |
When there is a build which has a stage that marks the build as unstable, all the stages are marked incorrectly as unstable vs just the unstable stage. Expected action: only the stage that marked the build is unstable should return as such. 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). This is the same in stage view as well as stage graph incidentally. |
Sprint | indian [ 126 ] |
Rank | Ranked higher |
Sprint | indian [ 126 ] | arctic [ 131 ] |
Rank | Ranked lower |
Sprint | arctic [ 131 ] | tasman [ 136 ] |
Rank | Ranked lower |
Sprint | tasman [ 136 ] |
Rank | Ranked higher |
Sprint | tasman [ 136 ] |
Rank | Ranked lower |
Sprint | tasman [ 136 ] | indian [ 126 ] |
Rank | Ranked lower |
Link |
This issue blocks |
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Duplicate [ 3 ] | |
Status | Closed [ 6 ] | Reopened [ 4 ] |
Link |
This issue blocks |
Link |
This issue duplicates |
Link |
This issue relates to |
Sprint | indian [ 126 ] |
Assignee | Vivek Pandey [ vivek ] |
Component/s | pipeline [ 21692 ] | |
Component/s | blueocean-plugin [ 21481 ] |
Labels | blueocean |
Link |
This issue duplicates |
Resolution | Duplicate [ 3 ] | |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Link |
This issue duplicates |
Link |
This issue is blocked by |
Link |
This issue duplicates |
Link |
This issue relates to |
Resolution | Duplicate [ 3 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Component/s | blueocean-plugin [ 21481 ] | |
Component/s | pipeline [ 21692 ] |
Description |
When there is a build which has a stage that marks the build as unstable, all the stages are marked incorrectly as unstable vs just the unstable stage. Expected action: only the stage that marked the build is unstable should return as such. 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). This is the same in stage view as well as stage graph incidentally. |
NOTE this ticket is to track the linked blocking ticket for the blue ocean project. When there is a build which has a stage that marks the build as unstable, all the stages are marked incorrectly as unstable vs just the unstable stage. Expected action: only the stage that marked the build is unstable should return as such. 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). This is the same in stage view as well as stage graph incidentally. |
Description |
NOTE this ticket is to track the linked blocking ticket for the blue ocean project. When there is a build which has a stage that marks the build as unstable, all the stages are marked incorrectly as unstable vs just the unstable stage. Expected action: only the stage that marked the build is unstable should return as such. 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). This is the same in stage view as well as stage graph incidentally. |
*Problem* When there is a build which has a stage that marks the build as unstable, all the stages are marked incorrectly as unstable vs just the unstable stage. *Expected* only the stage that marked the build is unstable should return as such. *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). *NOTE this ticket is to track the linked blocking ticket for the blue ocean project* |
Description |
*Problem* When there is a build which has a stage that marks the build as unstable, all the stages are marked incorrectly as unstable vs just the unstable stage. *Expected* only the stage that marked the build is unstable should return as such. *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). *NOTE this ticket is to track the linked blocking ticket for the blue ocean project* |
*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 rather than just the unstable stage, parallel and step that caused the Pipeline to be unstable. *Expected* only the stage that marked the build is unstable should return as such. *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). *NOTE this ticket is to track the linked blocking ticket for the blue ocean project* |
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 rather than just the unstable stage, parallel and step that caused the Pipeline to be unstable. *Expected* only the stage that marked the build is unstable should return as such. *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). *NOTE this ticket is to track the linked blocking ticket for the blue ocean project* |
*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). *NOTE this ticket is to track the linked blocking ticket for the blue ocean project* |
Sprint | post-release [ 181 ] |
Rank | Ranked lower |
Rank | Ranked higher |
Sprint | post-release [ 181 ] | up next [ 171 ] |
Rank | Ranked lower |
Assignee | Vivek Pandey [ vivek ] |
Priority | Minor [ 4 ] | Critical [ 2 ] |
Link |
This issue is duplicated by |
Priority | Critical [ 2 ] | Minor [ 4 ] |
Priority | Minor [ 4 ] | Critical [ 2 ] |
Link |
This issue is duplicated by |
Sprint | up next [ 171 ] |
Sprint | 1.1 [ 251 ] |
Rank | Ranked higher |
Sprint | 1.1 [ 251 ] |
Rank | Ranked lower |
Rank | Ranked higher |
Priority | Critical [ 2 ] | Major [ 3 ] |
Priority | Major [ 3 ] | Minor [ 4 ] |
Priority | Minor [ 4 ] | Major [ 3 ] |
Link |
This issue relates to |
Epic Link | JENKINS-35759 [ 171771 ] | JENKINS-43952 [ 181484 ] |
Rank | Ranked higher |
Sprint | Blue Ocean 1.3 [ 311 ] |
Rank | Ranked lower |
Link |
This issue is blocked by |
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). *NOTE this ticket is to track the linked blocking ticket for the blue ocean project* |
{panel:title=Improvement on roadmap|titleBGColor=#3878de|titleColor=white} This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates. {panel} *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). *NOTE this ticket is to track the linked blocking ticket for the blue ocean project* |
Sprint | Blue Ocean 1.4 [ 311 ] | Blue Ocean 1.3 [ 296 ] |
Rank | Ranked lower |
Assignee | Vivek Pandey [ vivek ] | Andrew Bayer [ abayer ] |
Sprint | Blue Ocean 1.3 [ 296 ] | Blue Ocean 1.2-beta2 [ 341 ] |
Rank | Ranked lower |
Rank | Ranked higher |
Sprint | Blue Ocean 1.2-beta2 [ 341 ] | Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3 [ 341, 346 ] |
Link |
This issue relates to |
Sprint | Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3 [ 341, 346 ] | Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4 [ 341, 346, 361 ] |
Epic Link | JENKINS-43952 [ 181484 ] | JENKINS-45818 [ 184028 ] |
Link |
This issue is duplicated by |
Sprint | Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4 [ 341, 346, 361 ] | Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2-beta5 [ 341, 346, 361, 376 ] |
Sprint | Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2 [ 341, 346, 361, 376 ] | Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean 1.3 - beta 1 [ 341, 346, 361, 376, 386 ] |
Sprint | Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean 1.3 [ 341, 346, 361, 376, 386 ] | 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 [ 341, 346, 361, 376, 386, 401 ] |
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 [ 341, 346, 361, 376, 386, 401 ] | 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.4 - beta 2 [ 341, 346, 361, 376, 386, 401, 426 ] |
Labels | blueocean | blueocean testing-notes-reviewed |
Rank | Ranked higher |
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, Blue Ocean 1.4 - beta 2 [ 341, 346, 361, 376, 386, 401, 426 ] | 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 [ 341, 346, 361, 376, 386, 401 ] |
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 [ 341, 346, 361, 376, 386, 401 ] | 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.4 - beta 3 [ 341, 346, 361, 376, 386, 401, 416 ] |
Rank | Ranked higher |
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, Blue Ocean 1.4 - beta 3 [ 341, 346, 361, 376, 386, 401, 416 ] | 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 [ 341, 346, 361, 376, 386, 401 ] |
Rank | Ranked lower |
Remote Link | This issue links to "CloudBees Internal UX-663 (Web Link)" [ 18181 ] |
Remote Link | This issue links to "CloudBees Internal UX-663 (Web Link)" [ 18291 ] |
Description |
{panel:title=Improvement on roadmap|titleBGColor=#3878de|titleColor=white} This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates. {panel} *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). *NOTE this ticket is to track the linked blocking ticket for the blue ocean project* |
{panel:title=Improvement on roadmap|titleBGColor=#3878de|titleColor=white} This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates. {panel} *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). |
Link |
This issue is duplicated by |
Link |
This issue is duplicated by |
Description |
{panel:title=Improvement on roadmap|titleBGColor=#3878de|titleColor=white} This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates. {panel} *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). |
{panel:title=Improvement on roadmap|titleBGColor=#3878de} This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates. {panel} *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). |
Attachment | overall-success-but-some-stages-marked-as-red.png [ 41933 ] |
Assignee | Andrew Bayer [ abayer ] | |
Description |
{panel:title=Improvement on roadmap|titleBGColor=#3878de} This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates. {panel} *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). |
*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). |
Priority | Major [ 3 ] | Critical [ 2 ] |
Link |
This issue relates to |
Link | This issue is related to JENKINS-53889 [ JENKINS-53889 ] |
Link | This issue is related to JENKINS-53889 [ JENKINS-53889 ] |
Attachment | example-on-how-to-mark-unstable-stages-as-visually-failed-in-stage-overview.png [ 45087 ] |
Link |
This issue is duplicated by |
Attachment | image-2019-02-28-17-32-28-257.png [ 46214 ] |
Attachment | allYellow.jpg [ 46525 ] |
Component/s | pipeline [ 21692 ] | |
Component/s | blueocean-plugin [ 21481 ] |
Released As | Pipeline: API 2.34, Pipeline: Basic Steps 2.16, Pipeline: Graph Analysis 1.10, JUnit: 1.28 |
Remote Link | This issue links to "jenkinsci/pipeline-graph-analysis-plugin#25 (Web Link)" [ 22910 ] |
Remote Link | This issue links to "jenkinsci/workflow-api-plugin#91 (Web Link)" [ 22911 ] |
Remote Link | This issue links to "jenkinsci/workflow-basic-steps-plugin#83 (Web Link)" [ 22912 ] |
Remote Link | This issue links to "jenkinsci/blueocean-plugin#1954 (Web Link)" [ 22913 ] |
Remote Link | This issue links to "jenkinsci/warnings-ng-plugin#58 (Web Link)" [ 22914 ] |
Remote Link | This issue links to "jenkinsci/junit-plugin#118 (Web Link)" [ 22915 ] |
Assignee | Devin Nusbaum [ dnusbaum ] |
Status | Reopened [ 4 ] | In Progress [ 3 ] |
Attachment | image-2019-05-17-16-18-02-806.png [ 47404 ] |
Attachment | screenshot-not-showing-unstable-stage.png [ 47405 ] |
Link |
This issue is duplicated by |
Released As | Pipeline: API 2.34, Pipeline: Basic Steps 2.16, Pipeline: Graph Analysis 1.10, JUnit: 1.28 | 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 |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Link |
This issue relates to |
Link | This issue causes JENKINS-58085 [ JENKINS-58085 ] |
Link | This issue causes JENKINS-58085 [ JENKINS-58085 ] |
Link | This issue is related to JENKINS-58783 [ JENKINS-58783 ] |
Link |
This issue relates to |
Link | This issue is related to JENKINS-27092 [ JENKINS-27092 ] |
A sample response json is:
This is the first stage, which should have succeeded.