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

Handle skipped stages and parallels in the Pipeline Graph

    Details

    • Sprint:
      Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4
    • Similar Issues:

      Description

      Ready for release

      This improvement is completed and scheduled for release in 1.2. Check the roadmap page for updates.

      Context
      The Pipeline team have added the ability to "skip" stages in the Pipeline (JENKINS-37781).

      Scope

      • Skipped stages are shown as not built
      • Declarative Pipeline will not provide flow nodes for skipped parallels so we can always assume that there won't be any skipped parallels.
      • If the first stage is skipped then the pipeline should start from a "Start" node.
      • If the last stage is skipped then the pipeline should end with a "End" node.
      • Ensure that the editors start/end nodes match the style in this mockup

      Mockup

        Attachments

          Issue Links

            Activity

            Hide
            comscience15 Nat Sr added a comment -

            James Dumay Josh McDonald Hi guys, I wonder instead of adding "when{....}" to determine whether the stage will be skipped or not, can we have user input feature to ask if they want to skip the stage or not. Do we have this feature too?

            Show
            comscience15 Nat Sr added a comment - James Dumay Josh McDonald Hi guys, I wonder instead of adding "when{....}" to determine whether the stage will be skipped or not, can we have user input feature to ask if they want to skip the stage or not. Do we have this feature too?
            Hide
            sophistifunk Josh McDonald added a comment -

            I imagine you'd achieve that easily enough with an input step to set a variable?

            Show
            sophistifunk Josh McDonald added a comment - I imagine you'd achieve that easily enough with an input step to set a variable?
            Hide
            michaelneale Michael Neale added a comment -

            Nat Sr not explicitly no - but like Josh says, could have an input step in an earlier stage that captures some environment variable that is then referred to in 'when'. A parametrised job could also provide the same variable I think. Can't put an input inside a 'when' (I think). 

            Show
            michaelneale Michael Neale added a comment - Nat Sr not explicitly no - but like Josh says, could have an input step in an earlier stage that captures some environment variable that is then referred to in 'when'. A parametrised job could also provide the same variable I think. Can't put an input inside a 'when' (I think). 
            Hide
            ruudp Ruud P added a comment -

            it is fixed with an update of jenkins, at this moment this works fine for me

            Show
            ruudp Ruud P added a comment - it is fixed with an update of jenkins, at this moment this works fine for me
            Hide
            comscience15 Nat Sr added a comment -

            Josh McDonald Michael Neale Thanks for your feedback. Yes, it is easy to set a variable. My thought is just about if there is a complicated case which is sometimes is outside the set up variable. So if we can get it with user input too, it would be great. 

            Show
            comscience15 Nat Sr added a comment - Josh McDonald Michael Neale Thanks for your feedback. Yes, it is easy to set a variable. My thought is just about if there is a complicated case which is sometimes is outside the set up variable. So if we can get it with user input too, it would be great. 

              People

              • Assignee:
                sophistifunk Josh McDonald
                Reporter:
                jamesdumay James Dumay
              • Votes:
                10 Vote for this issue
                Watchers:
                20 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: