本文介绍了Clearcase:集成流合并(补丁)的活动依赖性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有一个补丁模型,我们打算使用 cset.pl -findmerge< activity> 有选择地将累积活动合并到补丁流(集成流到集成流)。请注意,我们使用的是单流模型;尽管将支持对使用自己的开发流的团队的支持(即,当他们加入一个项目时,默认情况下将与集成一起工作)。

We have a patch model where we're intending on using cset.pl -findmerge <activity> to selectively merge cumulative activities to a patch stream (integration stream to integration stream). Note that we're using a single stream model; although support for teams working with their own dev stream would be supported (i.e. when they join a project they would be working with the integration by default).

但是存在问题

所以说您有集成流A

file a.txt
-> Change 1 (baselined ReleaseA)-> Change 2 -> Change 3

fileb.txt
-> Change 1 (baselined ReleaseA)-> Change 2

集成流B和配置。经理决定他们要在新补丁中包含 Change 3 (补丁集成流-集成流C)。

他们执行 cset.pl fetchmerge 变更3 (其中包括对变更2 的更改) )。

文件b 的更改2 未被接收,因此问题正在识别这些活动依赖性

an integration stream B and the config. manager decides they want to include "Change 3" in a new patch (patch integration stream - integration stream C).
They perform a cset.pl fetchmerge against Change 3 (which includes changes for Change 2).
Change 2 for fileb does not get picked up so the issue is identifying these activity dependencies.

有人有什么想法吗?

推荐答案

必须使用多种cctool命令查看视图中的当前版本并将其推送到脚本中以获取活动依赖项列表

Had to use a variety of cctool commands to view current version in view and pushed it into a script to get a list of activity dependencies

这篇关于Clearcase:集成流合并(补丁)的活动依赖性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-14 20:50