没有VOB(Clearcase UCM)的组件有什么用途? [英] What is the use of component without VOB (Clearcase UCM)?

查看:94
本文介绍了没有VOB(Clearcase UCM)的组件有什么用途?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我被告知要在UCM中创建组件。

I was told to create component in UCM.

您如何向初学者解释组件和VOB之间的区别?

How would you explain a difference between component and VOB to a beginner?

还要求两个选择。

VOB中的组件和没有VOB的组件。

Components in VOB and Components without VOB.

拥有不带VOB的组件有什么用?

What is the use of having Component without VOB?

推荐答案

您总是有一个与组件有关的Vob。

Vob是数据库(文件-基于数据库的数据库,而不是基于SQL的数据库,其中包含所有元素(文件和目录)的所有版本。
不要与PVob混合使用,PVob是一种仅包含UCM元数据的特殊Vob类型(例如UCM项目,流,组件名称,活动等的列表。)

You always have a Vob involved with a Component.
A Vob is the database (file-based database, not an SQL-based) containing all versions of all elements (files and directories).
Not to be mixed with a PVob, which is a special kind of Vob containing only UCM metadata (like the list of UCM projects, streams, components names, activities, ...).

您有两种组件,但是每个组件都是一组连贯的文件:

You have two kinds of components, but each one is a coherent set of files:


  • Vob组件:全部Vob是一个组件。

  • 基于根的组件:该组件具有它的根位于Vob的第一目录级别 \aVob\aRoot

  • Vob component: the all Vob is a component.
  • Root-based components: the component has its root in the first directory level of a Vob: \aVob\aRoot.

最好创建基于根的组件(即,每个Vob包含多个组件),因为要创建的每个Vob都意味着多个进程来对其进行管理( vob_server vob_rpc ),它很快就会占用大量资源。

但是,Vob中的几个组成部分(甚至一百个)都不成问题。

It is best to create root-based components (ie, several components per Vob), because each Vob you would create means several processes to manage it (vob_server, vob_rpc), and it becomes quite resource intensive quickly.
However, several components (even an hundred) within a Vob is not a problem.

但这意味着您的Vob名称必须通用到足以容纳您的组件。

But that means the name of your Vob must be "generic" enough to accommodate your components.

对于无根组件(具有PVob,但没有Vob),请参见 关于植根和无根的ClearCase UCM组件

As for rootless components (with a PVob, but no Vob), see "About rooted and rootless ClearCase UCM components".


无根组件:

Rootless Components:


  • 在UCM环境中绝对不可修改。

  • 不与数据存储相关(无Vob)

  • 用于跟踪其他组件中的更改。

  • 可以包含依赖项列表,也称为(复合基线结构)

  • 使用没有相应标签类型的基线进行跟踪。

  • should NEVER be modifiable in a UCM environment.
  • are not associated with a data storage (vob-less)
  • are used to track changes from Other Components.
  • can contain dependency lists also known as a (Composite baseline Structure)
  • are tracked with baselines that have NO corresponding label type.

无根组件仅应用于跟踪有根组件的进度s。

当需要根组件依赖时,应使用无根组件基线。依赖关系是严格的,一旦实现就可以执行严格的流程。

Rootless Components should only be used to track the progress of Rooted Components.
Rootless component baselines should be used when rooted component dependencies are needed. The dependencies are rigid and can enforce a strict process once implemented.

请参见 创建复合基线以查看运行中的无根组件。

See "To create a composite baseline" to see a rootless component in action.

这篇关于没有VOB(Clearcase UCM)的组件有什么用途?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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