Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
f7ae84f9
Commit
f7ae84f9
authored
Nov 02, 2018
by
Michael Kozono
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document limitation of bare repository import
parent
001cb5aa
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
46 additions
and
1 deletion
+46
-1
doc/raketasks/import.md
doc/raketasks/import.md
+46
-1
No files found.
doc/raketasks/import.md
View file @
f7ae84f9
...
@@ -6,6 +6,7 @@
...
@@ -6,6 +6,7 @@
-
The groups will be created as needed, including subgroups
-
The groups will be created as needed, including subgroups
-
The owner of the group will be the first admin
-
The owner of the group will be the first admin
-
Existing projects will be skipped
-
Existing projects will be skipped
-
Projects in hashed storage may be skipped (see
[
Importing bare repositories from hashed storage
](
#importing-bare-repositories-from-hashed-storage
)
)
-
The existing Git repos will be moved from disk (removed from the original path)
-
The existing Git repos will be moved from disk (removed from the original path)
## How to use
## How to use
...
@@ -26,7 +27,6 @@ sudo -u git mkdir /var/opt/gitlab/git-data/repository-import-<date>/new_group
...
@@ -26,7 +27,6 @@ sudo -u git mkdir /var/opt/gitlab/git-data/repository-import-<date>/new_group
If we copy the repos to
`/var/opt/gitlab/git-data/repository-import-<date>`
, and repo A needs to be under the groups G1 and G2, it will
If we copy the repos to
`/var/opt/gitlab/git-data/repository-import-<date>`
, and repo A needs to be under the groups G1 and G2, it will
have to be created under those folders:
`/var/opt/gitlab/git-data/repository-import-<date>/G1/G2/A.git`
.
have to be created under those folders:
`/var/opt/gitlab/git-data/repository-import-<date>/G1/G2/A.git`
.
```
```
sudo cp -r /old/git/foo.git /var/opt/gitlab/git-data/repository-import-<date>/new_group/
sudo cp -r /old/git/foo.git /var/opt/gitlab/git-data/repository-import-<date>/new_group/
...
@@ -70,3 +70,48 @@ Processing /var/opt/gitlab/git-data/repository-import-1/group/xyz.git
...
@@ -70,3 +70,48 @@ Processing /var/opt/gitlab/git-data/repository-import-1/group/xyz.git
* Skipping repo /var/opt/gitlab/git-data/repository-import-1/@shared/a/b/abcd.git
* Skipping repo /var/opt/gitlab/git-data/repository-import-1/@shared/a/b/abcd.git
[...]
[...]
```
```
## Importing bare repositories from hashed storage
### Background
Projects in legacy storage have a directory structure that mirrors their full
project path in GitLab, including their namespace structure. This information is
leveraged by the bare repository importer to import projects into their proper
locations. Each project and its parent namespaces are meaningfully named.
However, the directory structure of projects in hashed storage do not contain
this information. This is beneficial for a variety of reasons, especially
improved performance and data integrity. See
[
Repository Storage Types
](
../administration/repository_storage_types.md
)
for
more details.
### Which repositories are importable?
#### v10.3 or earlier
Importing bare repositories from hashed storage is unsupported.
#### v10.4 and later
In order to support this, we began storing the full GitLab project path with
each repository. However, existing repositories were not migrated to include
this path.
The following are importable as bare repositories:
-
Created in hashed storage in v10.4+
-
Migrated to hashed storage in v10.4+
-
Renamed in v10.4+
-
Transferred to another namespace in v10.4+
-
Ancestor renamed in v10.4+
-
Ancestor transferred to another namespace in v10.4+
The following are
**not**
importable as bare repositories:
-
Created in or migrated to hashed storage in v10.3 or earlier, and was not
renamed or transferred in v10.4+, and whose ancestor namespaces were not
renamed or transferred in v10.4+.
There is an
[
open issue to add a migration to make all bare repositories
importable
](
https://gitlab.com/gitlab-org/gitlab-ce/issues/41776
)
.
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment