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

Visualizing (list of sequential steps) as groups, as part of one stage

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The pipeline view of Blue Ocean makes a great deal in listing a block of parallel steps by just displaying different boxes under each other. This seems to work only for parallel steps defined in one stage. If I add different build steps to a stage, operated sequentielly, the visualizing only displys one box for the entire stage. It would be helpful to express a group of steps, as part of the stage, processed sequentially, but shown as dedicated boxed (one group of steps in one box, the stage comprises a set of sequential groups of sequential steps).

        Attachments

          Issue Links

            Activity

            Hide
            jamesdumay James Dumay added a comment - - edited

            Michael Hüttermann I think this is related to JENKINS-38442 but could you please provide an example Jenkinsfile pipeline script and screenshot of how it is currently rendered to help clarify your request?

            Show
            jamesdumay James Dumay added a comment - - edited Michael Hüttermann I think this is related to JENKINS-38442 but could you please provide an example Jenkinsfile pipeline script and screenshot of how it is currently rendered to help clarify your request?
            Hide
            michaelhuettermann Michael Hüttermann added a comment -

            Here a concrete example. The following snippet defines four tasks which are processed in parallel. In Blue Ocean pipeline view, this is wonderfully displayed as four boxes one after the other, see screenshot.

             
               stage 'Check preconditions'
               parallel "Sanity check 1": {
                    echo "1"
                }, "Sanity check 2": {
                    echo "2i"
                }, "Sanity check 3": {
                    echo "3"
                }, "Sanity check 4": {
                    echo "4"
                }
            

            The idea now is to define the four example steps as a sequence of steps which have to be processed sequentially and still displayed as four paths as part of the stage (similar to the four parallel paths displayed now when run in parallel).

            The current solution does not allow that. If I now define sequential steps as part of a stage, the single steps are displayed in the lower part of pipeline view, but the upper part of the pipeline view just shows one graphical control i.e. the stage (which sums up all steps). This is fine, but not as powerful as the requested functionality.

            With other words, such a notation is requested:

             
               stage 'Check preconditions'
               sequential "Sanity check 1": {
                    echo "1"
                }, "Sanity check 2": {
                    echo "2"
                }, "Sanity check 3": {
                    echo "3"
                }, "Sanity check 4": {
                    echo "4"
                }
            

            This would lead to a very similar graphical presentation as the parallel processing, see attachment, but the difference is, that the four parts are run sequentially, not in parallel. It seems to be an implementation detail whether a key word sequential is used or something like group. Looks like JENKINS-38442 offers a generic approach to much more functionality than what is requested here.

            Show
            michaelhuettermann Michael Hüttermann added a comment - Here a concrete example. The following snippet defines four tasks which are processed in parallel. In Blue Ocean pipeline view, this is wonderfully displayed as four boxes one after the other, see screenshot. stage 'Check preconditions' parallel "Sanity check 1": { echo "1" }, "Sanity check 2": { echo "2i" }, "Sanity check 3": { echo "3" }, "Sanity check 4": { echo "4" } The idea now is to define the four example steps as a sequence of steps which have to be processed sequentially and still displayed as four paths as part of the stage (similar to the four parallel paths displayed now when run in parallel). The current solution does not allow that. If I now define sequential steps as part of a stage, the single steps are displayed in the lower part of pipeline view, but the upper part of the pipeline view just shows one graphical control i.e. the stage (which sums up all steps). This is fine, but not as powerful as the requested functionality. With other words, such a notation is requested: stage 'Check preconditions' sequential "Sanity check 1": { echo "1" }, "Sanity check 2": { echo "2" }, "Sanity check 3": { echo "3" }, "Sanity check 4": { echo "4" } This would lead to a very similar graphical presentation as the parallel processing, see attachment, but the difference is, that the four parts are run sequentially, not in parallel. It seems to be an implementation detail whether a key word sequential is used or something like group . Looks like JENKINS-38442 offers a generic approach to much more functionality than what is requested here.
            Hide
            jamesdumay James Dumay added a comment -

            Right that makes sense to me. Thanks for reporting this!

            Show
            jamesdumay James Dumay added a comment - Right that makes sense to me. Thanks for reporting this!
            Hide
            jamesdumay James Dumay added a comment -

            On further inspection this seems like a use case that could be covered by nested stages. Closing this ticket as a duplicate of JENKINS-38442 but we will review these and other linked tickets when cooking up a solution.

            Show
            jamesdumay James Dumay added a comment - On further inspection this seems like a use case that could be covered by nested stages. Closing this ticket as a duplicate of JENKINS-38442 but we will review these and other linked tickets when cooking up a solution.

              People

              • Assignee:
                Unassigned
                Reporter:
                michaelhuettermann Michael Hüttermann
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: