| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add latest changes from gitlab-org/gitlab@14-8-stable-eev14.8.0-rc42 | GitLab Bot | 2022-02-18 | 1 | -0/+17 |
| | | |||||
| * | 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@13-0-stable-ee | GitLab Bot | 2020-05-20 | 1 | -32/+0 |
| | | |||||
| * | Revert concurrent pipeline schedule creationrevert-concurrent-pipeline-schedule-creation | Shinya Maeda | 2019-06-18 | 1 | -0/+32 |
| | | | | | | | This commit reverts the previously introduced concurrent pipeline schedule creation which was a viable solution for mitigating inconsistent pipeline schedule by Sidekiq Memory Killer. | ||||
| * | Fix pipeline schedule when owner is nilfix-pipeline-schedule-owner-is-nil | Shinya Maeda | 2019-06-11 | 1 | -0/+8 |
| | | | | | Fixing the bug | ||||
| * | Make pipeline schedule worker resilientset-real-next-run-at-for-preventing-duplciate-pipeline-creations | Shinya Maeda | 2019-06-03 | 1 | -0/+28 |
| 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. | |||||
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |