1. John Strano
  2. PowerBuilder
  3. Wednesday, 06 February 2019

Much of the online information on migrating/converting CVS repositories to Git is at least 7 years old.

Does anyone have more recent experience and can recommend procedure and/or utilities?

Looking for the most dependable.

Of course would also desire the least moving parts, to reduce the configuration/points of failure to a minimum.

 

Thank you!

Bruce Armstrong Accepted Answer Pending Moderation
2
Votes
Undo

There's a few tools listed on the GitLab website:

https://docs.gitlab.com/ee/user/project/import/cvs.html#how-to-migrate

And here's a blog article on it:

https://www.isostech.com/blogs/software-development/journey-cvs-git/

My experience was more with PVCS to SVN.  We used the Polarion tool for that:

https://polarion.plm.automation.siemens.com/products/svn/svn_importer

After a great deal of work doing that though, I'm not sure it was really worth the effort. The only thing you get is access to the change history, and after a short time none of that was anything we were interested in anymore.

For the projects where we've gone from SVN to Git, we haven't bothered with a migration.  We just created fresh repositories with the baseline we were starting with.

 

Comment
ROFL. Thanks for the validation of going to GitLab's page.

That's where I first landed and from where I branched out.



Thanks for the isostech link. I hadn't found that.



Yes, it's only the change history the customer was thought to need to migrate.

The tracking of the change sets will start to "age out" soon.

As you say, the effort may not be worth the return in that it'll be obsolete within 2 or 3 releases of their product.
  1. John Strano
  2. Thursday, 7 February 2019
There are no comments made yet.
  1. Thursday, 7 February 2019
  2. PowerBuilder
  3. # 1
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.