列出所有源安全链接文件的工具 [英] Tool to list all source safe link files
问题描述
我的客户正在从Source Safe迁移到Clearcase.他们需要列出Source Safe数据库中的所有链接文件，以便可以将链接转移到Clearcase，因为显然所有源都必须在第1天检查到Clearcase中，而丢失任何现有链接.
My client is migrating from Source Safe to Clearcase. They need to list all the link files in the Source Safe database so the links can be carried over to Clearcase, as apparently all the source must be checked into Clearcase on day 1, losing any existing links.
是否有用于创建此报告的工具，甚至可以完全导入到clearcase中?
Are there any tools for creating this report, or perhaps even doing the full import into clearcase ?
我的计划是编写一个powershell脚本来递归Source Safe SS文件夹，并使用COM查找链接.
My plan is to write a powershell script to recurse Source Safe the SS folders, findings links using COM.
谢谢.
推荐答案
如VonC所述，从VSS到ClearCase的导入确实非常糟糕:
As VonC mentioned, the import from VSS to ClearCase is truly atrocious as:
- 导出/导入需要永远的时间才能完成，以至于我们为此针对IBM开了一个PMR(这没有帮助，顺便说一句)
- Source Safe共享将转换为文件，从而在各处创建重复项(恐怖！).
我自己从事ClearCase UCM的工作，我们做出了与您相同的决定(根据我在CM的10年经验，这始终是最好的决定):留下历史以供参考并最多导入几个手动在其他版本的基础上进行版本转换(例如，当前正在开发；正在测试中；正在实时发布).
I work on ClearCase UCM myself, and we took the same decision as you (which, in my 10 years of experience in CM, is ALWAYS the best decision): leave the history behind for reference and import at most a couple of versions one on top of the others, by hand (like current in development ; current in test ; current in live).
我们解决股票问题的方法如下:
The way we solved the shares' problem is as follow:
-
与源树隔离的共享"，将独立地从其他源中导入
The "shares" where isolated from the source-tree, to be imported independantly from the other sources
从头开始导入的其他来源(无历史记录且没有共享).假设在一个名为MAIN_SRC的组件中
The other sources where imported (without the history and without the shares) from scratch. Let say in a component called MAIN_SRC
从头开始导入(没有历史记录)的股票.让我们在名为SHARE_SRC
The shares where imported (without the history) from scratch. Let say in a component called SHARE_SRC
已创建一个包含以下两个组件的项目:MAIN___SRC和SHARE_SRC.
A project was created containing both components: MAIN___SRC, and SHARE_SRC.
现在，由于您的共享位于主源代码中，因此当您的IDE(例如Visual Studio)完全希望它们位于以前的相同文件夹(即，在Visual中，如果您不解决此问题，则所有项目都会出错，并且所有文件都需要从Visual自身内部重新链接，等等...很多工作).
Now, the problem is not solved because your shares are living aside your main source code, when your IDE (e.g. Visual Studio) fully expects them to be in the same folders they were before (i.e. in Visual all your projects become wrong if you don't solve this issue, and all the files would need to be relinked from within Visual itself, etc... A lot of work).
这可以通过使用ClearCase VOB符号链接来解决:
This is resolved by using ClearCase VOB symbolic links:
让我们说在MAIN___SRC中，您需要在SHARE_SRC中使用一个名为myShared文件的文件.
Let says in MAIN___SRC you need to use a file called myShared file in SHARE_SRC.
从需要使用myShared文件的文件夹中，使用命令行界面并运行:
From within the folder needing to use the myShared file, use the command line interface and run:
cleartool ln -s ..\..\SHARE_SRC\(myPath)\mySharedFile .
您需要尽可能多的.. \ ..才能进入ClearCase中的组件文件夹级别，然后沿着SHARE_SRC组件文件夹中的路径(myPath)向下移动.
You need as many ..\.. as necessary to go up to the component folder level in ClearCase, and then down following your path (myPath) in the SHARE_SRC component folder.
记住ClearCase路径由以下组成:
Remember the ClearCase path is composed of:
M:\ View_name \ VOB_name \ Component_name \您的第一级文件和文件夹
(VOB_name \ Component_name是组件的根"，如果只有单个组件VOB，则在这种情况下，VOB_name \ Component_name变为VOB_name)
( VOB_name\Component_name is the "root" of the component, apart if you have single component VOB, in this case VOB_name\Component_name becomes just VOB_name)
最简单的方法是对所有需要创建的VOB符号链接进行映射，并将所有必要的"cleartool ln -s"命令行放入脚本中以运行一次.
The easiest way is to have a mapping of all the VOB symbolic links that need to be created, and put all necessary "cleartool ln -s" command lines in a script to run once.
在那之后，您应该会很好，并且您的IDE认为源是它们过去的源.
After that, you should be fine, and your IDE think the sources are where they used to be.
干杯
托马斯
这篇关于列出所有源安全链接文件的工具的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
