| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add latest changes from gitlab-org/gitlab@13-4-stable-ee | GitLab Bot | 2020-09-19 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | 2020-07-20 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-02-25 | 1 | -3/+3 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-80898 | GitLab Bot | 2019-12-16 | 1 | -1/+1 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-13 | 1 | -2/+2 |
| | | |||||
| * | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-09-18 | 1 | -1/+1 |
| | | |||||
| * | Make pipeline schedule worker resilientset-real-next-run-at-for-preventing-duplciate-pipeline-creations | Shinya Maeda | 2019-06-03 | 1 | -1/+31 |
| | | | | | | | | | | | | | | 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. | ||||
| * | Add frozen_string_literal to spec/workersfrozen_string_spec_workers | Thong Kuah | 2019-04-01 | 1 | -0/+2 |
| | | | | | Adds `# frozen_string_literal: true` to spec/workers ruby files | ||||
| * | Address some comments with running a pipeline schedule | Stan Hu | 2017-12-12 | 1 | -6/+9 |
| | | |||||
| * | Add button to run scheduled pipeline immediately | Stan Hu | 2017-12-12 | 1 | -0/+36 |
| Closes #38741 | |||||
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |