Why does Clearcase diffbl include activities from my development stream when I diff integration stream baselines?

混江龙づ霸主 提交于 2019-12-06 06:50:27
VonC

Note: in the integration stream, you will mostly get deliver activities, ie activities recording the merges done during delivers from the development stream.

So if you want activities from two baselines done on the integration Stream, a simple

cleartool diffbl -nmerge -act bl1 bl2

should be enough.
If you somehow see activities from the development stream, that should mean you are comparing bl1 from integration stream with bl2 from a development stream or two baselines from integration with merges, ie with contributing activities.

Hence the –nmerge

Compares two baselines on the same stream and reports only activity and version changes made on that stream.


To illustrate why you see those activities without the -nmerge, see "List the contributing activities in the change set of a baseline or an integration activity"

An activity from the integration Stream will look like this:

Integration activities track work completed as a result of a deliver or rebase operation, and they are named accordingly with a prefix of either deliver or rebase to help distinguish them from user created activities.

If you right-click the activity and select Show Contributing Activities, you will see:

Which is the same than:

 cleartool lsactivity -contrib <deliver baseline>@\pvob

or

 cleartool lsact -fmt "%[contrib_acts]p" <deliver baseline>@\pvob

Again, the -nmerge option avoids the diffbl to list those contributing activities.

Tamir Gefen

That's because the contributing activities that come from child streams... Try

diffbl -nmerge

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!