BigW Consortium Gitlab

  1. 16 Jun, 2016 1 commit
  2. 03 Jun, 2016 2 commits
  3. 25 May, 2016 1 commit
  4. 24 May, 2016 1 commit
  5. 18 May, 2016 1 commit
  6. 15 May, 2016 1 commit
  7. 04 May, 2016 2 commits
  8. 29 Apr, 2016 2 commits
  9. 26 Apr, 2016 1 commit
  10. 25 Apr, 2016 1 commit
  11. 18 Apr, 2016 3 commits
  12. 15 Apr, 2016 1 commit
  13. 13 Apr, 2016 1 commit
    • Fix repository cache invalidation issue when project is recreated with an empty repo · 2ce7559d
      Stan Hu authored
      To reproduce:
      
      1. Create a project with some content
      2. Rename the project
      3. Create a new project with the same name.
      4. Boom - 404.
      
      After step 2, the branch and tag counts were not being cleared. This would
      cause `repository.has_visible_content?` to erroneously return `true`
      for the newly-created project.
      
      Closes #13384
  14. 09 Apr, 2016 1 commit
  15. 07 Apr, 2016 1 commit
  16. 04 Apr, 2016 1 commit
  17. 01 Apr, 2016 1 commit
  18. 27 Mar, 2016 1 commit
  19. 25 Mar, 2016 2 commits
  20. 24 Mar, 2016 1 commit
  21. 19 Mar, 2016 1 commit
    • Cache output of Repository#exists? · 68a4c98f
      Yorick Peterse authored
      This caches the output of Repository#exists? in Redis while making sure
      it's flushed properly when creating new repositories, deleting them,
      etc.
      
      For the ProjectWiki tests to work I had to make ProjectWiki#create_repo!
      public as testing private methods in RSpec is a bit of a pain.
  22. 17 Mar, 2016 2 commits
    • Added tests for Repository#build_cache · dd4b7897
      Yorick Peterse authored
    • Cache project avatars stored in Git · cd05d3f7
      Yorick Peterse authored
      The avatar logic has been moved from Project to Repository as this makes
      caching easier. The logic itself in turn has been changed so that the
      logo file names are cached in Redis. This cache is flushed upon pushing
      a commit but _only_ if:
      
      1. The commit was pushed to the default branch
      2. The commit actually changes any of the logo files
      
      If no branch or commit is given the cache is flushed anyway, this
      ensures that calling Repository#expire_cache without any arguments still
      flushes the avatar cache (e.g. this is used when removing a project).
      
      Fixes gitlab-org/gitlab-ce#14363
  23. 16 Mar, 2016 1 commit
  24. 08 Mar, 2016 5 commits
  25. 07 Mar, 2016 2 commits
  26. 02 Mar, 2016 1 commit
  27. 25 Feb, 2016 1 commit
  28. 20 Feb, 2016 1 commit
    • Flush emptiness caches whenever needed · e0cb3212
      Yorick Peterse authored
      This ensures that the emptiness cache (used for Repository#empty? and
      Repository#has_visible_content?) is flushed after comitting changes
      (using the web editor, API or Git) for new repositories. Once a
      repository is no longer empty there's no need to explicitly flush the
      cache for Repository#empty?. The cache for
      Repository#has_visible_content? in turn is already flushed whenever
      needed.
      
      Fixes gitlab-org/gitlab-ce#13387