Indicate at project level if the number of jobs in active pipelines might exceed plan limit
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Original description
Maximum jobs in active pipelines is defined per plan for SaaS (see GitLab.com settings). If a new pipeline would cause the total number of jobs to exceed the limit, the pipeline fails with a `job_activity_limit_exceeded` error. Currently, it's difficult to proactively monitor jobs in active pipelines per project using the API.As the runner team looks at surfacing the number of jobs in active pipelines at group level, there's still a need to improve the experience at project level so users can avoid hitting the limit allowed by their plan.
Proposal TBD
The proposal here can be -- changing the default experience. Such as pausing the pipelines that are triggered while number of jobs are close to the limit and surfacing a badge or a banner to state why they are paused.
Original proposal
Edited by 🤖 GitLab Bot 🤖