An error occurred fetching the project authors.
  1. 10 May, 2017 1 commit
  2. 21 Apr, 2017 1 commit
  3. 06 Apr, 2017 1 commit
  4. 16 Mar, 2017 1 commit
  5. 24 Feb, 2017 1 commit
  6. 23 Feb, 2017 5 commits
  7. 15 Feb, 2017 3 commits
  8. 03 Feb, 2017 1 commit
    • Filipa Lacerda's avatar
      Fix broken tests · c5f5ce88
      Filipa Lacerda authored
      Rename Build to Job
      
      Replace "Builds" by "Jobs" and fix broken specs
      
      Replace "Builds" by "Jobs"
      
      Fix broken spinach test
      
      Fix broken test
      
      Remove `˙` at the beginning of the file
      
      Fix broken spinach test
      
      Fix broken tests
      
      Changes after review
      c5f5ce88
  9. 01 Feb, 2017 1 commit
  10. 25 Jan, 2017 1 commit
  11. 20 Jan, 2017 1 commit
  12. 04 Jan, 2017 1 commit
    • Lin Jen-Shin's avatar
      WIP: Add tests and make sure that headers are set · 8c9a4ed3
      Lin Jen-Shin authored
      * We realized that headers were not set whenever we give 204
        because `render_api_error!` doesn't preserve the headers.
      
      * We also realized that `update_runner_info` would be called in
        POST /builds/register every time therefore runner is updated
        every time, ticking the queue, making this last_update didn't
        work very well, and the test would be failing due to that.
      8c9a4ed3
  13. 21 Dec, 2016 1 commit
  14. 19 Dec, 2016 4 commits
  15. 14 Dec, 2016 1 commit
  16. 28 Nov, 2016 1 commit
  17. 21 Nov, 2016 2 commits
  18. 16 Nov, 2016 1 commit
  19. 15 Nov, 2016 1 commit
  20. 01 Nov, 2016 1 commit
  21. 03 Oct, 2016 1 commit
  22. 19 Sep, 2016 1 commit
  23. 15 Sep, 2016 1 commit
  24. 13 Sep, 2016 3 commits
  25. 06 Sep, 2016 1 commit
  26. 05 Sep, 2016 1 commit
  27. 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
  28. 09 Aug, 2016 1 commit