在Clearcase UCM中重命名一个小工具，实际上建议这样做吗？ [英] Renaming a vob in Clearcase UCM , is it practically advisable?

问题描述

我们选择了与我们的项目名称一致的VOB名称（不要将项目名称与UCM项目名称混淆），以便我们可以轻松区分。

We selected vob names aligned with our project name ( do not confuse project name with UCM project name) so that we can easily distinguish.

但是最近我们的项目名称当我们将2种产品合并为一种产品时，已经发生了变化。

But recently our project name has been changed as we merge 2 products into one.

有人建议重命名Vob以指示项目名称。

Some people suggested to rename the vob to indicate the project name.

我们试图分析开发和建设的影响。

We tried to analyze the impacts from development and build & release perspective.

变化很小，在这里和那里我们不得不更改path变量以指示最新的VOB名称。

There were very little changes, here and there we had to change the path variable to indicate the latest vob name.

因此，我们同意重命名VOB名称。

So we agree for renaming the vob name.

然后作为Clearcase管理员，我必须进行影响分析。

Then as Clearcase admin i had to do impact analysis.

当我向高级Clearcase管理员咨询时。他们列出了可能的影响，如下所示。

When i asked advice from senior Clearcase admin. They listed possible impacts such as below.

1. VOB上的符号链接将断开，因此可能需要修复。


2. 最好在更改Vob名称之前清除所有签出项目


3. 将锁定Vob，以防止用户在更改名称时使用旧的Vob名称。


4. Vobs必须卸载并重新安装


5. 快照和CCRC视图可能会受到影响，因此必须重新同步。

1. symlinks across vob will be broken so they may need to repair.
2. It is better to clear all check out items before changing the vob name
3. vob will be locked to prevent users from using the old vob name while name change.
4. Vobs has to be unmounted and remounted
5. Snapshot and CCRC views may be affected , so it has to be resynchronized.

等。

您的项目中是否有任何尝试过的VOB重命名？您能否分享您所遇到的对我们有帮助的实际影响？

Has any one tried vob rename in your project? Can you share the practical impacts which you have faced which will be helpful for us?

如果您已经尝试并决定不以任何方式再做一次，可以提出建议吗？为什么实际上不建议这样做？

If you already tried and decided not to do it again by any means , can you advice why it is not practically advisable to do so?

预先感谢。

推荐答案

最重要的是，您的UCM组件将不再起作用：即使您可以更改其名称（它们的名称），也无法更改其根目录（即，VOB中的路径或VOB本身）。 标题）。

这与UCM项目名称无关（UCM项目不关心UCM重命名，只有UCM Streams可以）

Most importantly, your UCM components won't work anymore: you cannot change their root directory (ie path within the vob, or vob itself), even though you can change their name (their "title").
And that is independent from UCM project name (the UCM project don't care about UCM rename, only the UCM Streams do)

坦率地说，当面对这种重构时，我：

Frankly, when face with this kind of refactoring, I:

• 将所有内容保留在适当的位置，但锁定且为只读


• 从新组件/声音开始，导入最新的基线。

这篇关于在Clearcase UCM中重命名一个小工具，实际上建议这样做吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！