An error occurred fetching the project authors.
  1. 23 Feb, 2017 1 commit
  2. 18 Jan, 2017 1 commit
  3. 07 Dec, 2016 1 commit
  4. 06 Dec, 2016 2 commits
  5. 19 Nov, 2016 1 commit
  6. 17 Nov, 2016 1 commit
    • Lin Jen-Shin's avatar
      Improve how we could cancel pipelines: · 6d1c5761
      Lin Jen-Shin authored
      * Introduce `HasStatus.cancelable` which we might be able to cancel
      * Cancel and check upon `cancelable`
      * Also cancel on `CommitStatus` rather than just `Ci::Build`
      
      Fixes #23635
      
      Fixes #17845
      6d1c5761
  7. 18 Oct, 2016 1 commit
  8. 04 Oct, 2016 1 commit
  9. 03 Oct, 2016 4 commits
  10. 01 Oct, 2016 2 commits
  11. 30 Sep, 2016 1 commit
  12. 29 Sep, 2016 1 commit
  13. 18 Sep, 2016 1 commit
  14. 13 Sep, 2016 1 commit
  15. 12 Sep, 2016 1 commit
  16. 25 Aug, 2016 1 commit
  17. 19 Aug, 2016 2 commits
  18. 15 Aug, 2016 1 commit
  19. 11 Aug, 2016 1 commit
    • Kamil Trzcinski's avatar
      Pre-create all builds for Pipeline when a trigger is received · 39203f1a
      Kamil Trzcinski authored
      This change simplifies a Pipeline processing by introducing a special new status: created.
      This status is used for all builds that are created for a pipeline.
      We are then processing next stages and queueing some of the builds (created -> pending) or skipping them (created -> skipped).
      This makes it possible to simplify and solve a few ordering problems with how previously builds were scheduled.
      This also allows us to visualise a full pipeline (with created builds).
      
      This also removes an after_touch used for updating a pipeline state parameters.
      Right now in various places we explicitly call a reload_status! on pipeline to force it to be updated and saved.
      39203f1a
  20. 10 Aug, 2016 1 commit
  21. 18 Jul, 2016 1 commit
  22. 27 Apr, 2016 1 commit
  23. 17 Apr, 2016 1 commit
  24. 16 Apr, 2016 2 commits
  25. 13 Apr, 2016 4 commits
  26. 12 Apr, 2016 3 commits
  27. 11 Apr, 2016 2 commits