Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39847

Improved visualization for multiple "parallel"s within the same stage block

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • blueocean-plugin
    • None

      Improved visualization for multiple "parallel"s within the same stage block isn't planned at this time

      There is some debate on how this concept can be visualised in Blue Ocean. Much like nesting stages (see JENKINS-38442) this is difficult for us to visualize in a consistent way that meets user expectations.

      The current behaviour in Blue Ocean is to show all the parallels belonging to a stage under the same stage. However, this is currently not working due to a bug in pipeline - see JENKINS-39839.

      The following pipeline

      node {
        stage('S1') {  
          parallel 'S1.0': { sh('sleep 10') }
          
          parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') }
        }
          stage('S2') {  
          parallel 'S2.0': { sh('sleep 10') }
          
          parallel 'S2.1': { sh('sleep 10') }
        }
      }
      

      Is represented as this:

      • S1.0 is not displayed
      • S2.0 and S2.1 should be under stage 2
      • S2.0 and S2.1 are not marked as finished

      Additional note:
      Made with Pipeline plugin patched with https://github.com/jenkinsci/blueocean-plugin/pull/605

          [JENKINS-39847] Improved visualization for multiple "parallel"s within the same stage block

          before you ask why we should support single // — this is because the content of // might be autogenerated (by code or anything else)

          Julien Pivotto added a comment - before you ask why we should support single // — this is because the content of // might be autogenerated (by code or anything else)

          Vivek Pandey added a comment -

          roidelapluie blueocean uses workflow-api to build DAG that serves visualization. In this case, one of the event is not fired during parsing and that breaks things up. I have a ticket opened https://issues.jenkins-ci.org/browse/JENKINS-39839, have added comment and referenced your test case. Once its fixed its expected to work fine.

          Vivek Pandey added a comment - roidelapluie blueocean uses workflow-api to build DAG that serves visualization. In this case, one of the event is not fired during parsing and that breaks things up. I have a ticket opened https://issues.jenkins-ci.org/browse/JENKINS-39839 , have added comment and referenced your test case. Once its fixed its expected to work fine.

          Thanks

          Julien Pivotto added a comment - Thanks

          Michael Neale added a comment -

          Great - not sure how this would visually look, as it is all grouped in one stage column.

          THis means that even when all steps show up, it won't be helpful. So while that fix may help, the recommendation is to only have 1 parallel per stage.

          Michael Neale added a comment - Great - not sure how this would visually look, as it is all grouped in one stage column. THis means that even when all steps show up, it won't be helpful. So while that fix may help, the recommendation is to only have 1 parallel per stage.

            Unassigned Unassigned
            roidelapluie Julien Pivotto
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: