-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Component/s: blueocean-plugin
-
Labels:None
-
Environment:Jenkins 2.89
Blue Ocean 1.35
Pipeline Graph Analysis Plugin 1.6
-
Similar Issues:
-
Epic Link:
-
Sprint:Blue Ocean 1.5 - beta 3
Related to JENKINS-47219
Problem
When running a pipeline with parallel stages, the state of those stages is incorrectly displayed when a previous one has failed.
JenkinsFile
pipeline { agent any stages { stage('Run Tests') { steps { bat 'exit 1' } } stage('Deploy') { parallel { stage('Dev') { when { branch 'master' } steps { echo 'hello master' } } stage('QA') { steps { echo 'hello stable' } } } } } }
Log output:
First time build. Skipping changelog. [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Run Tests) [Pipeline] bat [parallel-stage-complete-bug-JNC4NY4S375GSWLOMCSNQAMH4OIZKQT7UCEAS4OYPXLQVHI6A3XA] Running batch script C:\...>exit 1 [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy) Stage 'Deploy' skipped due to earlier failure(s) [Pipeline] parallel [Pipeline] [Dev] { (Branch: Dev) [Pipeline] [QA] { (Branch: QA) [Pipeline] [Dev] stage [Pipeline] [Dev] { (Dev) [Pipeline] [QA] stage [Pipeline] [QA] { (QA) Stage 'Dev' skipped due to earlier failure(s) Stage 'QA' skipped due to earlier failure(s) [Pipeline] [Dev] } [Pipeline] [QA] } [Pipeline] [Dev] // stage [Pipeline] [QA] // stage [Pipeline] [Dev] } [Pipeline] [QA] } [Pipeline] // parallel [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE
This gives the following output:
Result when the pipe is successful:
(Changing the exit 1 to exit 0)
FYI: Cliff Meyers
- is duplicated by
-
JENKINS-50399 Skipped steps show as passed - plugins uptodate but still nothing
-
- Closed
-
- links to
Field | Original Value | New Value |
---|---|---|
Epic Link | JENKINS-43953 [ 181485 ] |
Description |
Related to *Problem* When running a pipeline with parallel stages, the state of those stages is incorrectly displayed when a previous one has failed. *JenkinsFile* {code:java} pipeline { agent { node { label 'itc-nodes' } } stages { stage('Run Tests') { steps { bat 'exit 1' } } stage('Deploy') { parallel { stage('Dev') { when { branch 'master' } steps { echo 'hello master' } } stage('QA') { steps { echo 'hello stable' } } } } } } {code} *Log output*: {code:java} First time build. Skipping changelog. [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Run Tests) [Pipeline] bat [parallel-stage-complete-bug-JNC4NY4S375GSWLOMCSNQAMH4OIZKQT7UCEAS4OYPXLQVHI6A3XA] Running batch script C:\...>exit 1 [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy) Stage 'Deploy' skipped due to earlier failure(s) [Pipeline] parallel [Pipeline] [Dev] { (Branch: Dev) [Pipeline] [QA] { (Branch: QA) [Pipeline] [Dev] stage [Pipeline] [Dev] { (Dev) [Pipeline] [QA] stage [Pipeline] [QA] { (QA) Stage 'Dev' skipped due to earlier failure(s) Stage 'QA' skipped due to earlier failure(s) [Pipeline] [Dev] } [Pipeline] [QA] } [Pipeline] [Dev] // stage [Pipeline] [QA] // stage [Pipeline] [Dev] } [Pipeline] [QA] } [Pipeline] // parallel [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE {code} This gives the following output: !failed-pipe-shows-skipped-as-green.png! Result when the pipe is successful: (Changing the exit 1 to exit 0) !success-pipe-run-with-skipped-stage.png! FYI: [~cliffmeyers] |
Related to - *Problem* When running a pipeline with parallel stages, the state of those stages is incorrectly displayed when a previous one has failed. *JenkinsFile* {code:java} pipeline { agent any stages { stage('Run Tests') { steps { bat 'exit 1' } } stage('Deploy') { parallel { stage('Dev') { when { branch 'master' } steps { echo 'hello master' } } stage('QA') { steps { echo 'hello stable' } } } } } } {code} *Log output*: {code:java} First time build. Skipping changelog. [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Run Tests) [Pipeline] bat [parallel-stage-complete-bug-JNC4NY4S375GSWLOMCSNQAMH4OIZKQT7UCEAS4OYPXLQVHI6A3XA] Running batch script C:\...>exit 1 [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy) Stage 'Deploy' skipped due to earlier failure(s) [Pipeline] parallel [Pipeline] [Dev] { (Branch: Dev) [Pipeline] [QA] { (Branch: QA) [Pipeline] [Dev] stage [Pipeline] [Dev] { (Dev) [Pipeline] [QA] stage [Pipeline] [QA] { (QA) Stage 'Dev' skipped due to earlier failure(s) Stage 'QA' skipped due to earlier failure(s) [Pipeline] [Dev] } [Pipeline] [QA] } [Pipeline] [Dev] // stage [Pipeline] [QA] // stage [Pipeline] [Dev] } [Pipeline] [QA] } [Pipeline] // parallel [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE {code} This gives the following output: !failed-pipe-shows-skipped-as-green.png! Result when the pipe is successful: (Changing the exit 1 to exit 0) !success-pipe-run-with-skipped-stage.png! FYI: [~cliffmeyers] |
Assignee | Nicolae Pascu [ nicu ] |
Sprint | Blue Ocean 1.5 - beta 3 [ 491 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Link |
This issue is duplicated by |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Remote Link | This issue links to "#1702 (Web Link)" [ 20337 ] |
Status | In Review [ 10005 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] |
hey Vivek Pandey a few people have picked this one up of late - might be worth looking into - should have been fixed as part of https://issues.jenkins-ci.org/browse/JENKINS-47219 but looks like a regression