We are having a specific requirement:
We have created default image first, cloned its capabilities and added custom capability to run selenium tests.
But it came into observation that when there are more jobs that require the selenium capability, a new instance of the Selenium image is being started and the job is running on that instance.
This is creating problems as most of the selenium stages take unto 40 mins to complete and the smaller jobs (< 5 mins and most take 15 secs) which are intended to run on the normal image are being queued.
Is there any way I can set the maximum number of instances of a particular image that can be running at any time?
Yeah but that just stops the smaller jobs from running on the Selenium image. But what if 3-4 selenium required jobs are in the queue but I do not want to fire new selenium instances instead they should just remain in queue till the selenium instance is free. Is there a way to do this?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs