summaryrefslogtreecommitdiff
path: root/app/workers/update_merge_requests_worker.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-04-301-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-12-021-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-09-171-2/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-06-121-0/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-121-15/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-03-021-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-191-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-241-0/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-301-0/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-181-0/+2
|
* Add a rubocop for Rails.loggerMayra Cabrera2019-07-101-1/+1
| | | | | | Suggests to use a JSON structured log instead Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
* Disable existing offenses for the CodeReuse copsYorick Peterse2018-09-111-0/+2
| | | | | This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
* Enable frozen string literals for app/workers/*.rbgfyoung2018-06-271-0/+2
|
* Add ApplicationWorker and make every worker include itDouwe Maan2017-12-051-2/+1
|
* [ci-skip] lintingupdate-merge-worker-metricsMicael Bergeron2017-11-141-1/+0
|
* rework the logging to be simpler and add a thresholdmicael.bergeron2017-11-141-6/+12
|
* add simple logging to UpdateMergeRequestsWorker#performmicael.bergeron2017-11-131-1/+12
| | | | this is to try to debug #35914
* Revert "add metrics tagging to the sidekiq middleware"39958-updatemergerequestsworker-are-failing-on-metric-taggingmicael.bergeron2017-11-081-9/+0
| | | | | | This reverts commit d5859bb9d59b3750ac6e9b8c4c17d69c4c3ed077. This reverts commit 2b7e03cf699f9d266af585a1a9399c3e219fe063. This reverts commit 7799a9bc442738935104d3b047c257e5c5884d95.
* rework the UpdateMergeRequestsWorker#metrics_tags35914-merge-request-update-worker-is-slowmicael.bergeron2017-11-011-4/+2
|
* reword `targets` to `metric tags`micael.bergeron2017-10-311-3/+4
| | | | add changelog
* add metrics tagging to the sidekiq middlewaremicael.bergeron2017-10-311-0/+10
|
* Moved call of SystemHooksService from UpdateMergeRequestsWorker to ↵gpongelli2017-03-071-3/+0
| | | | GitPushServic…
* Re-organize queues to use for Sidekiqseparate-sidekiq-queuesYorick Peterse2016-10-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Dumping too many jobs in the same queue (e.g. the "default" queue) is a dangerous setup. Jobs that take a long time to process can effectively block any other work from being performed given there are enough of these jobs. Furthermore it becomes harder to monitor the jobs as a single queue could contain jobs for different workers. In such a setup the only reliable way of getting counts per job is to iterate over all jobs in a queue, which is a rather time consuming process. By using separate queues for various workers we have better control over throughput, we can add weight to queues, and we can monitor queues better. Some workers still use the same queue whenever their work is related. For example, the various CI pipeline workers use the same "pipeline" queue. This commit includes a Rails migration that moves Sidekiq jobs from the old queues to the new ones. This migration also takes care of doing the inverse if ever needed. This does require downtime as otherwise new jobs could be scheduled in the old queues after this migration completes. This commit also includes an RSpec test that blacklists the use of the "default" queue and ensures cron workers use the "cronjob" queue. Fixes gitlab-org/gitlab-ce#23370
* Extract project#update_merge_requests and SystemHooks to its own worker from ↵15463-extract-update-merge-requestsPaco Guzman2016-10-131-0/+16
GitPushService