Allow configuring per-project concurrency limits
B
Brett Langdon
We have a ton of projects which use CircleCI and one bad actor can easily use up our concurrency limit and cause queuing across our entire org.
It would be great if we could configure per-project specific concurrency limits so we can have finer grain control and limit the impact any one project could have on others.
Autopilot
Merged in a post:
Rate limiting on pipelines/workflows at project level
j
jalingam@coupang.com
I would like to have the ability to apply rate limits on pipelines or workflows at a project level in CircleCI. This feature would help manage heavy usage by slowing down users who are using the service extensively, without completely blocking them. It would be beneficial to have a case-by-case rate limiting capability to ensure critical users are not impacted by others' heavy usage.
Minjun Seong
jalingam@coupang.com Hi! I'm a product manager at CircleCI. Would love to learn more about this request.
- Could you elaborate on why you would want to "slow down" heavy users? Wouldn't that slow down your developers?
- How do you define "critical users"? Could you give examples on how heavy usage of some users negatively impact "critical users"?
Thank you!