-
Story
-
Resolution: Duplicate
-
Major
Solution
- Fold in steps to their nearest stage so that they appear in the step list
- When
JENKINS-39658is fixed the error log will be appended to the step
Original request
Blue ocean shows parallel branches as separate "nodes" (circles) on the stage graph.
This means that if a build failure happens outside of a parallel branch, you end up with all green circles but a failed build.
See the attached 
This is for the simple pipeline:
node {
stage('first') {
sh "echo 42"
}
stage('par') {
parallel(
"left" : {
sh "echo 42"
},
"right" : {
sh "echo 43"
}
)
error "it's all bad"
}
}
What this should do:
if there are steps outside of parallel branches, show them as a node (circle) directly under the stage name (and if any steps fail, that node shows as failed).
- duplicates
-
-
- Closed
-
- is blocked by
-
JENKINS-39658 Include failed step's error to it's log
-
- Closed
-
- links to
[JENKINS-39335] If a failure happens outside of parallel branch it isn't shown in a stage
| Epic Link | New: JENKINS-35750 [ 171713 ] |
| Assignee | New: James Dumay [ jamesdumay ] |
hrmpw jglick michaelneale IMO currentBuild.result = "FAILURE" is not an idiomatic way of failing the Pipeline. A step would be more appropriate and we would be able to tie this failure to a specific flow node. Would appreciate your thoughts here.
node {
stage('first') {
sh "echo 42"
}
stage('par') {
parallel(
"left" : {
sh "echo 42"
},
"right" : {
sh "echo 43"
}
)
...
fail("The reason the pipeline failed")
...
}
| Description |
Original:
Blue ocean shows parallel branches as separate "nodes" (circles) on the stage graph. This means that if a build failure happens outside of a parallel branch, you end up with all green circles but a failed build. See the attached !Screen Shot 2016-10-28 at 10.06.00 am.png|thumbnail! This is for the simple pipeline: {noformat} node { stage('first') { sh "echo 42" } stage('par') { parallel( "left" : { sh "echo 42" }, "right" : { sh "echo 43" } ) currentBuild.result = "FAILURE" } } {noformat} |
New:
Blue ocean shows parallel branches as separate "nodes" (circles) on the stage graph. This means that if a build failure happens outside of a parallel branch, you end up with all green circles but a failed build. See the attached !Screen Shot 2016-10-28 at 10.06.00 am.png|thumbnail! This is for the simple pipeline: {noformat} node { stage('first') { sh "echo 42" } stage('par') { parallel( "left" : { sh "echo 42" }, "right" : { sh "echo 43" } ) error "it's all bad" } } {noformat} |
| Description |
Original:
Blue ocean shows parallel branches as separate "nodes" (circles) on the stage graph. This means that if a build failure happens outside of a parallel branch, you end up with all green circles but a failed build. See the attached !Screen Shot 2016-10-28 at 10.06.00 am.png|thumbnail! This is for the simple pipeline: {noformat} node { stage('first') { sh "echo 42" } stage('par') { parallel( "left" : { sh "echo 42" }, "right" : { sh "echo 43" } ) error "it's all bad" } } {noformat} |
New:
Blue ocean shows parallel branches as separate "nodes" (circles) on the stage graph. This means that if a build failure happens outside of a parallel branch, you end up with all green circles but a failed build. See the attached !Screen Shot 2016-10-28 at 10.06.00 am.png|thumbnail! This is for the simple pipeline: {noformat} node { stage('first') { sh "echo 42" } stage('par') { parallel( "left" : { sh "echo 42" }, "right" : { sh "echo 43" } ) error "it's all bad" } } {noformat} What this should do: if there are steps outside of parallel branches, show them as a node (circle) directly under the stage name (and if any steps fail, that node shows as failed). |
I have corrected this example as my example was too contrived (and probably not wrong).
If you use the error step, then you get a more valid version of this problem, I have corrected my example.
| Assignee | Original: James Dumay [ jamesdumay ] |
| Summary | Original: If a failure happens outside of parallel branch show all nodes as failed | New: If a failure happens outside of parallel branch it isn't shown in a stage |
cc jamesdumay we don't have a place to put failures like this to show the stage failed. Could we just show the branches as failed to make it clear where things went kaput? Or perhaps fail the stage text somehow?