|
So the only way to do it is outside the core - either by plugin (I'm not sure if the necessary hooks are available) or remote API (but I couldn't find any method to query the current queue length)? Cheers, Krystian, We're working at supplementing the new REST endpoints for 2.3.1. I'll see if the queues information can be made available through the REST API. As far as plugin points goes, there is a CustomPreBuildQueuedAction (see http://confluence.atlassian.com/display/BAMBOO/Pre+Build+Queued+Action Cheers, Mark C Oh! That's a great news. Thanks for info! I'll look into it then. Cheers, |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Hi guys,
After using EC2 internally here at Atlassian, what we have found was that to be able to scale up and down of agents purely based on load may be a little cost ineffective and a little too un-predictable.
What we have found that worked better for us was a schedule/time based scaling up and down. We have implemented this in
BAM-4326.Cheers,
Edwin