Page tree
Skip to end of metadata
Go to start of metadata
  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.

       See download command example…
      wget example
      $ wget https://subgit.com/download/subgit-gerrit-plugin-1.0.0-EAP4.jar
      
          --2017-05-11 18:15:37--  https://subgit.com/download/subgit-gerrit-plugin-1.0.0-EAP4.jar
          Resolving subgit.com (subgit.com)... 138.201.118.241
          Connecting to subgit.com (subgit.com)|138.201.118.241|: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:

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

      where

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


    • Open Gerrit configuration file by the following path:

      GERRIT_SITE/etc/gerrit.config

      where

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


      Locate   receive.timeout parameter and set it to 0:

      [receive]
         timeout = 0


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

      $ git config -f GERRIT_SITE/etc/gerrit.config receive.timeout 0
    • Restart Gerrit daemon:

      $ GERRIT_SITE/bin/gerrit.sh restart

      where

      • GERRIT_SITE  –  the directory that was used  as   $sitepath  during  Gerrit installation.
       See an example of the command output…
      Restart Gerrit daemon
      $ /gerrit/bin/gerrit.sh 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:

      CD to git directory
      $ cd GERRIT_SITE/git

      where

      • 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

      Git 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:

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

      where

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

      Configure authors mapping in   default authors mapping file:

      GIT_REPOS/subgit/authors.txt 

      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

    $ subgit import GIT_REPO 

    where 

        GIT_REPO  –   a path to the Git repository.

     See subgit import example…
    subgit import
    $ subgit import ./project.git
    
         SubGit version 3.2.4 ('Bobique') build #3670
    
         Authentication realm: <http://svn.example.com:80> 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.
    
          IMPORT SUCCESSFUL
  4. Clone your new Git repository and start working with it

    $ git clone GIT_REPO WORK_TREE

    where 

        WORK_TREE  –  a path to your working copy.

     See git clone example…
    git clone example
    $ git clone http://gerrit.example.com/user/project.git /home/user/project.git
      Cloning into '/home/user//project.git'...
      Password for 'http://gerrit.example.com': 
      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.

    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 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:

    Note:

    For one-time import, no license is needed.


    Should you need any assistance, don't hesitate to contact us at support@subgit.com