GitLab Bot
33795139ea
Add latest changes from gitlab-org/gitlab@master
2020-02-19 18:09:10 +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
25989ab7ef
Add latest changes from gitlab-org/gitlab@master
2019-10-18 11:11:44 +00:00
GitLab Bot
80f61b4035
Add latest changes from gitlab-org/gitlab@master
2019-09-18 14:02:45 +00:00
Mayra Cabrera
0ab89d8e36
Add a rubocop for Rails.logger
...
Suggests to use a JSON structured log instead
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
2019-07-10 19:26:47 +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
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
Lin Jen-Shin
c94f417dfa
Use queue_namespace rather than enqueue_in
2017-12-18 23:42:31 +08:00
Stan Hu
0ea70802e1
Fix Sidekiq worker and make flash message return a link to the pipelines page
2017-12-12 15:07:24 -08: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
