1. 15 Jun, 2017 1 commit
  2. 05 Jun, 2017 1 commit
  3. 01 Jun, 2017 2 commits
  4. 31 May, 2017 1 commit
  5. 25 May, 2017 2 commits
  6. 24 May, 2017 1 commit
  7. 22 May, 2017 3 commits
  8. 15 May, 2017 1 commit
    • Zeger-Jan van de Weg's avatar
      Do not schedule pipelines if the user can't · 9f933953
      Zeger-Jan van de Weg authored
      When the owner of a pipelines schedule was either blocked or was removed
      from the project, the pipeline schedular would still schedule the
      pipeline.
      
      This would than fail however, given the user had no access to the
      project and it contents. However, a better way to handle it would be to
      not schedule it at all. Furthermore, from now on, such schedules will be
      deactivated so the schedule worker can ignore it on the next runs.
      9f933953
  9. 12 May, 2017 1 commit
  10. 10 May, 2017 3 commits
  11. 09 May, 2017 1 commit
  12. 07 May, 2017 1 commit
  13. 05 May, 2017 4 commits
  14. 04 May, 2017 4 commits
  15. 03 May, 2017 1 commit
  16. 01 May, 2017 1 commit
  17. 24 Apr, 2017 3 commits
  18. 21 Apr, 2017 1 commit
  19. 19 Apr, 2017 1 commit
    • Drew Blessing's avatar
      Add retry to system hook worker · 354e37b8
      Drew Blessing authored
      The default number of Sidekiq retries is 25 over about 21 days.
      If an external system is unavailable for a length of time, hooks
      can pile up in the Sidekiq queues. If the situation gets bad enough
      the retry jobs dropping back into the main queue can slow down
      other jobs. Limit the retries to a sane number to avoid this
      scenario.
      354e37b8
  20. 14 Apr, 2017 7 commits