Disable scheduled pipeline jobs in Gitlab Globally not just at the job level
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
We use Zerto - GitLab instance for test upgrade, backup/restore. This system uses production data (restored from production backup).
The full backup/restore will also restore CI/CD scheduled jobs. However these jobs fail to run in the Zerto environment and users get failed scheduled job notifications, in applications like - MatterMost, Microsoft Teams,etc..., which is very confusing. This can also lead to loss of productivity trying to chase down issues that don't really exist.
We had to do a quite a few work-arounds to stop them from occurring in MatterMost
There needs to be a way to disable scheduled jobs globally.
Best known workaround
Disable the Sidekiq-Cron worker to prevent scheduled jobs from running. In Omnibus, this can be configured using the gitlab_rails['pipeline_schedule_worker_cron'] setting.
Recommended by @engwan: #246842 (comment 754119658)
Note that this workaround has some issues, see: disabling pipeline_schedule_worker_cron in Rail... (#414936 - closed)