An error occurred fetching the project authors.
- 07 Dec, 2017 5 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
Create has_environment_scope for centerlizing env_scope specific process. Pass environment_scope to deployment_platform method.
-
Shinya Maeda authored
-
- 06 Dec, 2017 1 commit
-
-
Matija Čupić authored
-
- 04 Dec, 2017 5 commits
-
-
Francisco Javier López authored
-
Tiago Botelho authored
-
Nick Thomas authored
Note the dependency on gitlab-shell v5.10.0
-
Nick Thomas authored
Note the dependency on gitlab-shell v5.10.0
-
Shinya Maeda authored
-
- 01 Dec, 2017 5 commits
-
-
Francisco Lopez authored
Comments from code review applied. Also switched forked_from_project and ForkedProjectLinks to ForkNetworkMember
-
Shinya Maeda authored
-
Shinya Maeda authored
commit 7277b3b3 Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 28 03:06:38 2017 +0900 Fix feature spec commit b4c4e1bd Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 28 02:01:41 2017 +0900 Fix integraetion tests commit 54c70a77 Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 28 01:26:14 2017 +0900 Fix static analysys commit f6d9dcf8 Author: Shinya Maeda <shinya@gitlab.com> Date: Mon Nov 27 23:55:25 2017 +0900 Fix unit tests commit c36d7842 Author: Shinya Maeda <shinya@gitlab.com> Date: Mon Nov 27 23:19:16 2017 +0900 Aling shared_exmaples to "same behavior between KubernetesService and Platform::Kubernetes" commit 53da3d97 Author: Shinya Maeda <shinya@gitlab.com> Date: Mon Nov 27 22:35:16 2017 +0900 Replce kubernetes_service and deployment_service to deployment_platform commit 1d7e3ef1 Author: Shinya Maeda <shinya@gitlab.com> Date: Mon Nov 27 21:48:54 2017 +0900 Duplicate spec for Platform::Kubernetes with kubernetes_project commit 5324383d Author: Shinya Maeda <shinya@gitlab.com> Date: Wed Nov 22 23:21:02 2017 +0900 Add test for checking interchangeability between KubernetesService and Clusters::Platform::Kubernetes commit 45f2d0af Author: Shinya Maeda <shinya@gitlab.com> Date: Wed Nov 22 18:31:07 2017 +0900 Add test suit for platform::kubernetes commit a8e2094c Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 23:29:33 2017 +0900 Remove logic which glues with KubernetesService, from Platforms::Kubernetes commit 3cf53cc6 Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 22:53:36 2017 +0900 Fix comments commit cff5eadd Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 22:52:05 2017 +0900 Add deployment platform selector commit cff4a50e Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 22:33:25 2017 +0900 Fix tests for Clusters::Platforms::Kubernetes commit 0d95ce51 Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 22:03:07 2017 +0900 Check diff between KubernetesService and Platforms::Kubernetes. Synchronize again. commit 8a55d2c5 Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 21:09:55 2017 +0900 Revert KubernetesService logic in Platforms::Kubernetes
-
Shinya Maeda authored
commit 647e01a62d92a51ff7002a49f4eb5df3cd09c657 Author: Shinya Maeda <shinya@gitlab.com> Date: Wed Nov 22 23:21:02 2017 +0900 Add test for checking interchangeability between KubernetesService and Clusters::Platform::Kubernetes commit f5d05a7c0e2351c46eda3bfec475d671d16ee2b8 Author: Shinya Maeda <shinya@gitlab.com> Date: Wed Nov 22 18:31:07 2017 +0900 Add test suit for platform::kubernetes commit 998eb71017179af11ab5f03861207f5df0fd834c Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 23:29:33 2017 +0900 Remove logic which glues with KubernetesService, from Platforms::Kubernetes commit 29f987b3ec747c85087ad0dc523d897f6802ed6f Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 22:53:36 2017 +0900 Fix comments commit 01b6a7a9fd476fc408e9f3a713d6c7dd6cb8690e Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 22:52:05 2017 +0900 Add deployment platform selector commit f70ebff43fb21ad49941cf5653024be056b2a664 Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 22:33:25 2017 +0900 Fix tests for Clusters::Platforms::Kubernetes commit b4a661e57bc9d14850ea059a6d6a755673925da2 Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 22:03:07 2017 +0900 Check diff between KubernetesService and Platforms::Kubernetes. Synchronize again. commit 09297530077841256043fb522d3cdd60e2baeee0 Author: Shinya Maeda <shinya@gitlab.com> Date: Tue Nov 21 21:09:55 2017 +0900 Revert KubernetesService logic in Platforms::Kubernetes
-
Christiaan Van den Poel authored
-
- 28 Nov, 2017 7 commits
-
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Shinya Maeda authored
-
Gabriel Mazetto authored
-
- 27 Nov, 2017 1 commit
-
-
Douwe Maan authored
-
- 24 Nov, 2017 1 commit
-
-
Douwe Maan authored
-
- 23 Nov, 2017 2 commits
-
-
Gabriel Mazetto authored
-
Jarka Kadlecova authored
-
- 21 Nov, 2017 3 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
Change feature flag to shared_runner_minutes_on_subnamespace and update code to verify if shared_runner_minutes can be used
-
Kamil Trzcinski authored
-
- 15 Nov, 2017 2 commits
-
-
Mayra Cabrera authored
- Adds rescue clase to import_url method - Ensure RemoteMirror model also validates the url Closes #833
-
Douwe Maan authored
-
- 09 Nov, 2017 1 commit
-
-
James Edwards-Jones authored
-
- 08 Nov, 2017 1 commit
-
-
Yorick Peterse authored
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.
-
- 07 Nov, 2017 1 commit
-
-
Yorick Peterse authored
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 Nov, 2017 2 commits
-
-
Douwe Maan authored
-
Markus Koller authored
-
- 04 Nov, 2017 1 commit
-
-
Matija Čupić authored
-
- 03 Nov, 2017 2 commits
-
-
Alejandro Rodríguez authored
-
Alejandro Rodríguez authored
-