CI Limits set at the Instance Level

Release notes

GitLab instance Admins may want to create limits on CI related events like how many jobs a project may run concurrently to reduce the likelihood of resource exhaustion and the instance becoming unresponsive or unstable.

Now you can set these limits in the administration console to configure the GitLab instance to your needs.

Problem to solve

Admins should be able to set limits for things like:

• ci_active_jobs
• ci_active_pipelines
• ci_daily_pipeline_schedule_triggers
• ci_instance_level_variables
• ci_jobs_trace_size_limit
• ci_needs_size_limit
• ci_pipeline_deployments
• ci_pipeline_schedules
• ci_pipeline_size
• ci_project_subscriptions
• ci_registered_group_runners
• ci_registered_project_runners

Proposal

Intended users

Feature Usage Metrics