-
Bug
-
Resolution: Unresolved
-
Minor
-
None
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.
- is blocking
-
JENKINS-27127 wait/notify steps
-
- Open
-
-
JENKINS-25570 Wait-for-condition step
-
- Resolved
-
-
JENKINS-26120 Safe sleep step
-
- Resolved
-
- links to
+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?