- 04 1月, 2018 2 次提交
-
-
-
We'd need to keep track of project full path otherwise directory tree created with hashed storage enabled cannot be usefully imported using the import rake task.
-
- 03 1月, 2018 2 次提交
-
-
由 James Lopez 提交于
-
由 James Lopez 提交于
-
- 23 12月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 22 12月, 2017 1 次提交
-
-
由 blackst0ne 提交于
-
- 21 12月, 2017 1 次提交
-
-
由 Kim Carlbäcker 提交于
This reverts merge request !15712
-
- 13 12月, 2017 1 次提交
-
-
由 Greg Stark 提交于
-
- 12 12月, 2017 1 次提交
-
-
由 Kim "BKC" Carlbäcker 提交于
-
- 07 12月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 05 12月, 2017 1 次提交
-
-
由 Jan Provaznik 提交于
* new merge request can be created by sending an email to the specific email address (similar to creating issues by email) * for the first iteration, source branch must be specified in the mail subject, other merge request parameters can not be set yet * user should enable "Receive notifications about your own activity" in user settings to receive a notification about created merge request Part of #32878
-
- 04 12月, 2017 2 次提交
-
-
由 Matija Čupić 提交于
-
由 Nick Thomas 提交于
Note the dependency on gitlab-shell v5.10.0
-
- 02 12月, 2017 1 次提交
-
-
由 Francisco Lopez 提交于
Comments from code review applied. Also switched forked_from_project and ForkedProjectLinks to ForkNetworkMember
-
- 01 12月, 2017 1 次提交
-
-
由 Christiaan Van den Poel 提交于
-
- 28 11月, 2017 6 次提交
-
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
-
- 27 11月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 24 11月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 23 11月, 2017 2 次提交
-
-
由 Gabriel Mazetto 提交于
-
由 Jarka Kadlecova 提交于
-
- 15 11月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 09 11月, 2017 1 次提交
-
-
由 James Edwards-Jones 提交于
-
- 08 11月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
Prior to this MR there were two GitHub related importers: * Github::Import: the main importer used for GitHub projects * Gitlab::GithubImport: importer that's somewhat confusingly used for importing Gitea projects (apparently they have a compatible API) This MR renames the Gitea importer to Gitlab::LegacyGithubImport and introduces a new GitHub importer in the Gitlab::GithubImport namespace. This new GitHub importer uses Sidekiq for importing multiple resources in parallel, though it also has the ability to import data sequentially should this be necessary. The new code is spread across the following directories: * lib/gitlab/github_import: this directory contains most of the importer code such as the classes used for importing resources. * app/workers/gitlab/github_import: this directory contains the Sidekiq workers, most of which simply use the code from the directory above. * app/workers/concerns/gitlab/github_import: this directory provides a few modules that are included in every GitHub importer worker. == Stages The import work is divided into separate stages, with each stage importing a specific set of data. Stages will schedule the work that needs to be performed, followed by scheduling a job for the "AdvanceStageWorker" worker. This worker will periodically check if all work is completed and schedule the next stage if this is the case. If work is not yet completed this worker will reschedule itself. Using this approach we don't have to block threads by calling `sleep()`, as doing so for large projects could block the thread from doing any work for many hours. == Retrying Work Workers will reschedule themselves whenever necessary. For example, hitting the GitHub API's rate limit will result in jobs rescheduling themselves. These jobs are not processed until the rate limit has been reset. == User Lookups Part of the importing process involves looking up user details in the GitHub API so we can map them to GitLab users. The old importer used an in-memory cache, but this obviously doesn't work when the work is spread across different threads. The new importer uses a Redis cache and makes sure we only perform API/database calls if absolutely necessary. Frequently used keys are refreshed, and lookup misses are also cached; removing the need for performing API/database calls if we know we don't have the data we're looking for. == Performance & Models The new importer in various places uses raw INSERT statements (as generated by `Gitlab::Database.bulk_insert`) instead of using Rails models. This allows us to bypass any validations and callbacks, drastically reducing the number of SQL queries and Gitaly RPC calls necessary to import projects. To ensure the code produces valid data the corresponding tests check if the produced rows are valid according to the model validation rules.
-
- 06 11月, 2017 2 次提交
-
-
由 Douwe Maan 提交于
-
由 Markus Koller 提交于
-
- 04 11月, 2017 2 次提交
-
-
由 Matija Čupić 提交于
-
由 Alejandro Rodríguez 提交于
-
- 03 11月, 2017 1 次提交
-
-
由 Bob Van Landuyt 提交于
-
- 02 11月, 2017 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 31 10月, 2017 3 次提交
-
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-
由 Jacopo 提交于
Pipeline hook data now includes the project_id
-
- 28 10月, 2017 1 次提交
-
-
由 Gabriel Mazetto 提交于
When project storage_version is `2` means attachments are using hashed storage.
-
- 27 10月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Now, when requesting a commit from the Repository model, the results are not cached. This means we're fetching the same commit by oid multiple times during the same request. To prevent us from doing this, we now cache results. Caching is done only based on object id (aka SHA). Given we cache on the Repository model, results are scoped to the associated project, eventhough the change of two repositories having the same oids for different commits is small.
-
- 23 10月, 2017 1 次提交
-
-
由 Shinya Maeda 提交于
-