Migrating to Subversion


problems can include invalid commit dates, corrupted storage data, etc. It's necessary to fix problems before proceeding with the import.

Once the SVN model is created, it is serialized into a Subversion dump file (a single file, used to re-create the whole SVN repository using the svnadmin tool). This is the most time consuming part of the import process, since the content of every version of every file is processed. The progress can be watched in the log file generated by the importer. Once the dump file is created, it can be (optionally) loaded into the SVN repository by the importer itself, or this task can be left to the user (which is the recommended setting).

Complete documentation of SVN Importer features is bundled in the binary distribution. A description of all the options can be found in the default configuration file. Both binary and source distributions are available for download from project page at http://polarion.org/. The project page also includes a project forum, and a link to SVN repository with sources, tracker and more.


Subversion Book - http://svnbook.com/

Subversion Home Page - http://subversion.tigris.org/

Michal Dobisek (michal.dobisek AT polarion.com) is Software Architect at Polarion Software ( http://polarion.com/). He has experience with CVS, Perforce and Subversion. He has two years experience in using, administering and tweaking Subversion. He holds a Masters degree in Cybernetics from Gerstner Laboratory of the Czech Technical University in Prague.

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.