It's all about the answers!

Ask a question

Migrating from Jazz SCM to GIT

Dave Marsico (4511014) | asked Apr 13 '15, 10:53 a.m.
Have the unfortunate task for migrating source code from Jazz SCM to GIT.   The optimal goal is to retain all the changeset history.     But attempts to walk though stream history changeset by changeset seems challenging as we encounter gaps due to dependencies... (as we accept changesets 1 by 1, hoping to create a corresponding GIT commit).    So wondering if conventional wisdom (for a successful outcome) is to instead map changeset "bundles" to git commits at the stream snapshot or baseline level.  I.e. accept all changeset for a baseline, do a git commit , tag this and move on to next one.  Appreciate any expert opinions or comments.

One answer

permanent link
Surya Tripathi (65017) | answered Apr 13 '15, 7:49 p.m.
As you have observed, keeping an one-to-one mapping RTC changesets and GIT commits can be very daunting and challenging for manual migration. Mapping at the baseline level offers an easier migration but then you will be loosing changeset history. Going by your approach of mapping baselines with commits makes sense. And, if you are going to keep the RTC repository live (only for reading),  you will be able to look up a changeset if necessary.

Your answer

Register or to post your answer.