1. 09 8月, 2017 1 次提交
  2. 02 8月, 2017 1 次提交
  3. 27 7月, 2017 1 次提交
  4. 20 7月, 2017 1 次提交
  5. 19 7月, 2017 1 次提交
  6. 17 7月, 2017 1 次提交
  7. 05 7月, 2017 1 次提交
  8. 08 6月, 2017 1 次提交
  9. 06 6月, 2017 3 次提交
  10. 05 6月, 2017 2 次提交
  11. 03 6月, 2017 1 次提交
  12. 02 6月, 2017 2 次提交
  13. 31 5月, 2017 1 次提交
  14. 30 5月, 2017 2 次提交
  15. 24 5月, 2017 1 次提交
  16. 15 5月, 2017 1 次提交
  17. 09 5月, 2017 1 次提交
  18. 08 5月, 2017 1 次提交
  19. 06 4月, 2017 3 次提交
  20. 05 4月, 2017 8 次提交
  21. 28 3月, 2017 1 次提交
  22. 16 3月, 2017 1 次提交
  23. 22 2月, 2017 1 次提交
  24. 15 12月, 2016 1 次提交
  25. 11 8月, 2016 1 次提交
    • 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
  26. 18 7月, 2016 1 次提交