从SourceSafe迁移到ClearCase的最佳方法是什么？

本文介绍了从SourceSafe迁移到ClearCase的最佳方法是什么？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我们目前有一个庞大的SourceSafe DB，其中包含十年的代码。我们正在寻找一种简单，稳定的方式将所有这些内容导入到新的Clearcase / Jazz环境中。

We currently have a fat SourceSafe DB with ten years of code in it. We're looking for an easy and stable way to import all of this in to a new Clearcase/Jazz environment.

什么是最好的最佳方法？

What is the best best method of doing this and are there any tools out there to do this automagically?

推荐答案

我知道这不能直接回答您的问题，但是我们有一个工具可以自动执行此操作？几年前，我们从VSS迁移到Perforce时遇到了类似的问题。我们研究了迁移所有文件历史记录的方法，但是发现的任何解决方案都存在问题，执行起来将花费很长时间。

I know this doesn't answer your question directly, but we had a similar problem several years ago when we moved from VSS to Perforce. We looked at the ways in which we could migrate the histories for all the files, but any solution we found had problems and would have taken a long time to execute.

最后，我们只是简单地决定将代码的当前版本导入Perforce作为基准，并将旧的历史记录保留在VSS中。早期，我们确实偶尔会提到VSS，但是几个月后我们就不需要了。

In the end we simply decided to import the current version of the code into Perforce as the baseline and leave the old history in VSS. In the early days we did refer back to VSS occasionally, but after a few months we didn't need to.

如果文件有问题，您只需要最近的几个修订，以便能够看到更改的内容以及原因。因此，如果文件更改非常频繁，您很快就会在新存储库中建立有用的历史记录。如果文件没有更改，那么根据定义它是稳定的，并且您不需要历史记录。

If there's a problem with a file you only need the last couple of revisions to be able to see what's changed and why. So if the file changes fairly frequently you'll soon build up a useful history in the new repository. If the file doesn't change then by definition it's stable an you don't need the history.

如果备份旧存储库，您可以随时返回到该文件。如果您真的需要挖掘保留历史记录。

If you back up the old repository you can always go back to it if you really need to to dig out the hold history.