GitLab Bot
d6ce16a407
Add latest changes from gitlab-org/gitlab@master
2022-01-28 12:17:26 +00:00
GitLab Bot
ff3bb8c2eb
Add latest changes from gitlab-org/gitlab@master
2021-07-29 03:09:06 +00:00
GitLab Bot
7e5b78ee03
Add latest changes from gitlab-org/gitlab@master
2021-07-21 12:09:35 +00:00
GitLab Bot
d899d2a373
Add latest changes from gitlab-org/gitlab@master
2021-04-30 18:10:09 +00:00
GitLab Bot
33795139ea
Add latest changes from gitlab-org/gitlab@master
2020-02-19 18:09:10 +00:00
GitLab Bot
b133cb2468
Add latest changes from gitlab-org/gitlab@master
2020-02-12 00:09:00 +00:00
GitLab Bot
6b833f1e03
Add latest changes from gitlab-org/gitlab@master
2020-02-04 15:08:40 +00:00
GitLab Bot
3fe9588b1c
Add latest changes from gitlab-org/gitlab@master
2019-10-30 15:14:17 +00:00
GitLab Bot
25989ab7ef
Add latest changes from gitlab-org/gitlab@master
2019-10-18 11:11:44 +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
Shinya Maeda
28f785404a
Prevent concurrent execution of PipelineScheduleWorker
...
Currently, PipelineScheduleWorker is fired in a short period on
our production server. We can stop this behavior by locking the
execution thread with in_lock method.
2019-04-28 12:59:23 +07:00
Nick Thomas
9f05e97aad
Run rubocop -a
2019-03-13 13:42:43 +00:00
Shinya Maeda
d56d419a79
Squashed commit of the following:
...
commit 0c00e52d339f8471a6ea425d5a4a59751a3f4a35
Author: Shinya Maeda <shinya@gitlab.com>
Date: Fri Nov 30 15:41:46 2018 +0900
Update schedules.md
commit 0ae56bf5a0ba9254d2ebd4c846395113ae72d686
Merge: c143777c9f2 9ce28bf08ba5f46278572ee8c40fc1fbbe5ccd1b8a581d531b
2018-11-30 16:32:52 +09:00
Yorick Peterse
2039c8280d
Disable existing offenses for the CodeReuse cops
...
This whitelists all existing offenses for the various CodeReuse cops, of
which most are triggered by the CodeReuse/ActiveRecord cop.
2018-09-11 17:32:00 +02:00
gfyoung
dfbe5ce435
Enable frozen string literals for app/workers/*.rb
2018-06-27 07:23:28 +00:00
Douwe Maan
0b15570e49
Add ApplicationWorker and make every worker include it
2017-12-05 11:59:39 +01:00
Shinya Maeda
65cadff190
Avoid deactivation when pipeline schedules execute a commit includes [ci skip]
2017-11-23 02:53:34 +09:00
Lin Jen-Shin
56ea7a0cfe
Merge allowed_to_create? into CreatePipelineService
2017-07-05 21:55:35 +08:00
Kamil Trzcinski
161af17c1b
Introduce source to pipeline entity
2017-05-31 14:17:49 +02:00
Z.J. van de Weg
9f93395389
Do not schedule pipelines if the user can't
...
When the owner of a pipelines schedule was either blocked or was removed
from the project, the pipeline schedular would still schedule the
pipeline.
This would than fail however, given the user had no access to the
project and it contents. However, a better way to handle it would be to
not schedule it at all. Furthermore, from now on, such schedules will be
deactivated so the schedule worker can ignore it on the next runs.
2017-05-15 10:01:29 +02:00
Zeger-Jan van de Weg
8df3997a92
Add Pipeline Schedules that supersedes experimental Trigger Schedule
2017-05-07 22:35:56 +00:00
