Migrating from Another SCM System
I looking for steps/documentation/best practices in regard to migrating from one source control system to RTC's SCM system. I have seen the link below which is specific to MS. However, I was looking for similar info for eClipse. Also, are there any specific concerns when migrating from StarTeam?
https://jazz.net/help-dev/clm/topic/com.ibm.team.concert.dotnet.doc/topics/t_migrate_from_scm_to_jazz.html
Thank you!
https://jazz.net/help-dev/clm/topic/com.ibm.team.concert.dotnet.doc/topics/t_migrate_from_scm_to_jazz.html
Thank you!
2 answers
Note that the topic referenced in the question is just about what you need to adjust in Visual Studio *after* you have migrated your version data into RTC SCM ... it doesn't help you actually do the data migration from one source control system to another.
If you don't need version history, and if you don't need to import multiple branches of the same code base, then it is easy to migrate ... just load the tip of the branch you want to import into the file system, and then "share" that file system tree into RTC SCM.
If you want history, then it gets harder. RTC currently only has two built-in "history importers" ... from Subversion and from ClearCase. If you want to import history from some other SCM system, then one approach is to do it as a two phase process ... first import from the other system into either Subversion or ClearCase, and then import from there into RTC. Since Subversion and ClearCase are two of the most commonly used SCM system, there is a reasonable chance that you can find a history importer from the other SCM system to one of those. If that is not the case, then you'll need to script the import yourself.
If you don't need version history, and if you don't need to import multiple branches of the same code base, then it is easy to migrate ... just load the tip of the branch you want to import into the file system, and then "share" that file system tree into RTC SCM.
If you want history, then it gets harder. RTC currently only has two built-in "history importers" ... from Subversion and from ClearCase. If you want to import history from some other SCM system, then one approach is to do it as a two phase process ... first import from the other system into either Subversion or ClearCase, and then import from there into RTC. Since Subversion and ClearCase are two of the most commonly used SCM system, there is a reasonable chance that you can find a history importer from the other SCM system to one of those. If that is not the case, then you'll need to script the import yourself.
Comments
showing 5 of 6
show 1 more comments
https://jazz.net/library/article/650 - Importing data from Subversion and CVS into Jazz Source Control
If you can get your data into CVS or SVN, you can use the SVN importer from the Eclipse client. Check the article for details.
As for StarTeam specifically, there isn't any documentation about migrating from it. Somebody else might have insight about the process.
For setting up with SCM, you'll want to think about the components to create for your source code. You can take a look at the articles in the library to get an idea of how SCM works and give you ideas of how you want to organize your source code in SCM.
If you can get your data into CVS or SVN, you can use the SVN importer from the Eclipse client. Check the article for details.
As for StarTeam specifically, there isn't any documentation about migrating from it. Somebody else might have insight about the process.
For setting up with SCM, you'll want to think about the components to create for your source code. You can take a look at the articles in the library to get an idea of how SCM works and give you ideas of how you want to organize your source code in SCM.