Read about our upcoming Code of Conduct on this issue

  1. 24 Oct, 2016 1 commit
  2. 17 Oct, 2016 2 commits
  3. 14 Oct, 2016 2 commits
  4. 13 Oct, 2016 2 commits
  5. 06 Oct, 2016 2 commits
  6. 04 Oct, 2016 1 commit
  7. 03 Oct, 2016 1 commit
  8. 30 Sep, 2016 1 commit
  9. 22 Sep, 2016 1 commit
  10. 21 Sep, 2016 3 commits
  11. 20 Sep, 2016 1 commit
  12. 19 Sep, 2016 4 commits
  13. 16 Sep, 2016 1 commit
  14. 15 Sep, 2016 1 commit
  15. 13 Sep, 2016 1 commit
  16. 09 Sep, 2016 1 commit
  17. 01 Sep, 2016 4 commits
  18. 31 Aug, 2016 1 commit
  19. 25 Aug, 2016 1 commit
  20. 18 Aug, 2016 1 commit
  21. 17 Aug, 2016 1 commit
  22. 12 Aug, 2016 2 commits
  23. 11 Aug, 2016 2 commits
    • Kamil Trzcinski's avatar
    • Kamil Trzcinski's avatar
      Pre-create all builds for Pipeline when a trigger is received · 9c9a8bc446d7
      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.
      9c9a8bc446d7
  24. 04 Aug, 2016 1 commit
  25. 29 Jul, 2016 2 commits