Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Configure Gerrit server:

    • Login to console on Gerrit server and install SubGit tool according to the   Installation guide.

    • Download   SubGit plugin for Gerrit server.

      MD5 checksum: a2db62d13ce8ac5c55515c14f90ea28b
      Compatible Gerrit versions: 2.9.x, 2.10.x, 2.11.x, 2.12.x, 2.13.x, 2.14.x and 2.15.x.

      titleSee download command example…

      Code Block
      titlewget example
      $ wget
          --2017-05-11 18:15:37--
          Resolving (
          Connecting to (||:443... connected.
          HTTP request sent, awaiting response... 200 OK
          Length: 9709051 (9.3M) [application/java-archive]
          Saving to: ‘subgit-gerrit-plugin-1.0.0-EAP4.jar’
          100%[============================================================================================================>] 9,709,051    814KB/s   in 10s    
          2017-05-11 18:15:48 (938 KB/s) - ‘subgit-gerrit-plugin-1.0.0-EAP4.jar’ saved [9709051/9709051]

    • Move the downloaded file into plugins directory:

      No Format
      $ mv ./subgit-gerrit-plugin-1.0.0-EAP4.jar GERRIT_SITE/plugins


      • GERRIT_SITE –  the directory that was used as $sitepath during Gerrit installation.

    • Open Gerrit configuration file by the following path:

      No Format


      • GERRIT_SITE  –  the directory that was used  as   $sitepath  during  Gerrit installation.

      Locate   receive.timeout parameter and set it to 0:

      No Format
         timeout = 0

      If you have Git installed on this machine, it can be done by the following command:

      No Format
      $ git config -f GERRIT_SITE/etc/gerrit.config receive.timeout 0

    • Restart Gerrit daemon:

      No Format
      $ GERRIT_SITE/bin/ restart


      • GERRIT_SITE  –  the directory that was used  as   $sitepath  during  Gerrit installation.
      titleSee an example of the command output…

      Code Block
      titleRestart Gerrit daemon
      $ /gerrit/bin/ restart
                  Stopping Gerrit Code Review: OK
                  Starting Gerrit Code Review: OK

    • Check if SubGit plugin is showed in Gerrit:

  2. Configure the repository

    • Create an empty Git repository:

    • Open Gerrit server console and navigate to   git directory within GERRIT_SITE:

      Code Block
      titleCD to git directory
      $ cd GERRIT_SITE/git


      • GERRIT_SITE  –  the directory that was used  as   $sitepath  during  Gerrit installation.

      The newly created project directory should be present here and named <given project name>.git

      Code Block
      titleGit directory contain
      $ ls -l
         drwxr-xr-x. 7 root root 100 May 10 12:00 All-Projects.git
         drwxr-xr-x. 7 root root 100 May 10 12:00 All-Users.git
         drwxr-xr-x. 7 root root 100 May 11 19:26 project.git

    • Run this command to configure SubGit import:

      No Format
      $ subgit configure --layout auto --trunk TRUNK SVN_URL GIT_REPO


      • SVN_URL   –  SVN project URL.
      • GIT_REPO  –  a path to the new Git repository.
      • TRUNK       –  a path, relative  to   SVN_URL,  that leads to an SVN directory serving as the   main line of development.
      titleSee subgit configure example…

      Code Block
      titlesubgit configure
      $ subgit configure --layout auto --trunk trunk ./repo.git
                  SubGit version 3.2.4 ('Bobique') build #3670
                  Configuring writable Git mirror of remote Subversion repository:
                      Subversion repository URL :
                      Git repository location   : ./repo.git
                  Detecting peg location... 
                  Authentication realm: <> Subversion Repository
                  Username [user]: user
                  Password [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.
                  To complete SubGit installation do the following:
                  1) Adjust Subversion to Git branches mapping if necessary:
                  2) Define at least one Subversion credentials in default SubGit passwd file at:
                     OR configure SSH or SSL credentials in the [auth] section of:
                  3) Optionally, add custom authors mapping to the authors.txt file(s) at:
                  4) Run SubGit 'install' command:
                      subgit install ./repo.git

    • Specify authors mapping

      Configure authors mapping in   default authors mapping file:

      No Format

      Or  change   core.authors  option  so that it points to the global authors mapping file.

      Find more details about authors mapping in   the   Authors mapping article.

  3. Import data to the Git repository

    No Format
    $ subgit import GIT_REPO 


        GIT_REPO  –   a path to the Git repository.

    titleSee subgit import example…

    Code Block
    titlesubgit import
    $ subgit import ./project.git
         SubGit version 3.2.4 ('Bobique') build #3670
         Authentication realm: <> Subversion Repository
          Username [git]: user
          Password for 'user': 
          Translating Subversion revisions to Git commits...
             Subversion revisions translated: 10248.
             Total time: 2 hours 15 minutes 38 seconds.

  4. Clone your new Git repository and start working with it

    No Format
    $ git clone GIT_REPO WORK_TREE


        WORK_TREE  –  a path to your working copy.

    titleSee git clone example…

    Code Block
    titlegit clone example
    $ git clone /home/user/project.git
      Cloning into '/home/user//project.git'...
      Password for '': 
      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.

    titleEmpty 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 the automatic branches and tags mapping didn't work correctly. In this case, mapping has to be set manually, see details on mapping in the   Branches and tags mapping.

  5. Get support

    If  you have encountered any problems, see the following guides for more details:

    License note

    For one-time import, no license key is required for import!is needed.

    Should you need any assistance, don't hesitate to contact us at