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

Allow sequential stages inside parallel in Scripted syntax

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Similar to JENKINS-46809, I would like the Blue Ocean GUI to properly visualize multiple stages in sequence that are all parallel of each other. Below is an example image of what this looks like using declarative syntax (working):

       

      Here is the declarative example code I wrote to generate the example image:

      pipeline {
        agent { label 'master' }
        stages {
          stage('Build and Test') {
            parallel {
              stage("Build and Test Linux") {
                stages {
                  stage("Build (Linux)") {
                    agent any
                    steps {
                      echo "Inside for loop 1"
                    }
                  }
                  stage("Test (Linux)") {
                    agent any
                    steps {
                      echo "Inside for loop 2"
                    }
                  }
                }
              }
              stage("Build and Test Windows") {
                stages {
                  stage("Build (Windows)") {
                    agent any
                    steps {
                      echo "Inside for loop 3"
                    }
                  }
                  stage("Test (Windows)") {
                    agent any
                    steps {
                      echo "Inside for loop 4"
                    }
                  }
                }
              }
            }
          }
        }
      }

       

      Here is example scripted Jenkins code that I would like to use. Linux and windows build/test flows happen in parallel. Inside each flow in a "build" stage and then a "test" stage. The Windows sequential build/test flow should be displayed in parallel with the Linux build/test flow, but right now the separate Build/Test sequential stages are combined into one circle/stage when using the scripted syntax.

       

      pipeline {
        agent any
        stages {
          stage("Build and Test") {
            steps {
              script {
                parallel linux: {
                  node("linux_build") {
                    echo "Inside for loop 1"
                  }
                  node("linux_test") {
                    echo "Inside for loop 2"
                  }
                },
                windows: {
                  node("windows_build") {
                    echo "Inside for loop 3"
                  }
                  node("windows_test") {
                    echo "Inside for loop 4"
                  }
                }
              }
            }
          }
        }
      }
      

       

      This is what the scripted example code currently generates:

       

        Attachments

          Issue Links

            Activity

            Hide
            jglick Jesse Glick added a comment -

            I do not know how Blue Ocean works in any detail. My comment was very much about the terminology. None of the examples given so far in this issue are using actual Scripted syntax—they all start with pipeline, which is Declarative syntax, and so all bets are off.

            At any rate, the closest Scripted analogue I can come up with for the original Declarative script would be

            parallel 'Build and Test Linux': {
                stage("Build (Linux)") {
                    echo "Inside for loop 1"
                }
                stage("Test (Linux)") {
                    echo "Inside for loop 2"
                }
            }, 'Build and Test Windows': {
                stage("Build (Windows)") {
                    echo "Inside for loop 3"
                }
                stage("Test (Windows)") {
                    echo "Inside for loop 4"
                }
            }
            

            which indeed also fails to display the stages—only the branches are shown. (Similarly when the whole script is enclosed in stage('Build and Test') {…}.)So I would consider that a bug in Blue Ocean: it should display a Pipeline build with a structure that its visualization layer supports, regardless of the syntax used to run that build. Perhaps there is some workaround that a B.O. developer could explain.

            Show
            jglick Jesse Glick added a comment - I do not know how Blue Ocean works in any detail. My comment was very much about the terminology. None of the examples given so far in this issue are using actual Scripted syntax—they all start with pipeline , which is Declarative syntax, and so all bets are off. At any rate, the closest Scripted analogue I can come up with for the original Declarative script would be parallel 'Build and Test Linux' : { stage( "Build (Linux)" ) { echo "Inside for loop 1" } stage( "Test (Linux)" ) { echo "Inside for loop 2" } }, 'Build and Test Windows' : { stage( "Build (Windows)" ) { echo "Inside for loop 3" } stage( "Test (Windows)" ) { echo "Inside for loop 4" } } which indeed also fails to display the stages—only the branches are shown. (Similarly when the whole script is enclosed in stage('Build and Test') {… }.)So I would consider that a bug in Blue Ocean: it should display a Pipeline build with a structure that its visualization layer supports, regardless of the syntax used to run that build. Perhaps there is some workaround that a B.O. developer could explain.
            Hide
            peacemoon An Tran added a comment -

            Jesse Glick From what I see in last comment int this ticket here https://issues.jenkins-ci.org/browse/JENKINS-53048?focusedCommentId=351304&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-351304 , Adam Carroll really wants to have an improvement instead of a bug report because the UI really on supports only declarative syntax of parallel command. If there is a bug, I would open a new one and keep this as improvement.

            Show
            peacemoon An Tran added a comment - Jesse Glick From what I see in last comment int this ticket here https://issues.jenkins-ci.org/browse/JENKINS-53048?focusedCommentId=351304&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-351304  , Adam Carroll really wants to have an improvement instead of a bug report because the UI really on supports only declarative syntax of parallel command. If there is a bug, I would open a new one and keep this as improvement.
            Hide
            jglick Jesse Glick added a comment -

            Contra Olivier Lamy’s comment there I consider this a bug. Blue Ocean should pay attention to the build metadata as provided by official Pipeline APIs and may not make assumptions about the mechanism used to run a build, except insofar as that is intrinsically required for a certain feature. (For example, a stage restart button should only appear next to a Declarative stage, because the feature of restarting a stage is tied to Declarative semantics.)

            Regardless of how the issue is classified, the question of whether it will be fixed or not depends entirely on the development team’s time and priorities.

            Show
            jglick Jesse Glick added a comment - Contra Olivier Lamy ’s comment there I consider this a bug. Blue Ocean should pay attention to the build metadata as provided by official Pipeline APIs and may not make assumptions about the mechanism used to run a build, except insofar as that is intrinsically required for a certain feature. (For example, a stage restart button should only appear next to a Declarative stage, because the feature of restarting a stage is tied to Declarative semantics.) Regardless of how the issue is classified, the question of whether it will be fixed or not depends entirely on the development team’s time and priorities.
            Hide
            peacemoon An Tran added a comment -
            Show
            peacemoon An Tran added a comment - I found some tickets that maybe related: https://issues.jenkins-ci.org/browse/JENKINS-53751 https://issues.jenkins-ci.org/browse/JENKINS-53162  
            Hide
            acarr468 Adam Carroll added a comment -

            Thanks Jesse Glick and An Tran for digging into this more! I personally am not concerned whether or not this is a bug or improvement, as long as it is fixed . It does sound a lot like a bug to me, but I do understand the argument for it being an improvement. Whatever the best path to resolution is will be fine with me.

            Based on the tickets An Tran linked above, it looks like others desire this functionality as well.

            Show
            acarr468 Adam Carroll added a comment - Thanks Jesse Glick and An Tran for digging into this more! I personally am not concerned whether or not this is a bug or improvement, as long as it is fixed . It does sound a lot like a bug to me, but I do understand the argument for it being an improvement. Whatever the best path to resolution is will be fine with me. Based on the tickets An Tran linked above, it looks like others desire this functionality as well.

              People

              • Assignee:
                Unassigned
                Reporter:
                acarr468 Adam Carroll
              • Votes:
                9 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated: