summaryrefslogtreecommitdiff
path: root/app/services/projects/transfer_service.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@14-6-stable-eev14.6.0-rc42GitLab Bot2021-12-201-6/+8
|
* Add latest changes from gitlab-org/gitlab@14-4-stable-eev14.4.0-rc42GitLab Bot2021-10-201-23/+22
|
* Add latest changes from gitlab-org/gitlab@14-3-stable-eev14.3.0-rc42GitLab Bot2021-09-201-7/+16
|
* Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42GitLab Bot2021-08-191-2/+8
|
* Add latest changes from gitlab-org/gitlab@14-1-stable-eev14.1.0-rc42GitLab Bot2021-07-201-1/+13
|
* Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42GitLab Bot2021-05-191-7/+7
|
* Add latest changes from gitlab-org/gitlab@13-8-stable-eev13.8.0-rc42Robert Speicher2021-01-201-2/+7
|
* Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42GitLab Bot2020-12-171-2/+9
|
* Add latest changes from gitlab-org/gitlab@13-6-stable-eeGitLab Bot2020-11-231-5/+11
|
* Add latest changes from gitlab-org/security/gitlab@13-5-stable-eeGitLab Bot2020-10-301-5/+7
|
* Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42GitLab Bot2020-10-211-0/+4
|
* Add latest changes from gitlab-org/gitlab@13-4-stable-eeGitLab Bot2020-09-191-3/+9
|
* Add latest changes from gitlab-org/gitlab@13-3-stable-eeGitLab Bot2020-08-201-0/+8
|
* Add latest changes from gitlab-org/gitlab@13-0-stable-eeGitLab Bot2020-05-201-3/+21
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-01-291-2/+4
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-311-0/+2
|
* Require maintainer permission to transfer projectsmanojmj2019-10-091-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-09-131-0/+2
|
* Add service to transfer group milestonesEugenia Grieff2019-09-041-0/+3
| | | | | | | | | | | - Add new service that transfers milestones from a group to a project - Include new service in Projects transfer service - Include FromUnion module in Milestone model to use in transfer service - Add specs for new milestones service - Add specs for transferring milestones in project transfer service
* Stop configuring group clusters on creation60379-remove-ci-preparing-state-feature-flagTiger2019-05-161-5/+0
| | | | | | | | | | | Immediate configuration is not ideal for group and instance level clusters as projects that may never be deployed would still have Kubernetes namespaces and service accounts created for them. As of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25586 we now create only the resources that are required for the project being deployed, at the time of deployment.
* Merge branch 'forbid-the-usage-of-reload' into 'master'Lin Jen-Shin2019-04-151-2/+2
|\ | | | | | | | | | | | | Forbid the usage of reload Closes #60218 See merge request gitlab-org/gitlab-ce!27125
| * Forbid the use of `#reload` and prefer `#reset`forbid-the-usage-of-reloadKamil TrzciƄski2019-04-151-2/+2
| | | | | | | | | | | | | | The `#reload` makes to load all objects into memory, and the main purpose of `#reload` is to drop the association cache. The `#reset` seems to solve exactly that case.
* | Externalize strings detected by rubocop-i18nMartin Wortschack2019-04-151-5/+5
|/ | | | | | - Externalize strings in milestones_helper - Externalize strings in app/services - Update PO file
* Update storage location after a project has been transferedDouglas Barbosa Alexandre2018-12-211-3/+4
|
* Create k8s namespace for project in group clustersThong Kuah2018-12-051-0/+5
| | | | | | | | | | | | | | | | | | | | AFAIK the only relevant place is Projects::CreateService, this gets called when user creates a new project, forks a new project and does those things via the api. Also create k8s namespace for new group hierarchy when transferring project between groups Uses new Refresh service to create k8s namespaces - Ensure we use Cluster#cluster_project If a project has multiple clusters (EE), using Project#cluster_project is not guaranteed to return the cluster_project for this cluster. So switch to using Cluster#cluster_project - at this stage a cluster can only have 1 cluster_project. Also, remove rescue so that sidekiq can retry
* Disable existing offenses for the CodeReuse copsYorick Peterse2018-09-111-0/+2
| | | | | This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
* fix path bug and update specsJames Lopez2018-08-301-1/+1
|
* Fix transfer project redirect loopJames Lopez2018-08-291-2/+3
|
* Remove code for dynamically generating routesstop-dynamic-routable-creationYorick Peterse2018-07-251-1/+0
| | | | | | This adds a database migration that creates routes for any projects and namespaces that don't already have one. We also remove the runtime code for dynamically creating routes, as this is no longer necessary.
* Enable more frozen string in app/services/**/*.rbrepo-forks/gitlab-ce-frozen-string-enable-apps-services-inner-moregfyoung2018-07-171-0/+2
| | | | Partially addresses #47424.
* Gitlab::Shell works on shard name, not pathZeger-Jan van de Weg2018-04-251-1/+1
| | | | | | | | | | | 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
* Cache personal projects count.Andreas Brandl2018-04-061-0/+2
| | | | Closes #37462.
* Fix Projects::TransferService#write_repository_config methodDouglas Barbosa Alexandre2018-01-031-1/+1
|
* Refactoring Project#write_repository_configDouglas Barbosa Alexandre2018-01-031-4/+1
|
* Update project full path in .git/config when transfering a projectDouglas Barbosa Alexandre2018-01-031-0/+10
|
* Fix project transfer with hashed-storage attachmentsNick Thomas2017-11-171-1/+11
|
* Fix hashed storage with project transfers to another namespacesh-port-hashed-storage-transfer-fixStan Hu2017-11-161-9/+17
| | | | | | | | With hashed storage enabled, we would fail to transfer a project to another namespace because the provided paths were wrong. Instead, we should not attempt to move paths at all. Closes gitlab-org/gitlab-ee#4056
* Added some extra TODOs for the Legacy Storage refactorGabriel Mazetto2017-08-011-0/+2
|
* Rename many path_with_namespace -> full_pathGabriel Mazetto2017-08-011-1/+1
|
* Expires full_path cache after repository is transferredDouglas Barbosa Alexandre2017-06-291-0/+1
|
* Rollback project folder move after error in Projects::TransferService30213-project-transfer-move-rollbackJames Edwards-Jones2017-06-201-40/+74
|
* Refactored transfer_service #execute actionprevent-project-transferJose Ivan Vargas2017-05-221-10/+6
|
* minor adjustments to the specsJose Ivan Vargas2017-05-221-1/+1
|
* Renamed some messages and refactored the project_edit class to a functionJose Ivan Vargas2017-05-221-2/+2
|
* Prevent project transfer if a new group is not selectedJose Ivan Vargas2017-05-221-1/+6
|
* Enable and autocorrect the CustomErrorClass copSean McGivern2017-03-011-1/+1
|
* Use Namespace#full_path instead of Namespace#pathDmitriy Zaporozhets2017-02-141-3/+3
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Refresh authorizations when transferring projectsrefresh-permissions-when-moving-projectsYorick Peterse2017-02-071-2/+15
| | | | | | | | This ensures that project authorizations are refreshed when moving a project from one namespace to another. When doing so the permissions for all users of both the old and new namespaces are refreshed. See #26194 for more information.
* Rename pages namespace or project path when changedKamil Trzcinski2017-01-311-0/+3
| | | | - Move UploadsTransfer to ProjectTransfer and inherit from this to UploadsTransfer and PagesTransfer
* Remove event caching codeYorick Peterse2016-11-231-3/+0
| | | | | | | | | | | | | | | | | | | Flushing the events cache worked by updating a recent number of rows in the "events" table. This has the result that on PostgreSQL a lot of dead tuples are produced on a regular basis. This in turn means that PostgreSQL will spend considerable amounts of time vacuuming this table. This in turn can lead to an increase of database load. For GitLab.com we measured the impact of not using events caching and found no measurable increase in response timings. Meanwhile not flushing the events cache lead to the "events" table having no more dead tuples as now rows are only inserted into this table. As a result of this we are hereby removing events caching as it does not appear to help and only increases database load. For more information see the following comment: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037