- 13 4月, 2016 1 次提交
-
-
由 Stan Hu 提交于
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
-
- 12 4月, 2016 2 次提交
-
-
由 Jeroen Bobbeldijk 提交于
-
由 Jeroen Bobbeldijk 提交于
-
- 11 4月, 2016 1 次提交
-
-
由 Jeroen Bobbeldijk 提交于
-
- 10 4月, 2016 1 次提交
-
-
由 Robert Speicher 提交于
Closes #14963.
-
- 07 4月, 2016 1 次提交
-
-
由 Stan Hu 提交于
Closes #14961
-
- 05 4月, 2016 1 次提交
-
-
GitHub Pull Requests importer handle with the repository while importing data, we need to make sure that the cached values are valid.
-
- 02 4月, 2016 2 次提交
-
-
由 Stan Hu 提交于
Closes #13957
-
由 Rubén Dávila 提交于
This will help us to avoid posible merge conflicts when merging gitlab-ce to gitlab-ee
-
- 27 3月, 2016 1 次提交
-
-
由 Stan Hu 提交于
Closes #14659
-
- 26 3月, 2016 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 25 3月, 2016 2 次提交
-
-
由 Stan Hu 提交于
Closes #14580
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 24 3月, 2016 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 20 3月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
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.
-
- 18 3月, 2016 3 次提交
-
-
由 Yorick Peterse 提交于
When calling Repository#build_cache we _don't_ want to build the diverging commit count cache as doing so can be _very_ slow for repositories with lots of branches. Because these caches are built whenever needed (= when actually viewing the list of branches in the web UI) we can safely remove this code from Repository#build_cache.
-
由 Yorick Peterse 提交于
This method is not used or tested anywhere.
-
由 Yorick Peterse 提交于
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
-
- 17 3月, 2016 1 次提交
-
-
由 Hiroyuki Sato 提交于
-
- 09 3月, 2016 4 次提交
-
-
由 Yorick Peterse 提交于
This ensures the right caches are flushed when adding a branch via the UI, instead of only flushing this one random cache.
-
由 Yorick Peterse 提交于
This ensures Repository#add_tag calls Repository#before_push_tag instead of just 1 random cache expiration method.
-
由 Yorick Peterse 提交于
This ensures that Repository#rm_branch calls before_remove_branch/after_remove_branch instead of just 1 random cache expiration method.
-
由 Yorick Peterse 提交于
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.
-
- 08 3月, 2016 3 次提交
-
-
由 tiagonbotelho 提交于
-
由 tiagonbotelho 提交于
-
由 tiagonbotelho 提交于
-
- 02 3月, 2016 2 次提交
-
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
- 25 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
This is only needed when calling the "expire_cache" method as the other expiration methods don't depend on Git data.
-
- 23 2月, 2016 2 次提交
-
-
由 Yorick Peterse 提交于
-
由 Yorick Peterse 提交于
This keeps all the cache expiration code in a single file/class instead of spreading it all across the codebase.
-
- 21 2月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
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
-
- 20 2月, 2016 7 次提交
-
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-
由 Rubén Dávila 提交于
-