Rational ClearCase 中的活动

发布于 2024-08-27 19:17:03 字数 336 浏览 12 评论 0 原文

我们正在考虑实施 Rational ClearQuest 来进行变更管理和缺陷跟踪。当我们集成 Rational ClearQuest 和 Rational ClearCase 时，活动将来自 Rational ClearQuest。

现在，由于 Rational ClearQuest 的实施由于流程的原因需要一些时间，因此我们正在考虑从开发人员方面删除活动创建。我们正在考虑让管理员为每个开发人员创建活动。

现在我有一些担忧，如果管理员创建活动并使用保护命令更改活动和组的所有者，是否足够？其他开发者也会使用此活动吗？既然活动是一项工作，那么它可以共享吗？

我需要澄清这一点。

谢谢。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

最近可好 2024-09-03 19:17:03

我不记得在使用 ClearQuest 时必须以某种方式以特殊权限保护 UCM 活动创建（我们现在不再使用它）

IBM 文章“关于在为 Rational ClearQuest 启用的项目中创建 UCM 活动< /a>”总结了活动创建过程：用户“从事 (ClearQuest) 活动”

在视图所附加的流中创建一个活动对象。

活动对象链接到 Rational ClearQuest 用户数据库中的记录，该数据库的记录类型已为 UCM 启用。

Rational ClearCase 活动的名称设置为与 Rational ClearQuest 记录的 ID 匹配。

您不直接创建 UCM 活动对象。

由于 ClearCase UCM 活动的创建是由 ClearQuest 管理的，因此您不需要：

自己创建一些 UCM 活动
尝试由特殊所有者保护这些活动。

您应该使用一些策略，例如 WorkOn 政策：

当开发人员尝试设置活动时，将调用此策略。
默认策略脚本会检查开发人员的用户名是否与 Rational® ClearQuest® 记录所有者字段中的名称相匹配。
如果名称匹配，开发人员就可以处理该活动。如果名称不匹配，WorkOn 将失败。

此政策的目的是确保开发人员在开始开展活动之前满足所有标准。您可能需要修改策略以检查其他条件。

文章“关于为 UCM 启用的 Rational ClearCase 活动和记录类型”详细介绍了两个概念（UCM 活动和 ClearQuest 记录类型）之间的链接

在使用 UCM 与 Rational ClearQuest 集成的项目中，基于为 UCM 启用的记录类型的记录可以与 Rational ClearCase 活动对象链接

替代文本 http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0 /topic/com.ibm.rational.clearcase.hlp.doc/cc_main/images/cq_pvob_map.gif

此链接使 Rational ClearQuest 客户端能够显示有关 Rational ClearCase 活动的信息（例如其更改集、其流以及当前是否在任何视图中设置）。
该链接还启用策略来管理您何时可以在 Rational ClearCase 环境中交付活动以及何时可以在 Rational ClearQuest 环境中关闭活动。
由于链接的支持 UCM 的记录和 Rational ClearCase 活动之间的密切关联，UCM 文档通常将这两个实体称为活动。

在项目中的任何一点，您的 Rational ClearQuest 用户数据库可能包含未链接到 Rational ClearCase 活动对象的记录，但具有为 UCM 启用的记录类型。
例如，新创建的记录可能不会链接到 Rational ClearCase 活动。您必须明确完成一项操作（例如，通过单击Action > Work On）才能将此类记录链接到 UCM 活动。

但是，为 Rational ClearQuest 启用的项目中的每个 Rational ClearCase 活动对象都必须链接到 Rational ClearQuest 记录。
如果不将 Rational ClearCase 活动对象链接到 Rational ClearQuest 用户数据库中的记录，则无法创建它。

提示：在为 Rational ClearQuest 启用的项目中，包含一个字段来描述活动所有者。 Rational ClearQuest 所有者字段和 Rational ClearCase 活动创建者是两个不同的数据点；前者存储在 Rational ClearQuest 用户数据库中，后者存储在 Rational ClearCase PVOB 中。

I don't remember having had to protect somehow UCM activity creation with special priviledge when using ClearQuest (we are no longer using it right now)

The IBM article "About creating UCM activities in a project enabled for Rational ClearQuest" summarizes the activity creation process: a user "work on a (ClearQuest) activity"

An activity object is created in the stream to which the view is attached.

The activity object is linked to the record in the Rational ClearQuest user database whose record type is enabled for UCM.

The name of the Rational ClearCase activity is set to match the Rational ClearQuest record's ID.

You do not create UCM activity objects directly.

Since the creation of ClearCase UCM activities is managed by ClearQuest, you don't need to:

create yourself some UCM activities
try protect those by a specal owner.

You should rather use some policies like the WorkOn policy:

This policy is invoked when a developer attempts to set an activity.
The default policy script checks whether the developer’s user name matches the name in the Rational® ClearQuest® record Owner field.
If the names match, the developer can work on the activity. If the names do not match, the WorkOn fails.

The intent of this policy is to ensure that all criteria are met before a developer can start working on an activity. You may want to modify the policy to check for additional criteria.

The article "About Rational ClearCase activities and record types enabled for UCM" details the link between the two notions (UCM activities and ClearQuest record type)

In a project that uses the UCM integration with Rational ClearQuest, records based on a record type enabled for UCM can be linked with Rational ClearCase activity objects

alt text http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0/topic/com.ibm.rational.clearcase.hlp.doc/cc_main/images/cq_pvob_map.gif

This link enables the Rational ClearQuest client to display information about the Rational ClearCase activity (such as its change set, its stream, and whether it is currently set in any view).
The link also enables policies governing when you can deliver an activity in the Rational ClearCase environment and when you can close an activity in the Rational ClearQuest environment.
Because of the close association between linked UCM-enabled records and Rational ClearCase activities, the UCM documentation usually refers to both entities as activities.

At any point in a project, your Rational ClearQuest user database may contain records that are not linked to a Rational ClearCase activity object, but have a record type that is enabled for UCM.
For example, a newly created record might not be linked to a Rational ClearCase activity. You must explicitly complete an action (for example, by clicking Action > Work On) to link such a record to a UCM activity.

However, each Rational ClearCase activity object in a project enabled for Rational ClearQuest must be linked to a Rational ClearQuest record.
You cannot create a Rational ClearCase activity object without linking it to a record in a Rational ClearQuest user database.

Tip: In a project enabled for Rational ClearQuest, a field is included to describe the activity owner. The Rational ClearQuest owner field and the Rational ClearCase activity creator are two different data points; the former is stored in a Rational ClearQuest user database and the latter in a Rational ClearCase PVOB.