1. 01 Apr, 2019 1 commit
  2. 10 Jul, 2018 1 commit
  3. 05 Mar, 2018 1 commit
  4. 16 Feb, 2018 3 commits
  5. 22 Aug, 2017 1 commit
  6. 21 Aug, 2017 1 commit
  7. 01 Aug, 2017 1 commit
  8. 21 Jun, 2017 1 commit
  9. 25 May, 2017 1 commit
  10. 22 May, 2017 1 commit
  11. 04 May, 2017 1 commit
  12. 04 Apr, 2017 1 commit
  13. 28 Mar, 2017 1 commit
  14. 23 Feb, 2017 2 commits
  15. 01 Dec, 2016 1 commit
    • Yorick Peterse's avatar
      Pass commit data to ProcessCommitWorker · 6b4d3356
      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.
      6b4d3356
  16. 07 Nov, 2016 1 commit
    • Yorick Peterse's avatar
      Process commits in a separate worker · 509910b8
      Yorick Peterse authored
      This moves the code used for processing commits from GitPushService to
      its own Sidekiq worker: ProcessCommitWorker.
      
      Using a Sidekiq worker allows us to process multiple commits in
      parallel. This in turn will lead to issues being closed faster and cross
      references being created faster. Furthermore by isolating this code into
      a separate class it's easier to test and maintain the code.
      
      The new worker also ensures it can efficiently check which issues can be
      closed, without having to run numerous SQL queries for every issue.
      509910b8