Details
-
Improvement
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
Jenkins 3.73.2, Blue Ocean Plugin 1.3.1, Pipeline 2.5
Description
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.
Attachments
Issue Links
- is duplicated by
-
JENKINS-44820 Parallel branches with no stage should not be displayed in Blue Ocean
-
- Resolved
-
- links to
- mentioned in
-
Page Loading...
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | Bildschirmfoto 2017-11-02 um 22.03.54.png [ 40207 ] |
Attachment | Senario1.png [ 40208 ] |
Attachment | Bildschirmfoto 2017-11-02 um 22.03.54.png [ 40207 ] |
Attachment | Senario1.png [ 40208 ] |
Attachment | ex1.png [ 40209 ] |
Description | 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 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 | ex2.png [ 40210 ] |
Attachment | ex3.png [ 40211 ] |
Attachment | ex4.png [ 40212 ] |
Environment | Jenkins 3.73.2, Blue Ocean Plugin 1.3.1 | Jenkins 3.73.2, Blue Ocean Plugin 1.3.1, |
Description |
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.. |
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. |
Environment | Jenkins 3.73.2, Blue Ocean Plugin 1.3.1, | Jenkins 3.73.2, Blue Ocean Plugin 1.3.1, Pipeline 2.5 |
Remote Link | This issue links to "Page (Jenkins Wiki)" [ 18146 ] |
Remote Link | This issue links to "Rationalising Parallel (Web Link)" [ 18148 ] |
Description |
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. |
*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. See [Rationalising Parallel|https://wiki.jenkins.io/display/JENKINS/Rationalising+parallel]. *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. |
Epic Link | JENKINS-43952 [ 181484 ] |
Link |
This issue is duplicated by |
Summary | Ocean View shouldn't visualize the parallel keyword of a scripted pipeline directly | Blue Ocean shouldn't visualize the parallel keyword of a scripted pipeline directly |
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.