We are happy users of the azure-vm-agents-plugin,  unfortunatley we often see that request for agent comes in bursts and that puts stress on the IOPS limmits on our jenkins master.  We are bootstrapping data from our master to the newley provisioned slaves and the more slaves that are provisioned at a time the slower the provisioning.  therefore it would be nice to have a limit of concurrent provisioning slaves.

          [JENKINS-56972] limit number of concurrent provissioning vm's

          Jonas Bovin added a comment -

          This feature might also help with an issue I have seen where the plugin requested 20 VM's and that was too many cores for our azure subscription and thus no VM's were provisioned - with this we would get as many as possible...

          Jonas Bovin added a comment - This feature might also help with an issue I have seen where the plugin requested 20 VM's and that was too many cores for our azure subscription and thus no VM's were provisioned - with this we would get as many as possible...

          Jie Shen added a comment -

          Make sense. I will check how to achieve this feature.

          Jie Shen added a comment - Make sense. I will check how to achieve this feature.

          Tim Jacomb added a comment -

          All issues have been transferred to GitHub.

          See https://github.com/jenkinsci/azure-vm-agents-plugin/issues

          Search the issue title to find it.

          (This is a bulk comment and can't link to the specific issue)

          Tim Jacomb added a comment - All issues have been transferred to GitHub. See https://github.com/jenkinsci/azure-vm-agents-plugin/issues Search the issue title to find it. (This is a bulk comment and can't link to the specific issue)

            jieshe Jie Shen
            lunarfs Frank Vissing
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: