1. 02 Oct, 2018 3 commits
  2. 11 Sep, 2018 1 commit
  3. 10 Aug, 2018 1 commit
  4. 16 Jul, 2018 1 commit
  5. 08 May, 2017 1 commit
  6. 07 May, 2017 1 commit
  7. 02 Apr, 2017 1 commit
  8. 06 Mar, 2017 5 commits
  9. 23 Feb, 2017 4 commits
  10. 06 Dec, 2016 1 commit
  11. 25 Nov, 2016 1 commit
  12. 24 Nov, 2016 1 commit
  13. 27 Oct, 2016 1 commit
  14. 26 Oct, 2016 4 commits
  15. 07 Oct, 2016 1 commit
  16. 03 Oct, 2016 2 commits
  17. 01 Oct, 2016 1 commit
  18. 30 Sep, 2016 1 commit
  19. 12 Sep, 2016 1 commit
  20. 31 Aug, 2016 1 commit
  21. 25 Aug, 2016 1 commit
  22. 12 Aug, 2016 1 commit
  23. 11 Aug, 2016 1 commit
    • 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