Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

To synchronize Subversion and Git repositories, SubGit maps entities of one system to those of another. One Git repository is always mapped to a single project within Subversion repository. There could be from one to many projects in Subversion repository. Git repository contains SubGit configuration that defines the following information and mappings:

  • Subversion project location within Subversion repository
  • Subversion project branches and tags are mapped to the Git branch and tag references
  • Subversion users are mapped to the Git committers

Above mappings are static and configured within Git repository once before translation and synchronization is started. All mappings and other information is stored in configuration files located in the GIT_REPOS/subgit directory. Following sections describe these mappings in more details.

Note:
Subversion is a very powerful system and sets mostly no limits on the repository and project layout. Hence, it may not be always possible to define necessary mappings for any project stored in Subversion repository found out there in the wild. Such unmappable projects would not be handled by SubGit. However, for the most of the Subversion repositories in production use, mappings could be defined and, in most cases, they are detected automatically by SubGit.

3.1 Subversion project location

Subversion repository may contain one or more projects. Project is a location (folder) in Subversion repository which follows Subversion recommended repository layout, i.e. project folder has trunk, branches and tags subfolders:
/project 
	/trunk # project's "main line" 
	/branches # contains project feature and version branches, copied from trunk or other branches 
	/tags # contains project tags (trunk and branches snapshots)

It is not necessary for trunk, branches and tags folders to have these exact names, but the roles of these folders are important. Each project could be mapped to a bare Git repository as shown in Figure 3.1 and Figure 3.2 along with the corresponding parts of SubGit configuration file.


 Single Project Repository Mapping

Figure 3.1. Single Project Repository Mapping

SubGit configuration file (single project mapping)

[svn] 
# URL that points to a project root 
# (may be the same as Subversion repository root) 
url = http://host/svn/repos


 Multiple Projects Repository Mapping

Figure 3.2. Multiple Projects Repository Mapping

SubGit configuration file (two projects mapping)

/var/git/project1.git/subgit/config 
	[svn] 
	# project location within Subversion repository 
	url = http://host/svn/repos/project1 
	... 
/var/git/project2.git/subgit/config 
	[svn] 
	# project location within Subversion repository 
	url = http://host/svn/repos/project2

  • No labels