Read about our upcoming Code of Conduct on this issue

  1. 01 Sep, 2016 1 commit
  2. 25 Aug, 2016 1 commit
  3. 22 Aug, 2016 2 commits
  4. 19 Aug, 2016 1 commit
  5. 18 Aug, 2016 2 commits
  6. 15 Aug, 2016 1 commit
  7. 13 Aug, 2016 1 commit
  8. 12 Aug, 2016 24 commits
  9. 11 Aug, 2016 2 commits
    • Kamil Trzcinski's avatar
      Pre-create all builds for Pipeline when a trigger is received · 9c9a8bc446d7
      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.
    • Paco Guzman's avatar
  10. 03 Aug, 2016 4 commits
  11. 02 Aug, 2016 1 commit
    • Paco Guzman's avatar
      Speedup DiffNote#active? on discussions, preloading noteables and avoid... · ec3ef23e22d7
      Paco Guzman authored
      Speedup DiffNote#active? on discussions, preloading noteables and avoid touching git repository to return diff_refs when possible
      - Preloading noteable we share the same noteable instance when more than one 
      discussion refers to the same noteable.
      - Any other call to that object that is cached in that object will be for any 
      - In those cases where merge_request_diff has all the sha stored to build a diff_refs get that 
      diff_refs using directly those sha instead accessing to the git repository to first get the 
      commits and later the sha.