Geek Answers Handbook

Migrating Source Safe database to SubVersion with history

People,

We have several source secure databases that need to be ported to SubVersion. Is there a (proven and verified) way to transfer them with history?

Thanks Essam

+7
version-control svn visual-sourcesafe configuration-management
source share
5 answers

You can try VssMigrate . This is the C # PowerAdmin VssMigrate port , which has the ability to "Allow individual VSS checks for atomic SVNs through an approximate timestamp."

+3
source share

I am also considering migration, and I have found some pages that can help you in this process:

These 3 pages contain information on how to transfer the full story from VSS to SVN

+8
source share

Stumbled upon this old question from google search. Another choice is from Polarion, which has a free SVN importer that can import from multiple sources. I'm trying now ...

http://www.polarion.com/products/svn/svn_importer.php

0
source share

My company developed the migration tool "Source Safe for Subversion": http://www.abstrakti.com/en-US/Products/Krepost

This tool was developed after problems with any other tool, when we had to transfer the client repository. It is also the only tool that can import SourceSafe tags into SVN.

Let me know if you have any problems, I will be happy to help you.

Eric

0
source share

I would recommend the original vss2svn project (which I used) compared to some of the other parameters listed here (e.g. VssMigrate) (which I did not use but looked at the website) because it:

  • It works on Linux, where you get much faster file operations (compared to NTFS) (for example, conversion takes 30 minutes instead of 12 hours).
  • Very hacked, generates intermediate, editable states (for example, dump file)

In past years, I used VSS / CVS / SVN to administer the database and used vss2svn for several VSS → SVN migrations (about a decade of history, 500 MB, IIRC). My strongest warning to anyone who converts the repository is that the most difficult task is usually not how to map specific files to specific revision numbers, but how to correctly handle corruption in the VSS database. That is why fast work (you are unlikely to achieve perfection for the first time), and a hacker operation is important.

I also highly recommend the vss2svn wiki pages on RunningTheMigration to anyone considering migration, no matter which tool you use at the end.

0
source share

More articles:


All Articles