Clearcase UCM中的完全基准和增量基准有什么区别? [英] What is the difference between Full baseline and Incremental baseline in Clearcase UCM?

查看:84
本文介绍了Clearcase UCM中的完全基准和增量基准有什么区别?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已为发布应用了完整的基准。对于前。基线 MYProj_2.0.0.20。

I have applied full baseline for my release. for ex. Baseline "MYProj_2.0.0.20".

然后测试团队发现了一些主要问题。为了修复该开发团队所做的少量更改。

Then testing team found some major issue. To fix that development team has delivered few changes.

完成构建后,我再次应用了相同的基准 MYProj_2.0.0.20。但是这次我已经应用了增量基线:根据UCM,基线MYProj_2.0.0.20变为MYProj_2.0.0.20.3452(末尾有一些随机数,使其变得唯一)。

After completing the build , I have applied the same baseline again "MYProj_2.0.0.20. But this time i have applied Incremental baseline. As per UCM, the baseline MYProj_2.0.0.20 was turned as MYProj_2.0.0.20.3452 (some random number at end to made it unique).

现在如果我将MYProj_2.0.0.20.3452视为发布基准,它将包含所有更改还是仅包含更改( MYProj_2.0.0.20和 MYProj_2.0.0.20.3452之间的增量更改)。

Now If i consider MYProj_2.0.0.20.3452 as release baseline, Will it contain all the changes or only the changes (delta change between "MYProj_2.0.0.20" and "MYProj_2.0.0.20.3452").

请澄清一下。

推荐答案

它将包含所有更改。

除了增量基线,这些基线的变化将通过添加以下内容来计算:

Except an incremental baselines will compute those changes by adding:


  • 唯一修改由少量更改(即增量基准是指:仅在自上一个基准以来的新版本上设置的标签)引入的

  • 先前已引用的所有其他更改s基线直到完整基线

请参见 基线类型



  • 完整基准是通过记录组件根目录下所有元素的所有版本而创建的基准。

  • 增量基线是您通过记录上一个完整基线以及自上一个完整基线创建以来已更改的元素版本所创建的基线。

  • A full baseline is a baseline that you create by recording all versions of all elements below the component's root directory.
  • An incremental baseline is a baseline that you create by recording the last full baseline and those versions of elements that have changed since the last full baseline was created.

(还有 检查点基线,如 关于ClearCase基准 ,由以下人员自动创建交付和变基操作,但您不必担心

这就是为什么我总是更喜欢完整的基线:如果您的最后一个基线是一个基线,则所有增量操作(例如与另一个基线进行比较)都更快。

支持增量基线的论点是它们创建起来更快(因为放置基线的版本较少)。

但是,如果您的UCM组件太大,以至于在所有版本的 all 上贴上标签太长,也许您的组件首先太大了。

That is why I always prefer a full baseline: all delta operation (like a "compare with another baseline") are quicker if your last baseline is a full one.
The argument in favor of incremental baselines is that they are faster to create (because of the lesser number of version to put baseline on).
But if your UCM component is so large that putting a label on all its versions is too long, maybe your component is too big in the first place.

请注意,您始终可以将增量基准升级到完整基准。

Note that you always can upgrade an incremental baseline to a full baseline.

请注意,您之间还有区别:

Note also that you have a difference between:


  • 基线的标题(此处为 MYProj_2.0.0.20 :您可以输入尽可能多的 MYProj_2.0.0.20 基线

  • 基线的ID(始终唯一:如果 MYProj_2.0.0.20 已被使用,然后ClearCase在末尾生成一些数字: MYPro j_2.0.0.20.345 2)

  • the title of a baseline (here "MYProj_2.0.0.20": you can put as many "MYProj_2.0.0.20" baselines as you want)
  • the id of a baseline (always unique: if "MYProj_2.0.0.20" is already taken, then ClearCase generate some numbers at the end: "MYProj_2.0.0.20.3452")

这篇关于Clearcase UCM中的完全基准和增量基准有什么区别?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆