Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2017-07-27Remove superfluous lib: true, type: redis, service: true, models: true, ↵Rémy Coutable
services: true, no_db: true, api: true Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-05-31Introduce source to pipeline entityKamil Trzcinski
2017-03-28Use `:empty_project` where possible in service specsRobert Speicher
2016-11-21Refactor cache refreshing/expiringYorick Peterse
This refactors repository caching so it's possible to selectively refresh certain caches, instead of just expiring and refreshing everything. To allow this the various methods that were cached (e.g. "tag_count" and "readme") use a similar pattern that makes expiring and refreshing their data much easier. In this new setup caches are refreshed as follows: 1. After a commit (but before running ProjectCacheWorker) we expire some basic caches such as the commit count and repository size. 2. ProjectCacheWorker will recalculate the commit count, repository size, then refresh a specific set of caches based on the list of files changed in a push payload. This requires a bunch of changes to the various methods that may be cached. For one, data should not be cached if a branch used or the entire repository does not exist. To prevent all these methods from handling this manually this is taken care of in Repository#cache_method_output. Some methods still manually check for the existence of a repository but this result is also cached. With selective flushing implemented ProjectCacheWorker no longer uses an exclusive lease for all of its work. Instead this worker only uses a lease to limit the number of times the repository size is updated as this is a fairly expensive operation.
2016-10-28Fix lightweight tags not processed correctly by GitTagPushServiceAlejandro Rodríguez
When we updated gitlab_git to 10.4.1, `tag.target` changed from pointing to the sha of the tag to the sha of the commit the tag points to. The problem is that only annotated tags have `object_sha`s, lightweight tags don't (it's nil), so (only) in their case we still need to use `tag.target`.
2016-06-30Expire branch/tag git data when needed.Paco Guzman
When pushing commits to existing branches we don’t need to flush branch git data (branch names / counts) When flushes the cache when pushing commits skip to flush branch and tag git data (names / counts) because those operations are managed explicitly in each case Repopulated expired cache as soon as possible
2016-04-19Refactor GitTagPushService and fig tags_push system event hookGabriel Mazetto
2016-03-10web hooks to webhooksashleys
2015-12-15Fixed Rubocop offensesGabriel Mazetto
2015-12-09Tag service specsDouwe Maan
2015-06-22Remove unnecessary whitespace between let and (Dmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2015-04-24Use project.commit convenience method.Douwe Maan
2015-03-21Extend push_tag event to include tag message and last commitKamil Trzcinski
2015-02-12Updated rspec to rspec 3.x syntaxJeroen van Baarsen
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
2014-03-06Renamed oldrev/newrev to before/afterJeroen van Baarsen
2014-03-06Added newrev and oldrev to the hook dataJeroen van Baarsen
2014-03-06Created a basic Git Tag Push serviceJeroen van Baarsen
This is the first version, and only has the most basic information about the tag that is created.