ClearCase® GitViews: Merge operations, CMI integration, and Interactive triggers

Merging

ClearCase GitViews use ClearCase UCM mechanisms for merge operations. Changes are merged using deliver and rebase operations initiated from the ClearCase GitView web interface. Client-side Git merges are not used to integrate changes into ClearCase. Developers must ensure that changes are committed to the Git master or main branch before performing deliver operations.

Change Management Integration (CMI)

ClearCase supports Change Management Integration (CMI), which can require tasks to be associated with ClearCase UCM activities before work can be performed. During a Git push operation, a ClearCase activity is automatically created to perform the required ClearCase operations.

If tasks are mandatory on the development stream, a Git pre-receive hook blocks the push operation unless one or more tasks are associated with the stream. To associate a task, the ClearCase GitView web interface allows users to select a task prior to initiating the Git push operation.

Interactive Triggers and Scripts

ClearCase provides a configurable trigger mechanism to enforce custom behaviors during ClearCase operations. These triggers can invoke customer-defined scripts, some of which may require user interaction.

To ensure compatibility with ClearCase GitViews, interactive triggers must use cleartool or clearprompt. ClearCase operations initiated from the GitView web interface, including deliver and rebase, pass interactive prompts to the user and wait for a response before continuing or aborting the operation.

If an interactive prompt is detected during a Git push operation, the ClearCase backend operations are aborted, and a warning message is displayed indicating that manual intervention is required.