1. 05 Jul, 2017 1 commit
  2. 24 May, 2017 1 commit
  3. 23 May, 2017 1 commit
  4. 17 May, 2017 1 commit
  5. 09 May, 2017 1 commit
  6. 05 May, 2017 2 commits
  7. 28 Apr, 2017 1 commit
  8. 07 Apr, 2017 1 commit
  9. 06 Apr, 2017 1 commit
  10. 23 Mar, 2017 6 commits
  11. 23 Feb, 2017 2 commits
  12. 24 Jan, 2017 1 commit
  13. 18 Jan, 2017 2 commits
  14. 21 Sep, 2016 1 commit
  15. 19 Sep, 2016 1 commit
  16. 16 Sep, 2016 1 commit
  17. 13 Sep, 2016 2 commits
  18. 01 Sep, 2016 3 commits
  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. 19 Jul, 2016 2 commits
  21. 18 Jul, 2016 4 commits
  22. 16 Jun, 2016 2 commits
  23. 13 Jun, 2016 2 commits