-
Improvement
-
Resolution: Duplicate
-
Minor
-
jenkins 2.64
blue ocean 1.0.1
With the following pipeline:
stage("begin") { println "begin" } parallel ( "no_stage": { println "no stage" }, "": { println "no name" }, "with_stage": { stage("my_stage") { println "named stage" } } ) stage("end") { println "end" }
we are getting the following display in BlueOcean:
But in the parallel step, only the third branch has a stage defined, and therefore only this one is expected to be displayed. Unfortunately all the branches are displayed even if not containing any stage.
Additionally, the name displayed for the third branch is the branch name instead of the stage name as one would have thought.
On the other hand, in the Pipeline view it is displayed as expected:
Use case: technical steps which need to run in parallel to maintain shared resources, advance timeout monitoring, etc ... doesn't have to pollute the Blue Ocean view.
May be possible to add a boolean option to the parallel step not to use branch name as default display name in Blue Ocean, and eventually make branch with no stage invisible ?
- duplicates
-
JENKINS-47799 Blue Ocean shouldn't visualize the parallel keyword of a scripted pipeline directly
-
- Open
-
- is related to
-
JENKINS-38442 View sequential stages in the pipeline visualization graph
-
- Closed
-
- mentioned in
-
Page Failed to load
[JENKINS-44820] Parallel branches with no stage should not be displayed in Blue Ocean
Description |
Original:
With the following pipeline: {code:java} stage("begin") { println "begin" } parallel ( "no_stage": { println "no stage" }, "": { println "no name" }, "with_stage": { stage("my_stage") { println "named stage" } } ) stage("end") { println "end" } {code} we are getting the following display in BlueOcean: !blueocean.png! But in the parallel step, only the third step as a *stage* defined, and therefore only this one is expected to be displayed. Unfortunately all the branches are displayed even if not containing any stage Typically in the Pipeline view it is displayed as expected: !stages.png! Use case: technical steps which need to run in parallel to maintain shared resources, advance timeout monitoring, etc ... doesn't have to pollute the Blue Ocean view. |
New:
With the following pipeline: {code:java} stage("begin") { println "begin" } parallel ( "no_stage": { println "no stage" }, "": { println "no name" }, "with_stage": { stage("my_stage") { println "named stage" } } ) stage("end") { println "end" } {code} we are getting the following display in BlueOcean: !blueocean.png! But in the parallel step, only the third branch has a *stage* defined, and therefore only this one is expected to be displayed. Unfortunately all the branches are displayed even if not containing any stage. Additionally, the name displayed for the third branch is the *branch name* instead of the *stage name* as one would have thought. On the other hand, in the Pipeline view it is displayed as expected: !stages.png! Use case: technical steps which need to run in parallel to maintain shared resources, advance timeout monitoring, etc ... doesn't have to pollute the Blue Ocean view. May be possible to add an boolean option to the parallel step not to use branch name as default display name in Blue Ocean ? |
Description |
Original:
With the following pipeline: {code:java} stage("begin") { println "begin" } parallel ( "no_stage": { println "no stage" }, "": { println "no name" }, "with_stage": { stage("my_stage") { println "named stage" } } ) stage("end") { println "end" } {code} we are getting the following display in BlueOcean: !blueocean.png! But in the parallel step, only the third branch has a *stage* defined, and therefore only this one is expected to be displayed. Unfortunately all the branches are displayed even if not containing any stage. Additionally, the name displayed for the third branch is the *branch name* instead of the *stage name* as one would have thought. On the other hand, in the Pipeline view it is displayed as expected: !stages.png! Use case: technical steps which need to run in parallel to maintain shared resources, advance timeout monitoring, etc ... doesn't have to pollute the Blue Ocean view. May be possible to add an boolean option to the parallel step not to use branch name as default display name in Blue Ocean ? |
New:
With the following pipeline: {code:java} stage("begin") { println "begin" } parallel ( "no_stage": { println "no stage" }, "": { println "no name" }, "with_stage": { stage("my_stage") { println "named stage" } } ) stage("end") { println "end" } {code} we are getting the following display in BlueOcean: !blueocean.png! But in the parallel step, only the third branch has a *stage* defined, and therefore only this one is expected to be displayed. Unfortunately all the branches are displayed even if not containing any stage. Additionally, the name displayed for the third branch is the *branch name* instead of the *stage name* as one would have thought. On the other hand, in the Pipeline view it is displayed as expected: !stages.png! Use case: technical steps which need to run in parallel to maintain shared resources, advance timeout monitoring, etc ... doesn't have to pollute the Blue Ocean view. May be possible to add a boolean option to the parallel step not to use branch name as default display name in Blue Ocean ? |
Description |
Original:
With the following pipeline: {code:java} stage("begin") { println "begin" } parallel ( "no_stage": { println "no stage" }, "": { println "no name" }, "with_stage": { stage("my_stage") { println "named stage" } } ) stage("end") { println "end" } {code} we are getting the following display in BlueOcean: !blueocean.png! But in the parallel step, only the third branch has a *stage* defined, and therefore only this one is expected to be displayed. Unfortunately all the branches are displayed even if not containing any stage. Additionally, the name displayed for the third branch is the *branch name* instead of the *stage name* as one would have thought. On the other hand, in the Pipeline view it is displayed as expected: !stages.png! Use case: technical steps which need to run in parallel to maintain shared resources, advance timeout monitoring, etc ... doesn't have to pollute the Blue Ocean view. May be possible to add a boolean option to the parallel step not to use branch name as default display name in Blue Ocean ? |
New:
With the following pipeline: {code:java} stage("begin") { println "begin" } parallel ( "no_stage": { println "no stage" }, "": { println "no name" }, "with_stage": { stage("my_stage") { println "named stage" } } ) stage("end") { println "end" } {code} we are getting the following display in BlueOcean: !blueocean.png! But in the parallel step, only the third branch has a *stage* defined, and therefore only this one is expected to be displayed. Unfortunately all the branches are displayed even if not containing any stage. Additionally, the name displayed for the third branch is the *branch name* instead of the *stage name* as one would have thought. On the other hand, in the Pipeline view it is displayed as expected: !stages.png! Use case: technical steps which need to run in parallel to maintain shared resources, advance timeout monitoring, etc ... doesn't have to pollute the Blue Ocean view. May be possible to add a boolean option to the parallel step not to use branch name as default display name in Blue Ocean, and eventually make branch with no stage invisible ? |
Epic Link | New: JENKINS-43953 [ 181485 ] |
Link |
New:
This issue is related to |
Attachment | New: image-2017-06-22-12-33-47-644.png [ 38583 ] |
Attachment | New: image-2017-06-22-12-47-13-324.png [ 38584 ] |
Attachment | New: image-2017-06-22-12-53-45-573.png [ 38585 ] |
Link |
New:
This issue is related to |