Synergy to SVN tools?
Arjen Jonkhart
Hi colleagues,
I was wondering if any of you came across some tools to convert a CM Synergy database to an SVN repo? Preferably with as much history as possible, of course J
We currently have a requirement to take one of our larger databases over to Subversion.
Any and all suggestions and experience are welcomed.
Thanks in advance,
Arjen.
William D Richards
Me too. We are heading in that direction at GM – just retired Rational Change, moving it to RTC. (I architected that process, and used RSS) Rational Synergy to Subversion is next…… ARE there any tools for this?
Bill Richards
--
You received this message because you are subscribed to the Google Groups "Synergy CM Tool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
synergy-cm-to...@googlegroups.com.
To post to this group, send email to
synergy...@googlegroups.com.
Visit this group at https://groups.google.com/group/synergy-cm-tool.
For more options, visit https://groups.google.com/d/optout.
Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.
Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.
cmtodd
Good to hear from you guys.
Sorry, no tools to mention for migrating from Synergy to svn. :-(
Of course, the ease of automating it yourself depends on if you really need all file history, or only baseline history. If you want all the file history, then you have quite a chore to move the files and then reconstruct each baseline from those files in the new CM system.
If you can live with only baseline history, Then it is just a matter of moving and syncing into the new CM system each baseline. That is of course unless you have sub-projects and want to preserver some kind of project hierarchy in the new system, then you are back to much more complicated (but still not as bad as having to reconstruct from the individual file versions).
Probably not telling you anything you've not already thought of. My real reasons for my response is to give a plug for the tool we chose. We are moving to a new tool as well, looked at several both "free" and purchased. We saw svn as more the past than the future. Also we were concerned with scaling and also how to duplicate our use of sub-projects for building blocks. We choose Plastic SCM and are still very happy with the decision. If you are not yet pass the point of no return on your decision making process for a new tool, you might want to check it out: plasticscm.com. Some keys we liked:
- Can work central, distributed, or any combo.
- VERY fast even when working to a central server over the WAN
- A one to one mapping of sub-project hierarchy to Plastic SCM features ("XLink" to repos).
- Easy to use and easy for users coming from other standard CM tools to pick up (e.g. GIT).
- Designed to work with VERY large files and projects. (Our 1-8GB and 50K file projects are not even close to the size of some of their other customers.)
- Built in ACL security.
- While not "free", the price is very reasonable.
www.plasticscm.com
Todd