Page History

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

   • Download   SubGit plugin for Gerrit server.
     
     MD5 checksum: 3902cf714c856524e8f4815ad70c00f3Move :   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.

     
     

   • Move the downloaded file into GERRIT_SITE/plugins directory:

     where

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

     
     

   • Open Gerrit configuration file residing by the following path:

     No Format
     GERRIT_SITE/etc/gerrit.config

     where

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

     
     Locate   receive.timeout parameter   parameter and set it to 0:

     No Format
     [receive] 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 the Gerrit daemon:
      

     • if you start have started the Gerrit daemon manually – stop –  stop it by Ctrl+C and then start it again:

       Code Block
       language text theme FadeToGrey title Start Gerrit daemon
       > java.exe -jar bin\gerrit.war daemon --console-log

       
       

     • if you have Gerrit run as Windows service - restart the service using services.msc console or by commands:

       No Format
       > sc stop Gerrit > sc start Gerrit

       
       

   • Check if SubGit plugin is showed in Gerrit:
     
     

2. Configure the repository
   
   
   • Create an empty Git repository:
     
     

   • Open the Gerrit server console and step into   git directory within directory  within   GERRIT_SITE:

     Code Block
     language text theme FadeToGrey title CD to git directory
     > cd GERRIT_SITE\git

     where

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

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

     Code Block
     language text theme FadeToGrey title Git directory contain
     > dir Volume in drive C has no label. Volume Serial Number is B86A-EF32 Directory of c:\gerrit\git 11.05.2017 20:21 <DIR> . 11.05.2017 20:21 <DIR> .. 11.05.2017 17:50 <DIR> All-Projects.git 11.05.2017 17:50 <DIR> All-Users.git 11.05.2017 20:14 <DIR> project.git

     
     

   • Run this command to configure SubGit import:

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

     where

     • SVN_URL   – SVN –  SVN project URL.
     • GIT_REPO – a REPO  –  path to the new Git repository.
     • TRUNK       –  a  –  path, relative to   SVN_URL, that   that leads to an the SVN directory that plays a role of the acts as the   main line of development.

     Expand
     title See subgit configure example…
     Code Block language text theme FadeToGrey title subgit configure > subgit.bat configure --layout auto --trunk trunk http://example.com/svn/repository/project c:\gerrit\git\project.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 : C:\repo.git Detecting peg location... Authentication realm: <http://example.com:80> Subversion Repository Username [user]: 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: C:\repo.git\subgit\config 2) Define at least one Subversion credentials in default SubGit passwd file at: C:\repo.git\subgit\passwd OR configure SSH or SSL credentials in the [auth] section of: C:\repo.git\subgit\config 3) Optionally, add custom authors mapping to the authors.txt file(s) at: C:\repo.git\subgit\authors.txt 4) Run SubGit 'install' command: subgit install "C:\repo.git"

     
     

   • Specify authors mapping

     Configure authors mapping in   default authors mapping file:

     No Format
     GIT_REPOS/subgit/authors.txt

     Or change Or  change   core.authors option so   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 into the Git repository by the command:
   
   

   No Format
   > subgit import GIT_REPO

   where 

       GIT_REPO – a REPO  –  a path to the Git repository.

   Expand
   title See subgit import example…
   Code Block language text theme FadeToGrey title subgit import > subgit import c:\gerrit\git\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 19 seconds. IMPORT SUCCESSFUL

   
   

4. When the command completed, you can clone your new Git repository and start to work with it:
   
   

   No Format
   > git clone GIT_REPO WORK_TREE

   where 

       WORK_TREE – a TREE  –  a path to your working copy.
   
   

   Expand
   title See git clone example…
   Code Block language text theme FadeToGrey title git clone example $ git clone http://gerrit.example.com/user/project.git C:\project.git Cloning into 'C:\project.git'... Password for 'http://user@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.

   
   

   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.

   
   

5. Get support:
   
   Have you faced with any problems, see the following guide for more details:
   
   
   • SubGit troubleshooting guide
   • SubGit configuration file reference
   • Authors mapping
   • Authors mapping examples
   • Branches and tags mapping
   • Branches and tags mapping examples
   • Automated branches and tags mapping generation
      

   Info
   title License note
   Note: no license key required for import!

   
   

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