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

Nested parallels blocks break rendering

    XMLWordPrintable

    Details

    • Epic Link:
    • Similar Issues:

      Description

      Using the following pipeline definition, there is no stage rendering in BO. Only logs.

      stage('Start') {
       node {
          echo "Start"
       }
      }
      
      stage('Middle'){
          parallel(step1: {
              node {
                  echo "step 1"
              }
          }, step2: {
              node {
                  echo "step 2 start"
                  parallel (
                      phase1: { echo "Phase 1" },
                      phase2: { echo "Phase 2" }
                  )
                  echo "step 2 end"
              }
      
          })
      }
      
      stage('End') {
       node {
          echo "End"
       }
      }
      

        Attachments

          Activity

          Hide
          michaelneale Michael Neale added a comment -

          Vivek Pandey James Dumay my understanding is that this should show up flattened in some fashion. I am not sure if it is API or visualisation but I thought could at least look if the data is right to start with at some point.

          Show
          michaelneale Michael Neale added a comment - Vivek Pandey James Dumay my understanding is that this should show up flattened in some fashion. I am not sure if it is API or visualisation but I thought could at least look if the data is right to start with at some point.
          Hide
          vivek Vivek Pandey added a comment -

          Right, nested parallel branches are supposed to look flattened, thats what DAG is returned by nodes API. That part looks fine. Tried on latest master, stages/parallels appear fine in karaoke(as build progresses). Probably whats reported is probably fixed in https://issues.jenkins-ci.org/browse/JENKINS-39229.

          Vincent Latombe As mentioned above, I suspect you are not seeing node graph only in initial run, on page refresh or if you clikc on previous run, you should see the node graph as below.

          Show
          vivek Vivek Pandey added a comment - Right, nested parallel branches are supposed to look flattened, thats what DAG is returned by nodes API. That part looks fine. Tried on latest master, stages/parallels appear fine in karaoke(as build progresses). Probably whats reported is probably fixed in https://issues.jenkins-ci.org/browse/JENKINS-39229 . Vincent Latombe As mentioned above, I suspect you are not seeing node graph only in initial run, on page refresh or if you clikc on previous run, you should see the node graph as below.
          Hide
          vlatombe Vincent Latombe added a comment -

          Using b12, I don't see the stages even after a page refresh on a completed build.

          Show
          vlatombe Vincent Latombe added a comment - Using b12, I don't see the stages even after a page refresh on a completed build.
          Hide
          vivek Vivek Pandey added a comment -

          Vincent Latombe Perhaps there is bug in b12 thats preventing from rendering nested branches. I can confirm its fixed on master. We are going to have a release (b13) early next week that should fix this issue. I am closing this issue for now. Feel free to open it if you still face this issue after b13 release next week.

          Show
          vivek Vivek Pandey added a comment - Vincent Latombe Perhaps there is bug in b12 thats preventing from rendering nested branches. I can confirm its fixed on master. We are going to have a release (b13) early next week that should fix this issue. I am closing this issue for now. Feel free to open it if you still face this issue after b13 release next week.

            People

            • Assignee:
              vivek Vivek Pandey
              Reporter:
              vlatombe Vincent Latombe
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: