1. 13 2月, 2017 1 次提交
  2. 06 2月, 2017 1 次提交
  3. 25 1月, 2017 2 次提交
  4. 20 1月, 2017 2 次提交
  5. 15 12月, 2016 1 次提交
  6. 27 11月, 2016 1 次提交
  7. 25 11月, 2016 4 次提交
  8. 14 11月, 2016 3 次提交
  9. 09 11月, 2016 2 次提交
  10. 08 11月, 2016 1 次提交
  11. 26 10月, 2016 1 次提交
  12. 17 10月, 2016 3 次提交
  13. 14 10月, 2016 1 次提交
  14. 08 10月, 2016 1 次提交
  15. 01 10月, 2016 2 次提交
  16. 30 9月, 2016 2 次提交
  17. 23 9月, 2016 3 次提交
  18. 14 9月, 2016 2 次提交
  19. 01 9月, 2016 1 次提交
  20. 19 8月, 2016 2 次提交
  21. 16 8月, 2016 1 次提交
  22. 12 8月, 2016 1 次提交
  23. 11 8月, 2016 2 次提交
    • K
      Pre-create all builds for Pipeline when a trigger is received · 39203f1a
      Kamil Trzcinski 提交于
      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
    • L
      4b559c9a