Preparation for data migration
![]()
Hi,
Soon we need to shift from " version Control" to "RTC".
Can you share any reference material or preparation plan. I want to know the things to be considered for this data migration. What to do, what not to do, etc.
Please suggest.
showing 5 of 8
show 3 more comments
|
One answer
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Feb 23 '15, 3:40 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I would pick a baseline of the files in the old system and then share that in Jazz SCM.
I would discourage to import the whole history into the new system. Keep the old one alive for some time and reduce access permissions. If you don't hear anything for half a year, switch the system off and keep a backup.
This way you should be able to import more than one baseline and be able to detect differences to them once you get started developing.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
The current system is "Version Manager" that needs to be migrated to RTC.
Is this Serena's PVCS Version Manager?
Yes Geoffrey. I have no clue from where to start. Please suggest.
I'm not aware of a direct PVCS->RTC importer. One approach is to use a two step process ... use a PVCS->SVN importer, and then use the SVN->RTC importer. Another approach is to write your own importer script, using the RTC scm command line to create the information in RTC.
Thanks.
If you google "pvcs subversion", the first hit is:
http://www.polarion.com/products/svn/svn_importer.php
I haven't used it myself, but it probably is a good place to start.
For subversion to RTC, see:
https://jazz.net/library/article/650
But if all you need is the latest version from your main branch, then extracting a copy of the files from PVCS onto your local drive, and then just importing them into RTC (using Eclipse, or the scm command line) is definitely the simplest and fastest approach.
Hi Geoffrey,
The difference is that a simple file system import will create a new history item for each imported file (with a single initial version), while the other styles of import will import the previous history of a file (in the case of "write your own script", the amount of history imported will be determined by the algorithm of your script).