Limit the containers available to a single repo within an organisation
Our organisation has an issue of one repo taking 95% of Circle containers at any given time of any given day. They have extremely long build and test times and they seem to push every single commit. This gets in the way of other teams. It would be good to be able to put limits on the number of containers a single repo can use of our organisation's allowance. A good way for this to be handled would be once they hit their allowance their builds are always lower priority than other repos.
May 20, 2020
There are no plans to support this, as we are moving towards usage-based plans that addresses this concern. Upgrading to our Performance Plan would provide elasticity in concurrency that would prevent this issue.