BigW Consortium Gitlab

  1. 17 Jul, 2017 1 commit
  2. 07 Jul, 2017 5 commits
  3. 05 Jul, 2017 1 commit
  4. 28 Jun, 2017 2 commits
  5. 27 Jun, 2017 1 commit
  6. 21 Jun, 2017 1 commit
  7. 12 Jun, 2017 1 commit
  8. 05 Jun, 2017 2 commits
  9. 01 Jun, 2017 2 commits
  10. 31 May, 2017 1 commit
  11. 25 May, 2017 2 commits
  12. 22 May, 2017 3 commits
  13. 15 May, 2017 1 commit
    • Do not schedule pipelines if the user can't · 9f933953
      Z.J. 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.
  14. 12 May, 2017 1 commit
  15. 10 May, 2017 3 commits
  16. 09 May, 2017 1 commit
  17. 07 May, 2017 1 commit
  18. 05 May, 2017 4 commits
  19. 04 May, 2017 4 commits
  20. 03 May, 2017 1 commit
  21. 01 May, 2017 1 commit
  22. 24 Apr, 2017 1 commit