The base ClearCase integration with Rational ClearQuest

In the Rational® ClearQuest® environment, change requests record defects or request modifications for a project or product. In the DevOps Code ClearCase® environment, versions of the elements that represent a project or product are managed. Each version embodies one or more changes to an element.

With the base ClearCase integration with Rational ClearQuest, one or more change requests are associated with one or more versions. These associations enable a project manager to correlate versions in one environment with project or product information in the other environment. A single change request can be associated with more than one version. The set of versions that implement the requested change is called the change set for that request.

A single version can be associated with more than one change request. These change requests are called the request set for that version.

Using the integration

The integration has the following interfaces:

  • As a DevOps Code ClearCase user, you can associate a version with one or more change requests at the time you check in or check out the version.
  • As a Rational ClearQuest user, you can view the change set for a request.
  • As a DevOps Code ClearCase user, you can submit queries to identify the change requests that are associated with a project over a period of time.
  • As a Rational ClearQuest administrator or schema designer, you can add DevOps Code ClearCase definitions to a Rational ClearQuest schema. These definitions enable change requests in databases that use the schema to contain and display associated change sets.
  • As a DevOps Code ClearCase administrator, you use the Integration Configuration tool to specify the conditions under which developers are prompted to associate versions with change requests. You can specify VOBs, branches, and element types for which developers can or must associate change requests.
  • As a DevOps Code ClearCase administrator, you can use the Integration Query Wizard on Windows systems to identify the change requests that are associated with a project over a period of time.

Using the Integration Configuration tool

The base DevOps Code ClearCase Integration Configuration tool on Windows systems displays a window in which you perform the following configuration steps:

  • Select a VOB to be enabled for the integration.
  • For the VOB, set policies that determine the conditions under which developers are prompted to make associations.
  • Select the trigger type to be used.

    If you select V2-Perl as the trigger type, you can use triggers defined in a central location rather than copies on all the client systems.

  • Specify the record type in the user database. Records of this type contain the change set information.

If you select V2-Perl as the trigger type, after you exit the configuration tool, you need to modify a configuration file (config.pl) to set database connectivity information and additional policy parameters.