You can achieve tight coordination of your organization’s configuration management and issue management capabilities by enabling one or both of the integrations between AccuRev’s configuration management and issue management facilities. The transaction-level integration is enabled by a trigger on a depot-by-depot basis:The “client_dispatch_promote” integration routine is built into the AccuRev software — no scripts are required — and includes both pre-operation and post-operation components:
1. On the client machine, a user invokes the AccuRev promote command.
2. The pre-operation part of the trigger fires on the client machine, prompting the user to specify one or more AccuWork issue records (SPACE-separated). If this part of the trigger fails (e.g. the user specifies a non-existent issue record), the promote command itself is cancelled.
3. The promote command completes, and is recorded in the AccuRev repository as a transaction.
4. The post-operation part of the trigger fires on the server machine, updating the issue record that the user specified by adding the number of the promote transaction to the affectedFiles field.If you use the built-in “client_dispatch_promote” integration routine as the pre-promote-trig trigger, you must not also set a server-post-promote-trig trigger. Doing so would suppress the post-operation component of the “client_dispatch_promote” routine.For information on handling this situation and other aspects of customizing the transaction-level integration, see Implementation and Customization of the Transaction-Level Integration on page 98. (This section also describes another integration between configuration management and issue management, which works at the change-package level instead of the transaction level.)Note: the purge command (GUI command Revert to Backed) also triggers this integration, because it is uses the depot’s pre-promote-trig trigger capability.
AccuRev, Inc. |
Phone: 781-861-8700 |
Fax: 781-861-8704 |
support@accurev.com |