- 08 12月, 2018 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
When a project is forked, the new repository used to be a deep copy of everything stored on disk by leveraging `git clone`. This works well, and makes isolation between repository easy. However, the clone is at the start 100% the same as the origin repository. And in the case of the objects in the object directory, this is almost always going to be a lot of duplication. Object Pools are a way to create a third repository that essentially only exists for its 'objects' subdirectory. This third repository's object directory will be set as alternate location for objects. This means that in the case an object is missing in the local repository, git will look in another location. This other location is the object pool repository. When Git performs garbage collection, it's smart enough to check the alternate location. When objects are duplicated, it will allow git to throw one copy away. This copy is on the local repository, where to pool remains as is. These pools have an origin location, which for now will always be a repository that itself is not a fork. When the root of a fork network is forked by a user, the fork still clones the full repository. Async, the pool repository will be created. Either one of these processes can be done earlier than the other. To handle this race condition, the Join ObjectPool operation is idempotent. Given its idempotent, we can schedule it twice, with the same effect. To accommodate the holding of state two migrations have been added. 1. Added a state column to the pool_repositories column. This column is managed by the state machine, allowing for hooks on transitions. 2. pool_repositories now has a source_project_id. This column in convenient to have for multiple reasons: it has a unique index allowing the database to handle race conditions when creating a new record. Also, it's nice to know who the host is. As that's a short link to the fork networks root. Object pools are only available for public project, which use hashed storage and when forking from the root of the fork network. (That is, the project being forked from itself isn't a fork) In this commit message I use both ObjectPool and Pool repositories, which are alike, but different from each other. ObjectPool refers to whatever is on the disk stored and managed by Gitaly. PoolRepository is the record in the database.
-
- 19 10月, 2018 1 次提交
-
-
由 Bob Van Landuyt 提交于
This removes the `ForkedProjectLink` model that has been replaced by the `ForkNetworkMember` and `ForkNetwork` combination. All existing relations have been adjusted to use these new models. The `forked_project_link` table has been dropped. The "Forks" count on the admin dashboard has been updated to count all `ForkNetworkMember` rows and deduct the number of `ForkNetwork` rows. This is because now the "root-project" of a fork network also has a `ForkNetworkMember` row. This count could become inaccurate when the root of a fork network is deleted.
-
- 20 8月, 2018 1 次提交
-
-
由 Toon Claes 提交于
A forked project stores its LFS objects in the `forked_from_project`. So the LFS objects become inaccessible, and therefore delete them from the database so they'll get cleaned up. To be refactored when implementing https://gitlab.com/gitlab-org/gitlab-ce/issues/39769
-
- 09 7月, 2018 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 07 6月, 2018 1 次提交
-
-
由 Robert Speicher 提交于
-
- 25 4月, 2018 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Direct disk access is done through Gitaly now, so the legacy path was deprecated. This path was used in Gitlab::Shell however. This required the refactoring in this commit. Added is the removal of direct path access on the project model, as that lookup wasn't needed anymore is most cases. Closes https://gitlab.com/gitlab-org/gitaly/issues/1111
-
- 22 3月, 2018 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 14 3月, 2018 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Prior to this change, this method was called add_namespace, which broke the CRUD convention and made it harder to grep for what I was looking for. Given the change was a find and replace kind of fix, this was changed without opening an issue and on another feature branch. If more dynamic calls are made to add_namespace, these could've been missed which might lead to incorrect bahaviour. However, going through the commit log it seems thats not the case.
-
- 29 12月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
In this case the project will get the minimum between both visibilities. If that visibility is restricted, then a lower level will be picked.
-
- 07 12月, 2017 1 次提交
-
-
由 Francisco Javier López 提交于
-
- 07 10月, 2017 2 次提交
-
-
由 Bob Van Landuyt 提交于
The helper creates a fork of a project with all provided attributes, but skipping the creation of the repository on disk.
-
由 Bob Van Landuyt 提交于
When no fork network exists for the source projects, we create a new one with the correct source
-
- 30 9月, 2017 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 26 8月, 2017 1 次提交
-
-
由 Gabriel Mazetto 提交于
There are some redundancies in the validation steps, and that is to preserve current error messages behavior Also few specs have to be changed in order to fix madness in validation logic.
-
- 15 8月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
The number of forks of a project doesn't change very frequently and running a COUNT(*) every time this information is requested can be quite expensive. We also end up running such a COUNT(*) query at least twice on the homepage of a project. By caching this data and refreshing it when necessary we can reduce project homepage loading times by around 60 milliseconds (based on the timings of https://gitlab.com/gitlab-org/gitlab-ce).
-
- 27 7月, 2017 1 次提交
-
-
由 Rémy Coutable 提交于
Remove superfluous lib: true, type: redis, service: true, models: true, services: true, no_db: true, api: true Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 06 6月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 28 3月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 25 3月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 03 1月, 2017 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 27 9月, 2016 1 次提交
-
-
由 Nick Thomas 提交于
Projects::ForkService delegates to this service almost entirely, but needed one small change so it would propagate create errors correctly. CreateService#execute needs significant refactoring; it is now right at the complexity limit set by Rubocop. I avoided doing so in this commit to keep the diff as small as possible. Several tests depend on the insecure behaviour of ForkService, so fi them up at the same time.
-
- 09 8月, 2016 1 次提交
-
-
由 tiagonbotelho 提交于
-
- 03 6月, 2016 2 次提交
-
-
由 James Lopez 提交于
This reverts commit 3e991230.
-
由 James Lopez 提交于
# Conflicts: # app/models/project.rb
-
- 25 5月, 2016 1 次提交
-
-
由 Felipe Artur 提交于
-
- 09 12月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 18 11月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 13 11月, 2015 1 次提交
-
-
由 Kamil Trzcinski 提交于
- Enable CI by default for all new projects
-
- 02 10月, 2015 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 19 9月, 2015 1 次提交
-
-
由 Valery Sizov 提交于
-
- 11 9月, 2015 1 次提交
-
-
由 Stan Hu 提交于
Use import_status to track async import status and give feedback to the user Closes #2388 Closes #2400
-
- 30 7月, 2015 1 次提交
-
-
由 Stan Hu 提交于
Add gitlab-shell to error message to give user a clue that something may be wrong there. Ran into this in #2082. User was told that repositories were created when they were not due to hooks symlink being wrong.
-
- 23 6月, 2015 1 次提交
-
-
由 Stan Hu 提交于
-
- 25 4月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 07 4月, 2015 1 次提交
-
-
由 Valery Sizov 提交于
-
- 13 2月, 2015 1 次提交
-
-
由 Jeroen van Baarsen 提交于
Signed-off-by: NJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 03 10月, 2014 1 次提交
-
-
由 Bernhard Kaindl 提交于
Remove overload of BaseService.initialize, so initialize gains params, which is used to pass the namespace (like e.g. in TransferService). The namespace is checked for permission to create projects in it.
-
- 25 8月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 17 1月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-