5.7 MultiSite: Posting Work to Deliver

If your organization uses ClearCase MultiSite to distribute development among multiple geographical sites, your project may share source files with developers at other sites. Each site has its own replica of project components, and developers work in site-specific replicas. Each replica controls (masters) a set of streams, and only developers at that replica's site can modify them.

If your site does not master a stream, you cannot complete deliver operations to that stream. UCM provides a variation of the deliver operation called a remote deliver. You must post your work to deliver. If the target stream is mastered by the local PVOB replica, the deliver operation is local.

After you deliver your work and the delivery is in the posted state, the project integrator at the site that masters the target stream completes the remote deliver operation.

To Deliver to a Nonmastered Target Stream

To make your work on a remote stream available in the target stream:

1. Prepare your work areas (see Preparing Your Work Areas).

2. Start the deliver operation (see Starting the Deliver Operation).

In a remote deliver operation, the source stream must be a development stream.

3. Select activities (see Selecting Activities).

4. Deliver the work so that it can be posted.

The deliver operation determines whether your development and target streams are mastered at different replicas. If they are mastered at different replicas, a remote deliver operation is put into effect. ClearCase changes mastership of the development stream object to match that of the target stream object, and it notifies you that it has assigned the development stream the posted status.

When your development stream has the posted status, notify the project integrator at the site that masters the target stream's replica. The project integrator can then find posted deliver operations and either continue the operation or cancel it to return the development stream to its previous state. Note that, after you post your work, only someone at the master site can cancel or complete the operation.

You can create activities and perform checkins and checkouts for your development stream while the remote deliver is in process. However, you cannot add, remove, or create baselines; add or remove components; or rebase the development stream. The delivery completes when the posted deliver operation is merged with the target stream.

Remote Deliveries with the UCM-ClearQuest Integration

In a project that uses the UCM-ClearQuest integration, the project manager may set the Do ClearQuest Action After Delivery policy on a project (see Deliveries and the UCM-ClearQuest Integration). This policy transitions activities in ClearQuest to a Complete state when the deliver operation completes successfully. For this policy to work in a MultiSite environment, all activities being delivered must be mastered by the same PVOB replica that masters the target stream.

In a MultiSite environment that uses the UCM-ClearQuest integration, the project manager sets the Check Mastership Before Delivery policy on a project to have the software check the mastership of all activities being delivered. If the deliver operation is local and all activities being delivered are not mastered locally, the deliver operation fails.

For a remote deliver operation, the Check Mastership Before Delivery policy causes the following behavior:

• If all activities are mastered by the remote replica, the deliver operation proceeds.

• If the deliver operation contains activities that are mastered by the local replica, MultiSite transfers mastership of those activities to the remote replica. After the project integrator at the remote site completes the deliver operation, MultiSite transfers mastership of the activities back to the local replica.

• If the deliver operations contains activities that are mastered by a third replica, the deliver operation fails.