You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional terminate conditions
This is very useful and works as accepted.
It should also be useful to add
Startup conditions
Time in the queue before to start a new instance: [ ] minutes.
(Meaning do not start a new vm if the time in queue is less then this time.)
Use case:
We use now a pool with 8 VM's starting from an image.
Because we completely delete the VM's from Azure if they get shut down, the startup of a VM takes about 5 to 10 minutes.
It often happens when a list of small builds (build time about 2/3 min) gets queued, extra Agents get fired up reacting to the queue, but by the time the extra Agents have started the queue already empty. (short build time against long start-up time.)
In our case setting this parameter to 10 minutes will solve this behavior.
The text was updated successfully, but these errors were encountered:
Startup parameter
We have now an option:
This is very useful and works as accepted.
It should also be useful to add
Time in the queue before to start a new instance: [ ] minutes.
(Meaning do not start a new vm if the time in queue is less then this time.)
Use case:
We use now a pool with 8 VM's starting from an image.
Because we completely delete the VM's from Azure if they get shut down, the startup of a VM takes about 5 to 10 minutes.
It often happens when a list of small builds (build time about 2/3 min) gets queued, extra Agents get fired up reacting to the queue, but by the time the extra Agents have started the queue already empty. (short build time against long start-up time.)
In our case setting this parameter to 10 minutes will solve this behavior.
The text was updated successfully, but these errors were encountered: