Commit Graph

25 Commits

Author SHA1 Message Date
GitLab Bot 5849e597a0 Add latest changes from gitlab-org/gitlab@master 2023-06-27 06:08:04 +00:00
GitLab Bot 849e6f56ae Add latest changes from gitlab-org/gitlab@master 2023-03-20 15:08:26 +00:00
GitLab Bot 12166c0faf Add latest changes from gitlab-org/gitlab@master 2023-02-16 12:08:03 +00:00
GitLab Bot c6c5dd8848 Add latest changes from gitlab-org/gitlab@master 2023-02-08 15:08:59 +00:00
GitLab Bot c1efda3e21 Add latest changes from gitlab-org/gitlab@master 2023-02-03 03:07:34 +00:00
GitLab Bot 5b1258ee90 Add latest changes from gitlab-org/gitlab@master 2023-01-23 09:08:21 +00:00
GitLab Bot 6d4ce68742 Add latest changes from gitlab-org/gitlab@master 2023-01-16 12:07:42 +00:00
GitLab Bot fc0afaf7da Add latest changes from gitlab-org/gitlab@master 2023-01-11 12:07:18 +00:00
GitLab Bot af833d9730 Add latest changes from gitlab-org/gitlab@master 2022-12-02 18:07:23 +00:00
GitLab Bot 2b8ac36bdd Add latest changes from gitlab-org/gitlab@master 2022-11-14 00:11:26 +00:00
GitLab Bot 135dd0646b Add latest changes from gitlab-org/gitlab@master 2022-10-27 00:10:35 +00:00
GitLab Bot fd31bd1fc7 Add latest changes from gitlab-org/gitlab@master 2022-10-11 12:09:17 +00:00
GitLab Bot d6ce16a407 Add latest changes from gitlab-org/gitlab@master 2022-01-28 12:17:26 +00:00
GitLab Bot 813226e2ba Add latest changes from gitlab-org/gitlab@master 2021-09-20 18:12:35 +00:00
GitLab Bot 2af44d609e Add latest changes from gitlab-org/gitlab@master 2021-04-21 12:09:16 +00:00
GitLab Bot 49a897eff9 Add latest changes from gitlab-org/gitlab@master 2020-09-08 09:08:31 +00:00
GitLab Bot 2f47b6d8e1 Add latest changes from gitlab-org/gitlab@master 2020-06-26 09:08:59 +00:00
GitLab Bot a8c82a6395 Add latest changes from gitlab-org/gitlab@master 2020-02-25 03:08:49 +00:00
GitLab Bot d10a462fed Add latest changes from gitlab-org/gitlab@master 2019-12-16 12:07:43 +00:00
GitLab Bot 8cc5f27909 Add latest changes from gitlab-org/gitlab@master 2019-12-13 12:07:41 +00:00
GitLab Bot 80f61b4035 Add latest changes from gitlab-org/gitlab@master 2019-09-18 14:02:45 +00:00
Shinya Maeda 6a18a411a3 Make pipeline schedule worker resilient
Currently, pipeline schedule worker is unstable because it's
sometimes killed by excessive memory consumption.
In order to improve the performance, we add the following fixes:

1. next_run_at is always real_next_run, which means the value
   always takes into account of worker's cron schedule
1. Remove exlusive lock. This is already covered by real_next_run
   change.
1. Use RunPipelineScheduleWorker for avoiding memory killer.
   Memory consumption is spread to the multiple sidekiq worker.
2019-06-03 10:04:57 +07:00
Thong Kuah d6b952ad3e
Add frozen_string_literal to spec/workers
Adds `# frozen_string_literal: true` to spec/workers ruby files
2019-04-01 13:35:22 -03:00
Stan Hu f6966cfa63 Address some comments with running a pipeline schedule 2017-12-12 15:07:23 -08:00
Stan Hu 8e7f19c60b Add button to run scheduled pipeline immediately
Closes #38741
2017-12-12 15:07:23 -08:00