summaryrefslogtreecommitdiff
path: root/spec/lib/gitlab/ci/cron_parser_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42GitLab Bot2020-10-211-7/+7
|
* Add latest changes from gitlab-org/gitlab@13-2-stable-eeGitLab Bot2020-07-201-1/+1
|
* Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot2020-05-201-136/+178
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-11-261-0/+16
|
* Add frozen_string_literal to spec/lib (part 1)Thong Kuah2019-07-261-0/+2
| | | | | Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
* Remove workaround by upgrading Fugit gemFabio Pitino2019-05-071-7/+0
| | | | | | | | Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/58241 * Upgrade Fugit gem to 1.2.1 which recognizes cron expressions for invalid days * Reverted previously implemented workaround * Leave test case which previously exposed the bug
* Rescue RuntimeError when "too many loops" occurFabio Pitino2019-05-071-0/+7
| | | | | | With this workaround we temporarily prevent an exception from Fugit gem to be raised in Gitlab::Ci::CronParser
* Write test that exposes bug with Fugit gemFabio Pitino2019-05-071-0/+7
|
* Add TimeCop freeze for DST and Regular timefix/sm/39817-fix-cron_parser_spec-rbShinya Maeda2017-11-051-6/+42
|
* Fix lazy error handling of cron parserDosuken shinya2017-05-031-9/+79
|
* Implement a offset calculation on cron_parser_specShinya Maeda2017-04-061-1/+1
|
* Rename cron_time_zone to cron_timezone. Separate add_concurrent_foreign_key.Shinya Maeda2017-04-061-14/+14
|
* Separate cron_valid? and cron_time_zone_valid?Shinya Maeda2017-04-061-13/+25
|
* Dry up next_time_from. Move cron_parser_spec to appropriate location.Shinya Maeda2017-04-061-0/+104