Multiple Image Configuration and image max instance limit

[Sarath Chandra]

Hi Atlassian,

We are having a specific requirement:

1. Have 3+ instances of Normal linux image.
2. Have at most 2 instances of linux image configured to run long running selenium tests.

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?

[Przemek Bruski · Accepted solution]

No, it's not possible, sorry. As a workaround What if you added a requirement to your smaller jobs that wouldn't be fulfilled by the Selenium images?

[Sarath Chandra]

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?

[Przemek Bruski]

A reasonable requirement, but it's not possible, sorry.

[Sarath Chandra]

Can it be done using some scripts? In the instance startup script we could poll to get number of instances of this image etc?

[Przemek Bruski]

Instances startup script is run after the instance is started.

[Louis Burton]

Is there an enhancement request for this?