ClearCase通用工作流程示例 [英] ClearCase Common Workflow Example

问题描述

我正在使用ClearCase，并且对该工具还很陌生。与其他源代码控制（例如git和svn）相比，我感到困惑和麻烦。我想知道是否有人可以完成典型的工作流程。因此，现在我们有一个主要的集成流，然后是一个子集成流，然后是每个项目的子集成流。

I am working with ClearCase and I am very new to the tool. I find it confusing and cumbersome compared to other source control, like git with svn, for example. I was wondering if someone could walk through a typical workflow. So right now we have a main integration stream, then a child stream on that, then from there child streams for each project.

用例1：

我检入文件并希望每个人都进行更改。我必须首先添加到ClearCase或签入，然后必须交付给我上方的每个流（两次），然后创建基线并进行重新设置以将更改逐级向下。这是正确的吗？

I check in a file and want everyone to get changes. I have to first add to ClearCase or check in, then I have to deliver to each stream above me (twice), then I would create a baseline and do a rebase to cascade the changes back down. Is this correct?

用例2：

如果我忘记了所做的更改，是否有一种机制查看我修改过的所有文件？并立即全部检查。

If I forget what changes I made, is there a mechanism to see all the files I modified? and check them all in at once.

用例3：

如果我要修改文件，

用例4：

如果我移动文件，必须我从透明的情况下将其删除，然后重新添加了吗？或者，如果我只想重命名程序包或文件，该怎么办？

If I move a file, must I remove it from clear case and then re-add it? Or what about if I just want to rename a package or file?

用例5：

现在我对主集成流有一个动态视图，然后是子视图在两者之间。如果我仅在一个流上工作，是否有必要在其他所有流上都拥有视图？

Right now I have a dynamic view on the main integration stream, then child views in between. If I am just working on one stream, is it necessary to have views on all the other streams?

我只是想有效地使用清晰的案例，但似乎要完成简单的任务，却有很多开销。谁能提供任何有关简化体验的提示或建议？

I am just trying to use clear case effectively, but it seems to accomplish simple tasks, there is a lot of overhead. Can anyone give any tips or advice on how to simplify the experience?

谢谢

推荐答案

您可以在此处查看 Git和ClearCase之间的主要区别，以帮助您入门。

You can see the main differences between Git and ClearCase here, to get you started.

用例1：

Use Case 1:

是，这就是为什么建议在以下情况下使用一个流的原因而不是本地的每个开发人员一个流。模型（我在这里谴责）

Yes, which is why it is advised to use one stream if possible, instead of the native "one stream per developer" model (that I denounced here)

使用情况2：

Use Case 2:

您可以使用基于 lsco | ci ，按此答案。

我详细介绍了这种方法在 使用Clearcase进行递归检入

ct lsco -r -cvi -fmt "ci -nc \"%n\"\n" | ct
ct lsco -r -cvi -fmt "unco -rm %n\n" | ct

用例3：

Use Case 3:

是，您需要在修改和签入之前签出文件，除非您直接在快照视图中以被劫持的文件；或在动态视图中显示为隐藏文件。

例如，参见 Eclipse不允许在未在ClearCase中检出的情况下修改文件

Yes, you need to checkout a file, before modification and checkin, unless you modify it directly in a snapshot view, as an hijacked file; or in a dynamic view as an eclipsed file.
See for instance "Eclipse not allowing to modify files without checkout in ClearCase" as an illustration of that issue.

用例4：

Use Case 4:

cleartool mv 会为您做到这一点（就像我在这里提到的）一样，但是您需要先检出父文件夹。

cleartool mv will do that for you (as I mentioned here), but you need to checkout the parent folder first.

要移动或重命名元素的目录住所必须退房。还必须检出目标目录。此目录可能与源目录相同。

The directory where the element to be moved or renamed resides must be checked out. The destination directory must also be checked out; this directory may be the same as the source directory.

用例5：

Use Case 5:

如果我仅在一个流上工作，是否有必要在其他所有流上都具有视图？

If I am just working on one stream, is it necessary to have views on all the other streams?

不，这些视图不必启动甚至不必创建。

No, those views don't have to be started or even created.

这篇关于ClearCase通用工作流程示例的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！