Make clear in create scheduled pipeline UI that actual run times depend on separate GitLab instance config
Problem to solve
When scheduling a new pipeline (especially if using cron syntax), the end user doing so is often under the impression that the pipeline will actually run at the defined time.
In actual fact, the time at which the pipeline will be created is dependent on the gitlab_rails['pipeline_schedule_worker_cron'] configuration in the instance's gitlab.rb file. The default for that is to create scheduled pipelines at the 19th minute of every hour.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
Further details
Proposal
If possible, we should add the actual value from gitlab_rails['pipeline_schedule_worker_cron'], or at least indicate that their pipelines may not run at the exact time scheduled, even if they ensure that runners are available.
Here's what a 500-seat premium customer had to say (Zendesk, internal use only):
For a regular end user scheduling a pipeline there is nothing there that says anything about the global configuration on the rb file. So they go ahead and schedule the jobs only to find out after many tries that is not working as expected. Ideally the UI should reflect the current rb configuration pickup period or something like that.
It's worth noting that this problem would go away if #22003 (closed) is accepted
Permissions and Security
Documentation
https://docs.gitlab.com/ee/user/project/pipelines/schedules.html