ClearCase UCM层次结构

本文介绍了ClearCase UCM层次结构的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述 我试图了解UCM对象的层次结构：UCM项目，流，基线，复合基线，VOB组件，活动，变更集等。您能解释这些对象之间的层次结构链接吗？您能否提供一个链接，以提供良好的解释？ 视觉图表也将很好I'm trying to understand the hierarchy of UCM objects: UCM project, streams, baselines, composite baselines, VOB components, activities, change sets etc.Can you explain the hierarchy links between these objects? Can you provide a link to a good explanation?A visual diagram will be good as well谢谢！推荐答案 UCM项目是UCM流的容器。 它包含至少一个根流（称为集成流）和几个子流。 有关更多信息，请参见 ClearCase中的集成流与集成视图。An UCM project is a container forn UCM Streams.It contains at least one root stream (called "integration stream"), and several sub-streams.See "Integration stream vs integration view in ClearCase" for more. UCM流是开发工作的表示，即共享的一种方式：-您想做什么（流的名称）-您需要执行的操作（配置或每个组件的基准列表）An UCM Stream is the representation of a "development effort", ie a way to share: - what you want to do (name of the Stream) - what you need to do it ("configuration" or list of Baselines for each Components)基准是某个组件的固定版本：所有文件A Baseline is a fixed version for a Component: all the files of a Component are labelled with the same label attached ot a Baseline.一个Component是一组连贯的文件（即使仅修改一个文件，也要分支或标记该文件）。全部设置）。A Component is a coherent set of file (even if you modify only one, you branch or label the all set).您可以拥有 com组件的元素，将触发创建复合基线： 请参阅 UCM中的复合基线是什么以及何时使用？了解更多。You can have "component of components", which will trigger the creation of composite baselines:See "What is composite baseline in UCM and when it will be used?" for more.活动是您在给定Stream中为给定组件修改的版本的列表。 请参阅 Clearcase：集成流合并（补丁）的活动依赖性。An activity is the list of versions you have modify for a given component, within a given Stream.See "Clearcase: Activity dependencies for integration stream merging (patches)" for more.请参阅 UCM项目中的数据流方式 这篇关于ClearCase UCM层次结构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！