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

Stage graph unsuitable for large and/or complex pipelines

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.40
      Blue Ocean 1.0.0-b17
    • Similar Issues:

      Description

      Improvement on roadmap

      This improvement is on the Blue Ocean project roadmap. Check the roadmap page for updates.

      The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

      Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would greatly exacerbate the problem.

      Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

      I envision two possible solutions:

      1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
      2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

      Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.

        Attachments

          Issue Links

            Activity

            ileitch Ian Leitch created issue -
            jamesdumay James Dumay made changes -
            Field Original Value New Value
            Sprint post-release [ 181 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Epic Link JENKINS-35755 [ 171716 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            jamesdumay James Dumay made changes -
            Attachment matrix-test-parallel.jpg [ 35767 ]
            jamesdumay James Dumay made changes -
            Sprint post-release [ 181 ] release candidate [ 171 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Link This issue blocks JENKINS-39770 [ JENKINS-39770 ]
            jamesdumay James Dumay made changes -
            Sprint up next [ 171 ] 1.1 [ 251 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Assignee Brody Maclean [ brody ]
            michaelneale Michael Neale made changes -
            Link This issue relates to JENKINS-38442 [ JENKINS-38442 ]
            jamesdumay James Dumay made changes -
            Sprint 1.1 [ 251 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-43247 [ JENKINS-43247 ]
            scgruber Sam Gruber made changes -
            Attachment too-much-pipeline.png [ 36852 ]
            jamesdumay James Dumay made changes -
            Summary Stage graph unsuitable for large, complex pipelines Stage graph unsuitable for large and/or complex pipelines
            jamesdumay James Dumay made changes -
            Epic Link JENKINS-35755 [ 171716 ] JENKINS-43953 [ 181485 ]
            jamesdumay James Dumay made changes -
            Description The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            {panel:title=Improvement on Roadmap|titleBGColor=lightgreen}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates, including the ETA.
            {panel}

            The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            jamesdumay James Dumay made changes -
            Description {panel:title=Improvement on Roadmap|titleBGColor=lightgreen}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates, including the ETA.
            {panel}

            The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            {panel:title=Improvement on Roadmap|titleBGColor=#3878de}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates, including the ETA.
            {panel}

            The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            jamesdumay James Dumay made changes -
            Description {panel:title=Improvement on Roadmap|titleBGColor=#3878de}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates, including the ETA.
            {panel}

            The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            {panel:title=Improvement on Roadmap|titleBGColor=#3878de|titleColor=white}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates, including the ETA.
            {panel}

            The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            jamesdumay James Dumay made changes -
            Description {panel:title=Improvement on Roadmap|titleBGColor=#3878de|titleColor=white}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates, including the ETA.
            {panel}

            The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            {panel:title=Improvement on Roadmap|titleBGColor=#3878de|titleColor=white}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates.
            {panel}

            The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            jamesdumay James Dumay made changes -
            Description {panel:title=Improvement on Roadmap|titleBGColor=#3878de|titleColor=white}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates.
            {panel}

            The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            {panel:title=Improvement on roadmap|titleBGColor=#3878de|titleColor=white}
            This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates.
            {panel}

            The Blue Ocean stage graph is great for small, simple pipelines however it breaks down with many parallel builds. See attached screenshot for an example.

            Because 'stage' can no longer be nested within 'parallel', all of our steps must belong under a single 'Test' stage. We have 19 parallel jobs, which is not an uncommon number for iOS/Android development where many combinations of app, device and OS version need to be tested. We'd actually like to split some of the jobs into smaller chunks to take advantage of idle build agents, but this would *greatly* exacerbate the problem.

            Grouping jobs under multiple stages would improve the UI experience, but also drastically increase the runtime of our integration runs as stages are executed serially.

            I envision two possible solutions:

            1. Stages have a 'parallel' option that allows them to run at the same time as other parallel stages.
            2. A step is introduced that is used purely as an annotation for the purposes of rendering a more appropriate graph. Ideally the step would be deeply nestable allowing for complex graph hierarchies.

            Thanks for all the hard work on Blue Ocean, it's really shaping up nicely and I eagerly await each new release.
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-46244 [ JENKINS-46244 ]
            jamesdumay James Dumay made changes -
            Assignee Brody Maclean [ brody ]
            benlangfeld Ben Langfeld made changes -
            Assignee Ben Langfeld [ benlangfeld ]
            benlangfeld Ben Langfeld made changes -
            Link This issue depends on JENKINS-47683 [ JENKINS-47683 ]
            michaelneale Michael Neale made changes -
            Remote Link This issue links to "Page (Jenkins Wiki)" [ 18103 ]
            michaelneale Michael Neale made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            michaelneale Michael Neale made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            michaelneale Michael Neale made changes -
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Resolved [ 5 ]
            jamesdumay James Dumay made changes -
            Remote Link This issue links to "CloudBees Internal UX-624 (Web Link)" [ 18192 ]

              People

              Assignee:
              benlangfeld Ben Langfeld
              Reporter:
              ileitch Ian Leitch
              Votes:
              19 Vote for this issue
              Watchers:
              36 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: