- 23 Feb, 2017 4 commits
-
-
Douwe Maan authored
This reverts commit e00fb2bdc2090e9cabeb1eb35a2672a882cc96e9. # Conflicts: # .rubocop.yml # .rubocop_todo.yml # lib/gitlab/ci/config/entry/global.rb # lib/gitlab/ci/config/entry/jobs.rb # spec/lib/gitlab/ci/config/entry/factory_spec.rb # spec/lib/gitlab/ci/config/entry/global_spec.rb # spec/lib/gitlab/ci/config/entry/job_spec.rb # spec/lib/gitlab/ci/status/build/factory_spec.rb # spec/lib/gitlab/incoming_email_spec.rb
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
Douwe Maan authored
-
- 05 Jan, 2017 1 commit
-
-
Lin Jen-Shin authored
-
- 08 Dec, 2016 1 commit
-
-
Lin Jen-Shin authored
commits from the other repository. We'll cleanup the tmp ref after we're done with our business.
-
- 21 Oct, 2016 1 commit
-
-
Yorick Peterse authored
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
-
- 19 Aug, 2016 1 commit
-
-
Sean McGivern authored
`after_sha` maps to the source branch, as it's the head of our compare, so these were just the wrong way around.
-
- 03 Aug, 2016 2 commits
-
-
Paco Guzman authored
So we have raw_diffs too
-
Paco Guzman authored
This object will manage Gitlab::Git::Compare instances
-
- 21 Jul, 2016 1 commit
-
-
Sean McGivern authored
-
- 06 Jul, 2016 1 commit
-
-
Douwe Maan authored
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 31 May, 2016 1 commit
-
-
Stan Hu authored
EmailsOnPushWorker was using the default queue, which made it impossible to prioritize MergeWorker and other key workers with a separate Sidekiq process.
-
- 17 May, 2016 1 commit
-
-
Sean McGivern authored
Based on: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/151
-
- 11 May, 2016 1 commit
-
-
Sean McGivern authored
The repository push email can be very expensive to generate, especially with syntax-highlighted diffs. Instead of generating the email for each recipient, generate one email object and reset the Message-Id and To headers for each recipient. (Cloning would also be expensive in the case of large emails, although probably not as bad as generating from scratch.)
-
- 25 Nov, 2015 1 commit
-
-
Valery Sizov authored
-
- 20 Aug, 2015 1 commit
-
-
Stan Hu authored
Gracefully handle SMTP user input errors (e.g. incorrect email addresses) to prevent Sidekiq retries Closes https://github.com/gitlabhq/gitlabhq/issues/9560
-
- 26 Mar, 2015 1 commit
-
-
Douwe Maan authored
-
- 23 Mar, 2015 1 commit
-
-
Douwe Maan authored
-
- 18 Mar, 2015 1 commit
-
-
Douwe Maan authored
-
- 10 Mar, 2015 1 commit
-
-
Douwe Maan authored
-
- 25 Feb, 2015 3 commits
-
-
Douwe Maan authored
See #1924.
-
Douwe Maan authored
See #1950
-
Douwe Maan authored
See #1809.
-
- 14 Nov, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 29 Jul, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 12 Feb, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 18 Dec, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-