When project managers implement project policies with Rational ClearCase® triggers, users may be prompted
to provide additional information or take further action with certain
Rational ClearCase operations.
A project manager can use ClearCase triggers to control
the behavior of Rational ClearCase commands by arranging
for a specific program or executable script to run before or after
the command runs. Virtually any command that modifies an element can
run a trigger.
Although you cannot create a ClearCase trigger
from the IBM Rational® ClearTeam Explorer™, you might need to respond
to a trigger's prompt by supplying additional information or taking
further action with certain Rational ClearCase operations.
There are two general categories of ClearCase triggers:
- Preoperation triggers fire before the designated ClearCase command
is executed. For example, preoperation trigger on checkin can prompt
you to add an appropriate comment.
- Postoperation triggers fire after a ClearCase operation
has completed and can take advantage of the operation's completion
status. For example, a postoperation trigger on checkin can send an
e-mail message indicating that a particular developer modified a particular
element.
Triggers can also automate a variety of process management functions.
For example:
- Applying attributes or attaching labels to objects when they are
modified
- Logging information that is not included in the Rational ClearCase event records
- Initiating a build or source code analysis whenever particular
objects are modified
Note: In some instances, a trigger may perform an operation and you
may see not evidence of the trigger firing or performing the operation.
In other instances, you may see a display that differs from command
to command or from VOB to VOB.