Scheduled pipeline minute cron syntax doesn't work correctly if not set to 0
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
When you are setting pipeline schedule to run e.g. 7 18 2 4 * which is At 18:07 on day-of-month 2 in April it would instead be scheduled to At 19:00 on day-of-month 2 in April incorrectly interpreting minute value.
Steps to reproduce
- Open Pipeline Schedules
- Configure pipeline to run at
7 18 2 4 * - Save this value
- Check when the pipeline is scheduled to run with hover over value in Next Run column
- It will output 2 April 2024 at 19:00:00 CEST
Example Project
What is the current bug behavior?
When the pipeline schedule is set to run at minute other than 0 e.g. 7 18 2 4 * - it will run an hour later in this case at minute 0 or At 19:00 on day-of-month 2 in April
What is the expected correct behavior?
When the pipeline is scheduled to run at minute other than 0 e.g. 7 18 2 4 * it runs At 18:07 on day-of-month 2 in April
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)