-
Bug
-
Resolution: Fixed
-
Minor
-
None
Pipeline jobs start executing almost immediately and then proceed to queue while waiting for a node to run the actual steps on.
The metrics plugin records and tracks the time queuing but does not associate this with the pipeline job itself because ExecutorStepExecution.PlaceholderTask does not implement Run
We need to resolve the Run and accumulate the additional queue time against the pipeline.
- is related to
-
JENKINS-42416 Metrics should include Pipeline "node()" sections.
- Closed
-
JENKINS-39180 Milestone option to coalesce queue items while awaiting executor
- Open
-
JENKINS-35630 Building on an executor for Pipeline job is incorrect
- Closed