-
Improvement
-
Resolution: Unresolved
-
Minor
Problem
The current Pipeline duration time includes pause time spent in "input" steps. I think it would be good to have a separation of build time from time spent waiting for inputs eg. 10m (Paused for 1h) or perhaps if more compact form was required, something like "10m 5s (+1h 2m 3s)".
For clarification, I'm referring to the time quoted by the "Activity" tab "Duration" column, and the value next to the clock symbol in the pipeline run details page.
Requirements
We should be able to determine the time taken:
- In the queue
- pausing for input
- running
- total duration, for the pipeline to run in real time including time spent in queue, paused and running.
[JENKINS-45022] Pipeline duration should not include the time it was paused for input or waiting on resources
Summary | Original: Split Pipeline Step Time from Pause Time | New: Pipeline duration should not include the time it was paused for input or waiting on queued |
Summary | Original: Pipeline duration should not include the time it was paused for input or waiting on queued | New: Pipeline duration should not include the time it was paused for input or waiting on resources |
Description |
Original:
The current Pipeline duration time includes pause time spent in "input" steps. I think it would be good to have a separation of build time from time spent waiting for inputs eg. 10m (Paused for 1h) or perhaps if more compact form was required, something like "10m 5s (+1h 2m 3s)". For clarification, I'm referring to the time quoted by the "Activity" tab "Duration" column, and the value next to the clock symbol in the pipeline run details page. |
New:
*Problem* The current Pipeline duration time includes pause time spent in "input" steps. I think it would be good to have a separation of build time from time spent waiting for inputs eg. 10m (Paused for 1h) or perhaps if more compact form was required, something like "10m 5s (+1h 2m 3s)". For clarification, I'm referring to the time quoted by the "Activity" tab "Duration" column, and the value next to the clock symbol in the pipeline run details page. *Requirements* We should be able to determine the time taken: * In the queue * pausing for input * running * total duration, for the pipeline to run in real time including time spent in queue, paused and running. |
Epic Link | New: JENKINS-45048 [ 183138 ] |
inkychris I 100% agree. We are working towards this now by ensuring Pipeline steps can expose their statuses more consistently. When we have this it will be possible to extract this information.