Request: Ability to change maximum scheduled pipeline frequency on a per-project or per-group level

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

A customer requests the ability to change maximum scheduled pipeline frequency on a per-project or per-group level when a group- or project-specific runner is registered.

The customer's use case is to allow projects or groups with their own runners to run scheduled pipelines more frequently than the limitation defined by the global gitlab_rails['pipeline_schedule_worker_cron'] value, thus allowing more liberal use of specific runners without congesting shared runners.