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

More consistent use of PauseAction

    Details

    • Similar Issues:

      Description

      Currently PauseAction is added only by InputStep. But it makes sense to add also for SleepStep (JENKINS-26120) and WaitForConditionStep (JENKINS-25570), as well as for the proposed wait step (JENKINS-27127). This would allow visualizations to give a better picture of which flow builds and branches were active at a given time, compute running time more accurately, etc.

        Attachments

          Issue Links

            Activity

            Hide
            svanoort Sam Van Oort added a comment -

            +1 for tracking these with a common base. If we go this course, could we move the PauseAction should probably be moved to workflow-api actions, to avoid potential dependency issues and make it easier to consume?

            Show
            svanoort Sam Van Oort added a comment - +1 for tracking these with a common base. If we go this course, could we move the PauseAction should probably be moved to workflow-api actions, to avoid potential dependency issues and make it easier to consume?
            Hide
            jglick Jesse Glick added a comment -

            Uh, yes, it should have been in workflow-api to begin with.

            Show
            jglick Jesse Glick added a comment - Uh, yes, it should have been in workflow-api to begin with.

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                jglick Jesse Glick
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: