Pipeline schedules timezone reset to UTC when editing
Summary
Customer reported in zd-250600(internal) reported a bug when the a pipeline schedule is going to be edit the previous selected timezone resets to UTC.
This has been confirmed in gitlab.com, the behavior seem to be every other time the pipeline gets edited.
Steps to reproduce
- Create a pipeline Schedule.
- Select a different timezone from UTC.
- Add variables to the schedule
- Save.
- Go edit the schedule pipeline.
- Time zone changed back to UTC.
Example Project
What is the current bug behavior?
Selected timezone reset to UTC
What is the expected correct behavior?
Selected timezone should be persisted on pipeline schedule.
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)
Possible fixes
Edited by Gerardo Gutierrez