- Install SubGit tool according to the Installation guide.
- Configure GitLab server:
- Log in to GitLab web GUI and create a new project:
Give a name to your project, do not check “Initialize repository with a README” checkbox, and click Create project button.
- Log in to GitLab web GUI and create a new project:
- Configure the repository:
Change identity to 'git' user:
Code Block language text theme FadeToGrey title change identity to git user
$ su git
Change the directory to the one that contains the newly created project.
Older versions of GitLab stored projects in
where <username> was the GitLab username that had been used during the project creation on step 1.
Since version 10.0 GitLab uses hashed storage as follows:
To find the repository path in GitLab v.10+, follow this guide.
Navigate to that directory:
Code Block language text theme FadeToGrey title change directory
$ cd /var/opt/gitlab/git-data/repositories/<repo_path>
Perform initial configuration:
$ subgit configure --layout auto --trunk TRUNK SVN_URL GIT_REPO
SVN_URL –SVN project URL.
GIT_REPO –a path to the new GitLab project that's been created at step 1, for example,
TRUNK –a path, relative to
SVN_URL, that leads to an SVN directory that plays the role of the main line of development.
Expand title see the configuration command example. Code Block language text theme FadeToGrey title subgit configure example
$ subgit configure --layout auto --trunk trunk http://svn.example.com/svn/repository/project ./project.git SubGit version 3.2.4 ('Bobique') build #3670 Configuring writable Git mirror of remote Subversion repository: Subversion repository URL : http://svn.example.com/svn/repository/project Git repository location : ./project.git Git repository is served by GitLab, hooks will be installed into 'custom_hooks' directory. Detecting peg location... Authentication realm: <http://svn.example.com/:80> Subversion Repository Username [git]: user Password for 'user': Peg location detected: r10248 project/trunk Fetching SVN history... Done. Growing trees... Done. Project origin detected: r1 project/trunk Building branches layouts... Done. Combing beards... Done. Generating SVN to Git mapping... Done. CONFIGURATION SUCCESSFUL To complete SubGit installation do the following: 1) Adjust Subversion to Git branches mapping if necessary: /var/opt/gitlab/git-data/repositories/user/project.git/subgit/config 2) Define at least one Subversion credentials in default SubGit passwd file at: /var/opt/gitlab/git-data/repositories/user/project.git/subgit/passwd OR configure SSH or SSL credentials in the [auth] section of: /var/opt/gitlab/git-data/repositories/user/project.git/subgit/config 3) Optionally, add custom authors mapping to the authors.txt file(s) at: /var/opt/gitlab/git-data/repositories/user/project.git/subgit/authors.txt 4) Run SubGit 'install' command: subgit install ./project.git
Specify authors mapping.
Configure authors mapping in default authors mapping file:
Specify a username and password that are used by SubGit to access the SCN repository. Edit passwd file:
By default, there's only subgit secret credential pair. Replace it with the username and its corresponding password.
Info title SVN authentication
There are several methods to configure authentication to access the SVN server, but we use a plain text password file here to simplify the guide. See more authentication methods in SVN Authentication if this method does not fit your needs.
- Establish a mirror and start using the new Git repository:
Establish a two-way mirror with this command:
$ subgit install GIT_REPO
GIT_REPO– a path to the GitLab project.
Expand title See SubGit install example… Code Block language text theme FadeToGrey title subgit install
$ subgit install ./project.git SubGit version 3.2.4 ('Bobique') build #3670 Translating Subversion revisions to Git commits... Subversion revisions translated: 10248. Total time: 2 hours 15 minutes 24 seconds. INSTALLATION SUCCESSFUL
When the command completes, you can clone your new Git repository and start to work with it:
$ git clone GIT_REPO WORK_TREE
WORK_TREE– a path to your working copy.
Expand title See the command example Code Block language text theme FadeToGrey title repository cloning example
$ git clone http://email@example.com/user/project.git /home/user/gitlab_project.git Cloning into '/home/user/gitlab_project.git'... Password for 'http://firstname.lastname@example.org': remote: Counting objects: 99, done. remote: Compressing objects: 100% (39/39), done. remote: Total 99 (delta 50), reused 99 (delta 50) Unpacking objects: 100% (99/99), done.
Warning title Empty working tree case
If Git warns you that you are cloning an empty repository and you don't see your files in the working tree, most probably automatic branches and tags mapping didn't work correctly. In this case, mapping has to be set manually, see details on mapping in Branches and tags mapping.
Try and buy.
Info title Trial period
Note: the trial period for SubGit mirror is 30 days, after that period you should buy a license key at https://subgit.com/pricing.
Once you receive an email with a license key, upload this license key to your server and run the following command:
$ sudo subgit register --key subgit.key GIT_REPO
GIT_REPO– a path to your newly created Git repository.
Expand title Subgit register example… Code Block language text theme FadeToGrey title subgit register
$ sudo subgit register --key subgit.key /home/user/repo.git SubGit version 3.2.4 ('Bobique') build #3670 Registration information: Registered for: Example company Purchase ID: OS-111111111111111 Expiration date: April 23, 2028 You may use this key to register 9 more repositories (out of 10). REGISTRATION SUCCESSFUL Thank you for registering SubGit! Visit http://www.subgit.com/ in case you have any questions and for more information on SubGit.
- Get support:
If you encounter any problems, see the following guides for more details:
Note: no license key required for import!