-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins ver. 2.32.2
Sometimes it can take a long time to spin up a VM. It would be nice if we could set a number-of-VMs threshold where retention time does not apply. For example, I could keep two of my "general" VMs running at all times so jobs start immediately under light load, and new VMs only start getting created under heavier load.
Looks like the logic is in main/java/com/microsoft/azure/AzureVMCloudRetensionStrategy.java ?
[JENKINS-41922] "Minimum instances" support
Assignee | Original: Claudiu Guiman [ clguiman ] | New: Azure DevOps [ azure_devops ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Component/s | New: _unsorted [ 19622 ] | |
Component/s | Original: azure-vm-agents-plugin [ 21950 ] |
A co-worker proposes an interesting similar-but-different proposal: minimum idle VM instances under load - i.e. if I set the value to 2, and i have jobs running on 2 of a given VM type, then 2 more get started up to pre-fulfil the requirements of subsequent job submissions whilst the first 2 are still in use.