merge-train pipeline schedules changed unexpectedly
Problem Statement
The merge-train
pipeline schedule responsible for syncing Security to Canonical is activated anytime we begin a security release. Most recently, it was discovered the schedule for running that pipeline had been incorrect set to run at 1600UTC daily. This normally, or should, run much more frequently to reduce the potential that the merge-train
needs to deal with merge conflicts.
Since any user can change the schedule, this can change without notification to us and leave us in a bad state. This recently led to: production#15941 (closed)
Solution
Since release-tools toggles whether or not the pipeline should run, I propose we ask that release-tools
validates the cron schedule to be as desired. This toggle runs every hour, so perhaps when run, it first validates if it needs to be active or not, and if active, validate and set the schedule as desired. If this solution is deemed acceptable, we should carry this method into the other merge-train
pipelines that release-tools
toggles (omnibus, gitaly).