1. 08 12月, 2016 2 次提交
  2. 06 12月, 2016 2 次提交
  3. 01 12月, 2016 4 次提交
  4. 17 11月, 2016 1 次提交
  5. 16 11月, 2016 1 次提交
  6. 15 11月, 2016 1 次提交
  7. 11 11月, 2016 4 次提交
  8. 10 11月, 2016 1 次提交
  9. 11 10月, 2016 1 次提交
  10. 10 10月, 2016 2 次提交
  11. 06 10月, 2016 1 次提交
  12. 14 9月, 2016 1 次提交
  13. 07 9月, 2016 1 次提交
  14. 18 8月, 2016 1 次提交
  15. 17 8月, 2016 9 次提交
  16. 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
  17. 10 8月, 2016 5 次提交
  18. 22 7月, 2016 1 次提交
  19. 13 7月, 2016 1 次提交