1. 08 Dec, 2016 1 commit
  2. 01 Dec, 2016 1 commit
    • Yorick Peterse's avatar
      Pass commit data to ProcessCommitWorker · 22942061ddc3
      Yorick Peterse authored
      By passing commit data to this worker we remove the need for querying
      the Git repository for every job. This in turn reduces the time spent
      processing each job.
      
      The migration included migrates jobs from the old format to the new
      format. For this to work properly it requires downtime as otherwise
      workers may start producing errors until they're using a newer version
      of the worker code.
      22942061ddc3
  3. 30 Nov, 2016 1 commit
  4. 29 Nov, 2016 1 commit
  5. 28 Nov, 2016 2 commits
  6. 23 Nov, 2016 1 commit
  7. 22 Nov, 2016 1 commit
  8. 18 Nov, 2016 4 commits
  9. 17 Nov, 2016 10 commits
  10. 16 Nov, 2016 3 commits
  11. 11 Nov, 2016 2 commits
  12. 10 Nov, 2016 2 commits
  13. 07 Nov, 2016 2 commits
  14. 06 Nov, 2016 1 commit
  15. 04 Nov, 2016 3 commits
  16. 26 Oct, 2016 3 commits
  17. 24 Oct, 2016 1 commit
    • Stan Hu's avatar
      Fix reply-by-email not working due to queue name mismatch · 38170b8c8ebe
      Stan Hu authored
      mail_room was configured to deliver mail to the `incoming_email`
      queue while `EmailReceiveWorker` was reading the `email_receiver`
      queue. Adds a migration that repeats the work of a previous
      migration to ensure all mails that wound up in the old
      queue get processed.
      
      Closes #23689
      38170b8c8ebe
  18. 21 Oct, 2016 1 commit
    • Yorick Peterse's avatar
      Re-organize queues to use for Sidekiq · 02c0ae5ed1f6
      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
      02c0ae5ed1f6