Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
Migration
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
KIT
GitLab
Migration
Commits
ca1da3c2
Commit
ca1da3c2
authored
1 year ago
by
Donghee Kang
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
d95492f5
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+8
-8
8 additions, 8 deletions
README.md
with
8 additions
and
8 deletions
README.md
+
8
−
8
View file @
ca1da3c2
...
...
@@ -19,18 +19,18 @@ Usage: migration_group_export_import.py
1.
add your personal access token (PAT) getting from the source and target gitlab both.
2.
In source(pilot) gitlab, find out the group id, which will be migrated. You should access it from the web browser.
3.
In target(new) gitlab, define the
`path`` of your subgroup. (not group name)
- `
group_namespace_in_target = 'kit/institute/m
igration
'
`
- `
group_namespace_in_target = 'kit/institute/m
y_group
'
`
In the target gitlab, a group structure "KIT / Institute" has to be eanbled in advance.
If the last subgroup "m
igration
" is not existing, "m
igration
" will be created first and projects wil be transferred on this subgroup.
If the last subgroup "m
igration
" is already existing, then all projects will be transferred to existing subgroup, directly.
If the last subgroup "m
y_group
" is not existing, "m
y_group
" will be created first and projects wil be transferred on this subgroup.
If the last subgroup "m
y_group
" is already existing, then all projects will be transferred to existing subgroup, directly.
> $ python3 migration_group_export_import.py
Procedure:
1. Exporting projects in a group `
my_group
` from the source gitlab. You needs to know `
group_id
` for this group `
my_group
`
2. Download exported files to the local directory `
"{PWD}/exported_files"
`
3. Importing the exported files to the target gitlab on `
"kit/institute/m
igration
"
`
3. Importing the exported files to the target gitlab on `
"kit/institute/m
y_group
"
`
...
...
@@ -39,17 +39,17 @@ Usage: migration_group_import_only.py
1. add your personal access token (PAT) getting from the target gitlab only.
2. define a set of exported files, that are located under the local directory `
"{PWD}/exported_files"
`
3. In target(new) gitlab, define the path of your subgroup
- `
group_namespace_in_target = 'kit/institute/m
igration
'
`
- `
group_namespace_in_target = 'kit/institute/m
y_group
'
`
In the target gitlab, a group structure "KIT / Institute" has to be eanbled in advance.
If the last subgroup "m
igration
" is not existing, "m
igration
" will be created first and projects wil be transferred on this subgroup.
If the last subgroup "m
igration
" is already existing, then all projects will be transferred to existing subgroup, directly.
If the last subgroup "m
y_group
" is not existing, "m
y_group
" will be created first and projects wil be transferred on this subgroup.
If the last subgroup "m
y_group
" is already existing, then all projects will be transferred to existing subgroup, directly.
> $ python3 migration_group_improt_only.py
Procedure:
1. No exporting and download is requried. In the directory`
"{PWD}/exported_files"
` all `
*
_exported.tar.gz"
` files(=projects) are enabled to use.
2. Importing the exported files to the target gitlab on the subgroup `
"kit/institute/m
igration
"
`
2. Importing the exported files to the target gitlab on the subgroup `
"kit/institute/m
y_group
"
`
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment