- 04 1月, 2018 1 次提交
-
-
由 Alejandro Rodríguez 提交于
-
- 28 12月, 2017 4 次提交
-
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
-
- 23 12月, 2017 2 次提交
-
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
-
- 22 12月, 2017 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 21 12月, 2017 1 次提交
-
-
由 Kim Carlbäcker 提交于
This reverts merge request !15712
-
- 15 12月, 2017 1 次提交
-
-
由 Nick Thomas 提交于
By importing this Ruby code into gitlab-rails (and gitaly-ruby), we avoid 200ms of startup time for each gitlab_projects subprocess we are eliminating. By not having a gitlab_projects subprocess between gitlab-rails / sidekiq and any git subprocesses (e.g. for fork_project, fetch_remote, etc, calls), we can also manage these git processes more cleanly, and avoid sending SIGKILL to them
-
- 14 12月, 2017 1 次提交
-
-
由 Ahmad Sherif 提交于
Closes gitaly#808
-
- 12 12月, 2017 1 次提交
-
-
由 Kim "BKC" Carlbäcker 提交于
-
- 08 12月, 2017 1 次提交
-
-
由 Kim Carlbäcker 提交于
-
- 07 12月, 2017 3 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
This also allows us to simplify the naming since we can make some fetching methods private.
-
- 05 12月, 2017 3 次提交
-
-
由 Ahmad Sherif 提交于
Closes gitaly#780
-
由 Alejandro Rodríguez 提交于
-
由 Ahmad Sherif 提交于
Closes gitaly#737
-
- 04 12月, 2017 1 次提交
-
-
由 Kim "BKC" Carlbäcker 提交于
-
- 01 12月, 2017 1 次提交
-
-
由 Stan Hu 提交于
This was failing regularly with an Error 500 when the API branches endpoint was used. Closes #40615
-
- 30 11月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 29 11月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
If a merge request was created with a branch name that also matched a tag name, we'd generate a comparison to or from the tag respectively, rather than the branch. Merging would still use the branch, of course. To avoid this, ensure that when we get the branch heads, we prepend the reference prefix for branches, which will ensure that we generate the correct comparison.
-
- 23 11月, 2017 2 次提交
-
-
由 Douwe Maan 提交于
-
由 Lin Jen-Shin 提交于
-
- 22 11月, 2017 1 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
-
- 21 11月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
After installing a new gem, batch-loader, a construct can be used to queue data to be fetched in bulk. The gem was also introduced in both gitlab-org/gitlab-ce!14680 and gitlab-org/gitlab-ce!14846, but those mrs are not merged yet. For the generation of diffs, both the old blob and the new blob need to be loaded. This for every file in the diff, too. Now we collect all these so we do 1 fetch. Three `.allow_n_plus_1_calls` have been removed, which I expect to be valid, but this needs to be confirmed by a full CI run. Possibly closes: - https://gitlab.com/gitlab-org/gitlab-ce/issues/37445 - https://gitlab.com/gitlab-org/gitlab-ce/issues/37599 - https://gitlab.com/gitlab-org/gitlab-ce/issues/37431
-
- 18 11月, 2017 2 次提交
-
-
由 Alejandro Rodríguez 提交于
-
由 Sean McGivern 提交于
Conflicts used to take a `Repository` and pass that to `Gitlab::Highlight.highlight`, which would call `#gitattribute` on the repository. Now they use a `Gitlab::Git::Repository`, which didn't have that method defined - but defining it on `Gitlab::Git::Repository` does make it available on `Repository` through `method_missing`, so we can do that and both cases will work.
-
- 17 11月, 2017 1 次提交
-
-
由 Jacopo 提交于
Adds a rubocop rule (with autocorrect) to ensure line break after guard clauses.
-
- 10 11月, 2017 1 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
-
- 09 11月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Moving more git operations to be executed by Gitaly, now the check if a repository exists is an opt out endpoint. Can be disabled, for the time being, by performing in the rails console: > Feature.get('gitaly_repository_exists').disable => true Part of gitlab-org/gitaly#314
-
- 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.
-
- 04 11月, 2017 1 次提交
-
-
由 Alejandro Rodríguez 提交于
-
- 03 11月, 2017 1 次提交
-
-
由 micael.bergeron 提交于
also, I refactored the MergeRequest#fetch_ref method to express the side-effect that this method has. MergeRequest#fetch_ref -> MergeRequest#fetch_ref! Repository#fetch_source_branch -> Repository#fetch_source_branch!
-
- 02 11月, 2017 1 次提交
-
-
由 James Edwards-Jones 提交于
Gitlab::Git::Blob.batch_lfs_metadata can be used to check for LFS pointers. It uses a lazy enumorator and filters by blob size
-
- 01 11月, 2017 1 次提交
-
-
由 Alejandro Rodríguez 提交于
-
- 27 10月, 2017 1 次提交
-
-
由 Lin Jen-Shin (godfat) 提交于
-
- 26 10月, 2017 1 次提交
-
-
由 Andrew Newdigate 提交于
-
- 25 10月, 2017 1 次提交
-
-
由 Alejandro Rodríguez 提交于
We also delete some unused code related to the aforementioned feature.
-