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

Support visualization of downstream pipelines in Jenkins pipeline based views

      If I have a pipeline job (formerly workflow) Foo, that then triggers another pipeline job Bar, it does not get reflected in the delivery pipeline view. Job Bar is triggered as a build step in my job, for example:

      Job Foo:

      stage('Building') {
          println 'Triggering Bar'
          build 'Bar'
      }
      

      Job Bar:

      node('master') {
          stage('Child job stage') {
              println 'Doing stuff in child job'
          }
      }
      

      Only the Foo pipeline job and its steps are displayed in the delivery pipeline view:

      In this case, both Foo and Bar should have appeared as separate entities on the delivery pipeline view.

        1. teamcityView.png
          teamcityView.png
          24 kB
        2. pipeline view.png
          pipeline view.png
          12 kB
        3. mtldP.png
          mtldP.png
          6 kB

          [JENKINS-43679] Support visualization of downstream pipelines in Jenkins pipeline based views

          Martin created issue -
          Martin made changes -
          Description Original: If I have a pipeline job (formerly workflow) Foo, that then triggers another pipeline job Bar, it does not get reflected in the delivery pipeline view. Job bar is triggered as a build step in my job, for example:

          Job Foo:
          {code:java}
          stage('Building') {
              println 'Triggering Bar'
              build 'Bar'
          }
          {code}
          Job Bar:
          {code:java}
          node('master') {
              stage('Child job stage') {
                  println 'Doing stuff in child job'
              }
          }
          {code}
          Only the Foo pipeline job and its steps are displayed in the delivery pipeline view:

          !mtldP.png!

          In this case, both Foo and Bar should have appeared as separate entities on the delivery pipeline view.
          New: If I have a pipeline job (formerly workflow) Foo, that then triggers another pipeline job Bar, it does not get reflected in the delivery pipeline view. Job Bar is triggered as a build step in my job, for example:

          Job Foo:
          {code:java}
          stage('Building') {
              println 'Triggering Bar'
              build 'Bar'
          }
          {code}
          Job Bar:
          {code:java}
          node('master') {
              stage('Child job stage') {
                  println 'Doing stuff in child job'
              }
          }
          {code}
          Only the Foo pipeline job and its steps are displayed in the delivery pipeline view:

          !mtldP.png!

          In this case, both Foo and Bar should have appeared as separate entities on the delivery pipeline view.

          Tommy Tynjä added a comment -

          martinmine this is currently not within scope and I'm unsure if it should be. Do you have any suggestion for how that could be visualized?

          Tommy Tynjä added a comment - martinmine this is currently not within scope and I'm unsure if it should be. Do you have any suggestion for how that could be visualized?
          Tommy Tynjä made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Tommy Tynjä made changes -
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          Tommy Tynjä made changes -
          Assignee Original: Patrik Boström [ patbos ]
          Martin made changes -
          Attachment New: pipeline view.png [ 37410 ]

          Martin added a comment -

          tommysdk how is this outside the scope of the plugin? The summary on the wiki page says "Visualisation of Delivery/Build Pipelines, renders pipelines based on upstream/downstream jobs", I don't see why the case my jobs are pipelines makes them fall outside the scope of the plugin. 

          I would suggest to display the pipeline jobs the same way as downstream jobs are visualized. Based on the description on the wiki, I was expecting something more like this: 

          Martin added a comment - tommysdk  how is this outside the scope of the plugin? The summary on the wiki page says "Visualisation of Delivery/Build Pipelines, renders pipelines based on upstream/downstream jobs ", I don't see why the case my jobs are pipelines makes them fall outside the scope of the plugin.  I would suggest to display the pipeline jobs the same way as downstream jobs are visualized. Based on the description on the wiki, I was expecting something more like this: 

          Tommy Tynjä added a comment -

          martinmine Thanks for your thoughts on this. What I meant is that with the current solution, this is not a supported use case and therefore it does not show up as you expect in the pipeline view.

          Are your pipelines always short and only contain one or a few stages only? I think it could make a difference on how you would expect this to work depending on if you have short or long pipelines.

          Tommy Tynjä added a comment - martinmine Thanks for your thoughts on this. What I meant is that with the current solution, this is not a supported use case and therefore it does not show up as you expect in the pipeline view. Are your pipelines always short and only contain one or a few stages only? I think it could make a difference on how you would expect this to work depending on if you have short or long pipelines.

          Martin added a comment -

          tommysdk In that case if my current use-case is not supported, what is the actual use-case that the pipeline (workflow) job support that is currently covered by JENKINS-34040? The issue description says pipelines (note: plural), and the description for adding a new view for pipeline jobs says "Continuous Delivery pipelines, perfect for visualization on information radiators. Shows one or more delivery pipeline instances, based on traditional Jenkins jobs with upstream/downstream dependencies." which gives me the impression I can use this for displaying multiple pipelines together and their relationship. 

          How is the length of my pipeline relevant (Do you also mean pipeline jobs or the concept of pipelines which this plugin utilizes that is again different from pipeline jobs ? To answer your question, my current pipeline jobs contains just 3-4 stages. However, they are then distributed across multiple jobs as I'm doing multi-platform builds. 

          Martin added a comment - tommysdk In that case if my current use-case is not supported, what is the actual use-case that the pipeline (workflow) job support that is currently covered by JENKINS-34040 ? The issue description says pipelines (note: plural), and the description for adding a new view for pipeline jobs says "Continuous Delivery pipelines, perfect for visualization on information radiators. Shows one or more delivery pipeline instances , based on traditional Jenkins jobs with upstream/downstream dependencies." which gives me the impression I can use this for displaying multiple pipelines together and their relationship.  How is the length of my pipeline relevant (Do you also mean pipeline jobs or the concept of pipelines which this plugin utilizes that is again different from pipeline jobs ? To answer your question, my current pipeline jobs contains just 3-4 stages. However, they are then distributed across multiple jobs as I'm doing multi-platform builds. 

            Unassigned Unassigned
            martinmine Martin
            Votes:
            9 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: