-
Bug
-
Resolution: Unresolved
-
Major
-
None
If Jenkins is quieting down and there are builds in the queue, nodes are still provisioned from any clouds.
Ideally, Jenkins would not provision new slaves when it is supposed to be quieting down.
- is related to
-
JENKINS-27565 Nodes can be removed as idle before the assigned tasks have started
-
- Closed
-
- links to
[JENKINS-20967] Cloud provisioning called when Jenkins is quieting Down
Assignee | New: Stephen Connolly [ stephenconnolly ] |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 152778 ] | New: JNJira + In-Review [ 178327 ] |
It seems that the root cause is that each label's LoadStatistics are still reporting queue lengths over zero.
So a simple fix would just have hudson.slaves.NodeProvisioner#update not provision if Jenkins.isQuietingDown().