-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
3
-
Hi Team,
Requesting for a configuration item restricting a maximum instances of a particular type of elastic agent, that could be set below the global limit.
The number of elastic images should be configurable for each elastic image (and not only a maximum number of all elastic instances).
If one team is committing first on a day, then their jobs will trigger the start of many elastic instances . If later another team commits, then in worst case the maximum number of elastic instances is already reached, and so no elastic instance can start anymore.
A solution would be to limit the number of elastic instances for each image individually.
P.S.: This is a critical request from one of our esteemed customers in the organisation.
[BAM-21431] Configure maximum number of elastic instances
We found following workaround for this missing feature of Bamboo:
In AWS License Manager you can now limit the number of instances for a specific AMI.
Nevertheless: Any updates on this topic from Bamboo site?
This is indeed a blocking issue due to the limiting of elastic instances based on remote agents in the license, combined with wanting dedicated instances for specific teams/projects.
If one of our teams does a full build and test of it's project it will quickly spin up all machines that it can and fills the full agent allowence.
We need to be able to set a limit on the amount of instances it can create based on the image type.
Hello,
this issue is now really blocking is in our whole enterprise.
We have some team which is running a huge amount of jobs, which triggers the start of many elastic instances of their image once they start commiting in the morning (until the maximum number is reached). All other teams are now blocked since no new instances can be started.
Of course we could increase the number of maximum number of instances at all, but this does not solve the actual issue. Then we come to the same point in few weeks.
IMHO this feature request should only be a small code change (if/else) and it does not change any previous behavior (e.g. the value could be defaulted to 0 which means not limited). Isn't it?
Why can it not be implemented by Atlassian in a fast way?
I would appreciate this feature.
It is essential for the work with elastic images. Also if I want to optimize the costs, I maybe want to limit the number of expensive agents (e.g. maximum 2 instances of this image). The feature of an additional max-instances-per-image value would be perfect!
This feature is not on our current roadmap, as we are currently focusing on delivering ephemeral kubernetes agents and improving availability and resilience of the product. It's possible that we will reconsider working on it at some point in time but, to avoid creating any false expectations, I must emphasize that it won't happen in the nearest future.
Thanks,
Martyna Wojtas
Product Manager, Bamboo