-
Improvement
-
Resolution: Unresolved
-
Major
-
Jenkins 3.73.2, Blue Ocean Plugin 1.3.1, Pipeline 2.5
Problem
Sophisticated users of Pipeline want a more usable way to visualize and interact with their Pipelines. Blue Ocean cannot visualise pipelines in a meaningful way to users where there are a large number of stages or parallels.
Goals
- Reduce unnecessarily visualised parallel branches by reserving parallel syntaxes for visualisation and non-visualisation purposes.
- Increase developer satisfaction by making the rules of Pipeline visualisation more consistent and the visualisation usable at any scale.
Original Request
I believe the Pipeline keyword parallel should not be rendered by Ocean View directly respectively in it's on right , but only with transitive dependent Stages. Exception is when there is no stage enclosed by the parallel keyword. Background: since parallel can be used with enclosed stages and not only for the parallel execution of steps, the keyword has moved from being a mere implementation tool to a conceptional one for modeling workflows, this needs to be reflected in the visualization. In the following comments there are some examples, which try to proove the point respectively my expectations.
I am aware that there maybe nesting limitations, respectively how deeply the parallel keyword resp. stages are nested. Here i pratical tread-offs should be made.
- is duplicated by
-
JENKINS-44820 Parallel branches with no stage should not be displayed in Blue Ocean
-
- Resolved
-
- links to
- mentioned in
-
Page Failed to load
[JENKINS-47799] Blue Ocean shouldn't visualize the parallel keyword of a scripted pipeline directly
Attachment | New: Bildschirmfoto 2017-11-02 um 22.03.54.png [ 40207 ] |
Attachment | New: Senario1.png [ 40208 ] |
Attachment | Original: Bildschirmfoto 2017-11-02 um 22.03.54.png [ 40207 ] |
Attachment | Original: Senario1.png [ 40208 ] |
Attachment | New: ex1.png [ 40209 ] |
Description | Original: I believe the Pipeline keyword parallel should not be rendered by Ocean View directly respectively in it's on right , but only with transitive dependent Stages. Exception is when there is no stage enclosed by the parallel keyword. Background: since parallel can be used with enclosed stages and not only for the parallel execution of steps, the keyword has moved from being a mere implementation tool to a conceptional one for modeling workflows, this needs to be reflected in the visualization. In the following comments there are some examples, which try to proove the point respectively my expectations. |
New:
I believe the Pipeline keyword parallel should not be rendered by Ocean View directly respectively in it's on right , but only with transitive dependent Stages. Exception is when there is no stage enclosed by the parallel keyword. Background: since parallel can be used with enclosed stages and not only for the parallel execution of steps, the keyword has moved from being a mere implementation tool to a conceptional one for modeling workflows, this needs to be reflected in the visualization. In the following comments there are some examples, which try to proove the point respectively my expectations. I am aware that there maybe nesting limitations, respectively how deeply the parallel keyword resp. stages are nested. Here i can except consistent limitations.. |
Attachment | New: ex2.png [ 40210 ] |
Example:
Blue Ocean show's see attachment ex1.png
I would be ok with only Stage B, but since not stage word is enclosed ok.