1. 19 Dec, 2017 1 commit
    • Zeger-Jan van de Weg's avatar
      Load commit in batches for pipelines#index · c6edae38
      Zeger-Jan van de Weg authored
      Uses `list_commits_by_oid` on the CommitService, to request the needed
      commits for pipelines. These commits are needed to display the user that
      created the commit and the commit title.
      
      This includes fixes for tests failing that depended on the commit
      being `nil`. However, now these are batch loaded, this doesn't happen
      anymore and the commits are an instance of BatchLoader.
      c6edae38
  2. 07 Dec, 2017 1 commit
  3. 05 Dec, 2017 1 commit
  4. 04 Dec, 2017 1 commit
  5. 31 Oct, 2017 1 commit
  6. 27 Oct, 2017 1 commit
    • Zeger-Jan van de Weg's avatar
      Cache commits on the repository model · 3411fef1
      Zeger-Jan van de Weg authored
      Now, when requesting a commit from the Repository model, the results are
      not cached. This means we're fetching the same commit by oid multiple times
      during the same request. To prevent us from doing this, we now cache
      results. Caching is done only based on object id (aka SHA).
      
      Given we cache on the Repository model, results are scoped to the
      associated project, eventhough the change of two repositories having the
      same oids for different commits is small.
      3411fef1
  7. 19 Sep, 2017 1 commit
  8. 11 Sep, 2017 1 commit
  9. 22 Aug, 2017 1 commit
  10. 16 Aug, 2017 1 commit
  11. 08 Aug, 2017 4 commits
  12. 03 Aug, 2017 1 commit
  13. 27 Jul, 2017 3 commits
  14. 20 Jul, 2017 1 commit
  15. 18 Jul, 2017 2 commits
  16. 13 Jul, 2017 1 commit
  17. 12 Jul, 2017 1 commit
  18. 27 Jun, 2017 2 commits
  19. 26 Jun, 2017 1 commit
  20. 20 Jun, 2017 1 commit
  21. 01 Jun, 2017 1 commit
  22. 18 May, 2017 1 commit
  23. 17 May, 2017 1 commit
    • Alejandro Rodríguez's avatar
      Compare ids of commits if present for equality test · 71569a9c
      Alejandro Rodríguez authored
      This solves a problem where commits populated with Gitaly were not equal
      to commits populated with Rugged. This is because Gitaly may not return
      all fields of a commit for optimizations purposes, which resulted in
      false negatives when comparing the same commit (commits with the same
      sha) with different sources.
      71569a9c
  24. 09 May, 2017 1 commit
  25. 23 Feb, 2017 2 commits
  26. 05 Jan, 2017 2 commits
  27. 27 Apr, 2013 1 commit
  28. 16 Apr, 2013 1 commit
  29. 15 Apr, 2013 1 commit
  30. 03 Apr, 2013 1 commit
  31. 02 Apr, 2013 1 commit