- 15 Apr, 2016 1 commit
-
-
Robert Schilling authored
-
- 13 Apr, 2016 1 commit
-
-
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
-
- 09 Apr, 2016 1 commit
-
-
Robert Speicher authored
Closes #14963.
-
- 07 Apr, 2016 1 commit
-
-
Stan Hu authored
Closes #14961
-
- 04 Apr, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
GitHub Pull Requests importer handle with the repository while importing data, we need to make sure that the cached values are valid.
-
- 01 Apr, 2016 1 commit
-
-
Rubén Dávila authored
This will help us to avoid posible merge conflicts when merging gitlab-ce to gitlab-ee
-
- 27 Mar, 2016 1 commit
-
-
Stan Hu authored
Closes #14659
-
- 25 Mar, 2016 2 commits
-
-
Stan Hu authored
Closes #14580
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 24 Mar, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 19 Mar, 2016 1 commit
-
-
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.
-
- 17 Mar, 2016 2 commits
-
-
Yorick Peterse authored
-
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
-
- 16 Mar, 2016 1 commit
-
-
Hiroyuki Sato authored
-
- 08 Mar, 2016 5 commits
-
-
Yorick Peterse authored
This ensures the right caches are flushed when adding a branch via the UI, instead of only flushing this one random cache.
-
Yorick Peterse authored
This ensures Repository#add_tag calls Repository#before_push_tag instead of just 1 random cache expiration method.
-
Yorick Peterse authored
-
Yorick Peterse authored
This ensures that Repository#rm_branch calls before_remove_branch/after_remove_branch instead of just 1 random cache expiration method.
-
Yorick Peterse authored
The methods used for this are Repository#tag_count and Repository#branch_count which cache their output in Redis as well as memoizing it in an instance variable. Both methods have a corresponding methods/hooks to flush the caches at the right time.
-
- 07 Mar, 2016 2 commits
-
-
tiagonbotelho authored
-
tiagonbotelho authored
-
- 02 Mar, 2016 1 commit
-
-
Rubén Dávila authored
-
- 25 Feb, 2016 1 commit
-
-
Yorick Peterse authored
-
- 20 Feb, 2016 1 commit
-
-
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
-
- 19 Feb, 2016 3 commits
-
-
Rubén Dávila authored
-
Rubén Dávila authored
-
Rubén Dávila authored
-
- 18 Feb, 2016 3 commits
-
-
Yorick Peterse authored
If path_with_namespace is nil Repository#raw_repository will also return nil. Apparently code out there creates a Repository instance without a namespace path. Right.
-
Yorick Peterse authored
-
Yorick Peterse authored
Setting the "autocrlf" Git option is an overkill since it's rarely actually needed. More importantly, it has quite the impact on performance (see gitlab-org/gitlab-ce#13457 for more information). By setting "autocrlf" when creating or updating files we guarantee the option is always set properly when we actually need it _without_ introducing overhead for requests that have nothing to do with this option. Fixes gitlab-org/gitlab-ce#13457
-
- 17 Feb, 2016 1 commit
-
-
Yorick Peterse authored
This ensures the caches for Repository#empty? and Repository#has_visible_content? are flushed after a repository has been imported or forked. Fixes gitlab-org/gitlab-ce#13505
-
- 09 Feb, 2016 1 commit
-
-
Yorick Peterse authored
Instead of flushing the behind/ahead counts for all branches upon every push we now only flush the cache of branches that actually need to have these statistics recalculated. There are now basically 2 scenarios and their effects: 1. A user pushes a commit to the default branch, this results in the cache being flushed for all branches. 2. A user pushes to a non default branch, this results in _only_ the cache for that branch being flushed. The existing code (Repository#expire_cache) remains backwards compatible with the previous behaviour, the new behaviour is only applied when a branch name is passed as an argument. This ensures that when for example a project is deleted the cache for all branches is flushed.
-
- 08 Feb, 2016 2 commits
-
-
Yorick Peterse authored
This caches the output of the following methods: * Repository#empty? * Repository#has_visible_content? * Repository#root_ref The cache for Repository#has_visible_content? is flushed whenever a commit is pushed to a new branch or an existing branch is removed. The cache for Repository#root_ref is only flushed whenever a user changes the default branch of a project. The cache for Repository#empty? is never explicitly flushed as there's no need for it.
-
Tony Chu authored
-
- 21 Jan, 2016 1 commit
-
-
Yorick Peterse authored
Gitlab::Git::Repository#branch_count is a tad faster than the previous setup. See gitlab-org/gitlab_git!62 for more information.
-
- 10 Dec, 2015 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 09 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 03 Dec, 2015 2 commits
-
-
Rubén Dávila authored
-
Rubén Dávila authored
-
- 02 Nov, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-