1. 21 Aug, 2017 5 commits
  2. 01 Aug, 2017 1 commit
  3. 10 Jul, 2017 1 commit
  4. 22 Jun, 2017 1 commit
  5. 02 Jun, 2017 1 commit
  6. 27 Apr, 2017 1 commit
    • Alexander Randa's avatar
      Implement web hooks logging · 86a966b67dcc
      Alexander Randa authored
      * implemented logging of project and system web hooks
      * implemented UI for user area (project hooks)
      * implemented UI for admin area (system hooks)
      * implemented retry of logged webhook
      * NOT imeplemented log remover
      86a966b67dcc
  7. 08 May, 2017 1 commit
    • Toon Claes's avatar
      Use worker to destroy namespaceless projects in post-deploy · 824e4609c282
      Toon Claes authored
      Destroying projects can be very time consuming. So instead of destroying them in
      the post-deploy, just schedule them and make Sidekiq do the hard work.
      
      They are scheduled in batches of 5000 records. This way the number of database
      requests is limited while also the amount data read to memory is limited.
      824e4609c282
  8. 05 May, 2017 1 commit
  9. 04 May, 2017 1 commit
  10. 10 Apr, 2017 1 commit
  11. 07 Mar, 2017 2 commits
  12. 22 Feb, 2017 1 commit
  13. 17 Feb, 2017 1 commit
  14. 15 Dec, 2015 1 commit
  15. 21 Dec, 2016 1 commit
    • Vincent Wong's avatar
      Record and show last used date of SSH Keys · 08ff04185476
      Vincent Wong authored
      Addresses: Issue #13810
      
      1. Adds a last_used_at attribute to the Key table/model
      2. Update a key's last_used_at whenever it gets used
      3. Display how long ago an ssh key was last used
      08ff04185476
  16. 17 Dec, 2016 1 commit
  17. 11 Oct, 2016 1 commit
  18. 15 Nov, 2016 1 commit
  19. 21 Sep, 2016 1 commit
    • Toon Claes's avatar
      Add button to delete all merged branches · f20b6c5a8c7a
      Toon Claes authored
      It adds a button to the branches page that the user can use to delete
      all the branches that are already merged. This can be used to clean up
      all the branches that were forgotten to delete while merging MRs.
      
      Fixes #21076.
      f20b6c5a8c7a
  20. 07 Oct, 2016 1 commit
    • Yorick Peterse's avatar
      Process commits in a separate worker · e0fe6e6916ff
      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.
      e0fe6e6916ff
  21. 22 Oct, 2016 1 commit
  22. 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