Setting policies and installing triggers in a DevOps Code ClearCase VOB
Before developers can associate DevOps Code ClearCase® versions
with Rational®
ClearQuest® change
requests, you need to configure DevOps Code ClearCase as
follows:
- Using the Rational ClearQuest Integration Configuration tool, for each VOB, set policies that determine the conditions under which developers are prompted to associate versions with change requests. You can specify that developers are prompted on checking out a version, checking in a version, or both. You can also specify that prompting occurs only for some branch types or element types. Associations of checked-in versions with change requests can be either optional or required.
- Using the Rational ClearQuest Integration Configuration tool, select the trigger type that is to be used. If you use the V2-Perl trigger, you need to modify a configuration file to set database connectivity information and additional policy parameters.
The base ClearCase integration with Rational ClearQuest uses DevOps Code ClearCase element triggers on cleartool checkin (preoperation and postoperation), checkout (postoperation), and uncheckout (preoperation) commands to allow developers to associate versions with Rational ClearQuest change requests.