- 08 11月, 2017 40 次提交
-
-
由 Douwe Maan 提交于
Rewrite the GitHub importer to perform work in parallel and greatly improve performance Closes #33135, #38621, and #39361 See merge request gitlab-org/gitlab-ce!14731
-
由 Tim Zallmann 提交于
Added missing strings to prepare the tags page for internationalization See merge request gitlab-org/gitlab-ce!15256
-
由 Rémy Coutable 提交于
Add Internal QA specs to the pipeline See merge request gitlab-org/gitlab-ce!15240
-
由 Grzegorz Bizon 提交于
-
由 Douwe Maan 提交于
Change Sign Out route from a DELETE to a GET Closes #39708 See merge request gitlab-org/gitlab-ce!15231
-
由 Tim Zallmann 提交于
Cleanup tests See merge request gitlab-org/gitlab-ce!15261
-
由 Douwe Maan 提交于
When deleting merged branches, ignore protected tags Closes #39732 See merge request gitlab-org/gitlab-ce!15252
-
由 Douwe Maan 提交于
Free some reserved group routes See merge request gitlab-org/gitlab-ce!15052
-
由 Stan Hu 提交于
Make BackgroundTransaction#labels public See merge request gitlab-org/gitlab-ce!15257
-
由 Mike Greiling 提交于
fix karma config file See merge request gitlab-org/gitlab-ce!15263
-
由 Marcia Ramos 提交于
Modals in UX guide See merge request gitlab-org/gitlab-ce!14886
-
由 Stan Hu 提交于
Adds typescript support in webpack. With Mike G. See merge request gitlab-org/gitlab-ce!15264
-
由 Jacob Schatz 提交于
-
由 Jacob Schatz 提交于
-
由 Jacob Schatz 提交于
-
由 Yorick Peterse 提交于
-
由 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.
-
由 Marcia Ramos 提交于
Add note on registry restrictions on GitLab.com See merge request gitlab-org/gitlab-ce!15174
-
由 Chenjerai Katanda 提交于
-
由 Annabel Dunstone Gray 提交于
Project with many branches can lock server running "git branch --contains XXX" Closes #37824 See merge request gitlab-org/gitlab-ce!14812
-
由 Jose Ivan Vargas 提交于
-
由 Yorick Peterse 提交于
The GitHub importer (and probably other parts of our code) ends up calling Feature.persisted? many times (via Gitaly). By storing this data in RequestStore we can save ourselves _a lot_ of database queries. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/39361
-
由 Yorick Peterse 提交于
This adds the keyword argument "return_ids" to Gitlab::Database.bulk_insert. When set to `true` (and PostgreSQL is used) this method will return an Array of the IDs of the inserted rows, otherwise it will return an empty Array.
-
由 Yorick Peterse 提交于
By using SQL::Union we can return a proper ActiveRecord::Relation, making it possible to select the columns we're interested in (instead of all of them).
-
由 Annabel Dunstone Gray 提交于
-
由 Filipa Lacerda 提交于
-
由 tauriedavis 提交于
-
由 tauriedavis 提交于
-
由 Kamil Trzciński 提交于
Add Ingress to cluster applications section See merge request gitlab-org/gitlab-ce!15185
-
由 Filipa Lacerda 提交于
-
由 Kamil Trzciński 提交于
Upgrade vendored templates for 10.2 See merge request gitlab-org/gitlab-ce!15259
-
由 Nick Thomas 提交于
Improve GitLab Import rake task to work with Hashed Storage and Subgroups Closes #36509 See merge request gitlab-org/gitlab-ce!15157
-
由 James Lopez 提交于
-
由 Alessio Caiazza 提交于
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
-
由 Bob Van Landuyt 提交于
-