[JIRA] (JENKINS-41922) "Minimum instances" support
Title: Message Title Azure DevOps resolved as Fixed Fixed in 0.4.8 (pool retention strategy). Jenkins / JENKINS-41922 "Minimum instances" support Change By: Azure DevOps Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41922) "Minimum instances" support
Title: Message Title Jo Shields commented on JENKINS-41922 Re: "Minimum instances" support 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41922) "Minimum instances" support
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-41922 "Minimum instances" support Issue Type: Improvement Assignee: Claudiu Guiman Components: azure-vm-agents-plugin Created: 2017/Feb/10 11:39 AM Environment: Jenkins ver. 2.32.2 Priority: Minor Reporter: Jo Shields 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 ? Add Comment
