问题描述
我了解的是，
PVOB 是VOB的一种特殊类型，当将UCM作为软件配置管理过程实现为
时使用。 em>
What I understand is that, PVOB is a special type of VOB that is used when UCM isimplemented as the software configuration management process.
但是我怀疑与VOB有什么不同？我是CC新手，但据我所知，甚至PVOB都包含与VOB相同的信息。
But my doubt is how is it different from VOB? I am new to CC but, as far as I know, even PVOB contains the same information as VOB.
有人可以向我解释吗？
Can anyone explain me?
推荐答案
PVob就像一个VOB，它可以 版本文件和文件夹。
PVob is like a vob in that it can version files and folders.
但是按照惯例，您不使用pvob来添加到源代码管理。
But by convention, you don't use a pvob to "add to source control".
您将PVob用作 admin vob，一个经典的Vob，以便在其中声明组件，并管理与UCM相关的所有matadata：
You use a PVob as a "admin vob" for a classic Vob in order to declare component(s) in it, and to manage all the matadata associated to UCM:
- Projects
- 流
- 活动
- 合并超链接以进行交付和变基
- Projects
- Streams
- Activity
- Merge Hyperlinks for deliver and rebase
在这种情况下，正如我在所示，PVob在ClearCase 项目资源管理器，而不是ClearCase资源管理器。
In that case, as I mentioned here, PVob are visible in the ClearCase project Explorer, not the ClearCase Explorer.
与任何 AdminVob一样，pvob管理关联的vob的数据类型：请参见 。
简单来说，一个pvob还将管理 UCM 类型，从而使所有相关的UCM清单（包含以下内容）的项目，流和活动可见实际数据）。
As any "AdminVob", a pvob manages datatypes for the associated vobs: see "VOB datatypes and administrative VOB hierarchies".
Simply, a pvob will manage UCM types as well, making projects, streams and activities visibles for all the associated UCM vobs (which contain the actual data).
您实际上可以将pvob分组为hi层次结构，如 。
You can actually group pvob in a hierarchy, as explained in "Multiple PVOBs and a common administrative VOB".
在图1中，PVOB1和PVOB2的使用将PVOB3作为其管理VOB。
In Figure 1, PVOB1 and PVOB2 use PVOB3 as their administrative VOB.
这篇关于VOB和PVOB有什么区别？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！