是否有 RTC 等效的“挂起模式”？在 ClearCase 中？
我发现 RTC 中的“暂停更改设置”非常有用，而且由于我们也在使用 ClearCase（数十个用户），我想知道 ClearCase 中是否也提供该功能。 如果不是 - 它可以由 script/trigger/hook 生成吗？
我们使用UCM，我想解释一下我的问题： 如果我必须交付并且我想跳过交付一项活动，我可以决定不交付它（如果没有依赖项...），所以我的问题是关于我的当前流的工作：是这样吗？可以“暂停”我的当前流中的活动吗？
提前致谢
I found "Suspend Change-set" in RTC to be very useful, and since we're working with ClearCase as well (dozens of users) I'm wondering if that feature is also available in ClearCase as well.
If not - could it be generated by script/trigger/hook ?
We use UCM, and I'd like to explain my question:
if I have to deliver and I want to skip delivering one activity, I can decide not to deliver it (if no dependencies...) , so my question is regarding working on my current stream: Is that possible to "suspend" an activity from my current stream ?
Thanks in advance
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
简单来说，并不容易。
RTC 基本上是从头开始重写的 ClearCase，以及“挂起”模式 (也称为隐藏或搁置）利用应用变更集（到存储库的任何状态）的概念
UCM 变更集是文件版本的列表。每个版本都与其前身相关联，您无法轻松删除它（除非您执行一些操作负合并），然后稍后重新应用它们。
话虽这么说，Reuven 今天早上才联系我，因为他在 Stream 的快照视图中签出了文件，他想要变基（与您的交付问题类似的问题）。
一种可能的方法是创建另一个视图（动态视图），您可以将其用于变基，然后返回快照视图并更新它：它将检测更新的配置规范（在变基之后），并将不删除您当前签出的任何文件。
签入时，这些文件将与更新版本合并。
Simply put, not easily.
RTC is basically ClearCase rewritten from scratch, and the "suspend" mode (also called stashed or shelve) takes advantage of the notion of applying a changeset (to any state of a repository)
The UCM changeset are a list of versions of files. Each version is tied to its predecessor, and you cannot easily remove it (unless you do some negative or subtractive merges), and then re-apply them later.
That being said, Reuven just contacted me this morning, because he had files in checked out in a snapshot view on a Stream which he wants to rebase (similar issue to your deliver problem).
A possible way to do that is to create another view (dynamic one), which you can use for your rebase, and then go back to your snapshot view and update it: it will detect the updated config spec (following the rebase) and will not erase any of your currently checked out files.
On the checkin, those files will be merged with the updated version.