deliver

The deliver operation creates a UCM activity called the integration activity, which records a change set for the deliver operation. The activity name is of the form deliver.stream-name.date-stamp. When the deliver operation begins, the integration activity becomes the current activity for the integration view in use.

You can deliver your work in one step by specifying the –complete and –force options. The –force option suppresses prompting for user input during the deliver operation. The –complete option causes the deliver operation to continue to completion after the merge phase. Use this feature carefully to avoid the possibility of delivering merged files that may not compile.

In a deliver operation, automatic merging is the default behavior for elements, unless user or never merge types were set for the elements. For information about setting merge behavior for an element type, see mkeltype.

For elements of the user merge type, you must invoke your own tool to merge from the source stream version to the integration view. The deliver operation checks out the elements, but you are responsible for merging and drawing merge arrows. Until merge arrows are drawn, the deliver operation will not proceed to the completion phase.

A deliver operation ignores versions from the source stream for elements of the never merge type. If all other versions are properly merged, the deliver operation can proceed to the completion phase. No merging or merge arrows are required.

UCM includes policies that you can set to affect the deliver operation. You can set policies at project or stream creation with mkproject or mkstream or at a later time with chproject or chstream. For information about project and stream policies, see the reference pages for mkproject and mkstream.

The deliver command determines whether the target stream and source stream are mastered at different replicas. If they are, a remote deliver operation is put into effect. The source stream is assigned a posted status.

In a remote deliver operation, the source stream must be a development stream. If you want to deliver changes from an integration stream, you can do so by delivering to a development stream on the same replica, and then delivering from the development stream to the remotely mastered stream.

After the stream is in the posted state, the deliver operation can be continued only by someone working at the target stream's replica. Generally, this is the team's project integrator. Also, after it is posted, the deliver operation can be canceled only by a user at the replica where the target stream resides.

The option –to integration-view-tag is not accepted when starting a remote deliver operation. The remote post goes to the default target stream or an alternative target stream, if specified. The deliver –status command reports on any remote deliver operation in progress for the specified stream. The project integrator can then cancel or continue the deliver operation, using the –cancel option to halt it, or the –resume or –complete options to continue it. The project integrator must specify the integration view for the deliver operation.

While the remote deliver is in progress, you can create activities and perform checkins and checkouts for your source stream, but you cannot perform any of these operations:

• Add, remove, or create baselines
• Add or remove components
• Rebase the source stream
• Post another deliver operation
• Receive changes (as the target stream of a local deliver operation) from a development stream

Delivering selected activities to a nondefault target is subject to the following restrictions:

• If the full set of activities in the stream violates one of the policy settings, you will not be allowed to proceed with the selected activity delivery, even if the selected activities would not violate the policies.
• If the full set of activities in the stream contains changes from a foundation baseline, you will not be allowed to deliver selected activities from this stream, regardless of the deliver policy settings.
• If the set of activities you want to deliver contain versions in components that are not visible in the target stream or are not modifiable by the target stream, you will not be allowed to deliver the set of activities. Delivering an activity requires that you deliver all versions in all components in the change set. You can move the versions of the missing or nonmodifiable components into another activity.

Default

Command line interface.

–graphical

Starts the graphical user interface for deliver.

Default

The default source is the stream attached to the current view. The default destination is the parent stream of the source stream. For an integration stream, the default destination is the default deliver target (if one is set), using either a view attached to the parent stream owned by the current user, or the view used by the last default deliver operation performed on the source stream.

–stre/am stream-selector

Specifies a stream that is the source for the deliver operation. The source stream cannot be a read-only stream.

stream-selector is of the form [stream:]stream-name[@vob-selector], where vob-selector specifies the stream's project VOB.

–to integration-view-tag

Specifies a view attached to the deliver target stream in the same project or in a different project. This option is not accepted for a remote-post deliver operation.

–to new-integration-view-tag

Resets the target view to a new integration view. Use this option should the target view become inaccessible.

–rmviewref

Removes references to the inaccessible view from every VOB in which the view is registered. This is equivalent to rmview –uuid. Errors result when you attempt to remove view references from VOBs that are inaccessible. However, if the command returns OK status, you can safely ignore such errors. Be cautious when using this option to avoid stranding checked out files.

Default

For development streams, the parent stream of the source stream. For integration streams, the default deliver stream set by mkstream or chstream.

–tar/get stream-selector

Specifies the deliver target stream in the same or a different project. The target stream cannot be a read-only stream.

Using –to integration-view-tag alone is sufficient to start a deliver operation to the target stream. If –to and –target are used together, the view must be attached to the stream. If one default view is attached to the target stream and owned by the user, using –target stream-selector alone can start a deliver operation. Otherwise, an integration view must be specified.

stream-selector is of the form [stream:]stream-name[@vob-selector], where vob-selector specifies the stream's project VOB.

Default

None.

–sta/tus

Displays the status of a deliver operation. You are informed whether a deliver operation for the specified stream is in progress, whether the delivery is to a local stream or a remote stream, and, in the case of a remote deliver, whether the posted changes have been merged with the target stream.

Default

None.

–can/cel

Halts a deliver operation in progress, returning the source and destination streams to their states before the deliver operation began. However, this option cannot undo a deliver operation after the completion phase has begun.

You can also use –cancel to cancel a delivery following an interrupt (as by Ctrl+C) or whenever the operation encounters an unexpected problem that would be easier to resolve by starting over.

–reset –to integration-view-tag

You must not remove the developer view when a deliver operation is in progress. However, if the integration view is lost during a deliver operation, you can use the –reset –to option to reset a new integration view so you would be able to cancel the operation. You can also use this option with –resume and –complete. Before you can reset a new integration view, the view-related records of the old integration view must be removed. UCM checks to see if the old view has any checkouts and if it has none, unsets the integration activity set in the view.

Default

For each activity to be delivered, displays the owner and activity-selector. For each baseline to be delivered, displays the owner and baseline-selector.

–pre/view

Shows activities or baselines that would be delivered if you were to execute the deliver operation for the specified stream. These are any activities or baselines that have changed since the last deliver operation from this stream. Use –preview only when no deliver operation is in progress for the stream.

Default

Varies according to the kind of output that the options described here modify. See the descriptions of –status and –preview.

–l/ong

As a modifier of –status or –preview, displays a list of versions that may require merging, in addition to the default information displayed by –status or –preview.

–s/hort

Modifies the –preview option. (This option does not modify the default –preview output.)

Default

Delivers all activities in the stream that have changed since the last deliver operation from the stream.

–cac/t

Delivers the activity currently set in the view. The operation fails if you are not in a view, have not set your view to an activity or the activity depends on the inclusion of any unspecified activities. For an explanation of activity dependence, see the section Selecting activities to deliver.

Default

Delivers all activities in the stream that have changed since the last deliver operation from the stream.

–act/ivities activity-selector, ...

Specifies a list of activities to deliver. The list must be self-consistent: the activities specified must not depend on the inclusion of any unspecified activities. For example, activity A2 is dependent on activity A1 if both contain versions of the same element and A2 contains a later version than does A1.

In addition, any activities that have been included in baselines but not delivered must also be delivered if changes for that component are in the specified activities. If the list of activities you specify is incomplete, the operation fails and lists the additional required activities.

activity-selector is of the form [activity:]activity-name[@vob-selector] where vob-selector specifies the activity's project VOB.

Default

Delivers all activities in the stream that have changed since the last deliver operation from the stream.

–bas/elines baseline-selector, ...

Specifies a list of baselines to deliver. The baselines must be created in the source stream or from the source stream's foundation. A development stream can deliver activities or baselines, but an integration stream can deliver only baselines.

Default

None.

–res/ume

Resumes a deliver operation from the point at which it was suspended.

Default

None.

–com/plete

Completes a deliver operation. Verifies that changes being delivered have been merged with versions in the deliver target stream and that merge conflicts have been resolved. Checks in resulting new versions to the target stream and records that the deliver operation has been made. If merge conflicts exist, the deliver operation is suspended.

Use this option to complete a deliver operation or to resume a suspended deliver operation. To complete a deliver operation, you must specify this option; checking in merged versions to the integration view alone does not complete the deliver operation.

When used for a deliver operation in progress, this option implies the –resume option; that is, deliver –complete reports any merges that are still required and attempts to resolve them.

Default

Merging works as automatically as possible, prompting you to make a choice when two or more contributors differ from the base contributor. For general information, see the findmerge reference page.

–gm/erge

Performs a graphical merge for each element that requires it. This option does not remain in effect after a deliver operation is interrupted.

–ok

Pauses for verification on each element to be merged, allowing you to process some elements and skip others. This option does not remain in effect after a deliver operation is interrupted.

–q/uery

Prompts you for confirmation before proceeding with each change in the from-versions. Changes in the to-version are automatically accepted unless a conflict exists. This option does not remain in effect after a deliver operation is interrupted.

–abo/rt

Cancels a merge if it is not completely automatic. This option does not remain in effect after a deliver operation is interrupted.

–qal/l

Turns off all automated merging. Prompts you for confirmation before proceeding with each change. This option does not remain in effect after a deliver operation is interrupted.

–qnt/rivial

Turns off automated merging and prompts you to determine whether you want to proceed except in the case where a trivial merge would be done. This option does not remain in effect after a deliver operation is interrupted.

–ser/ial

Uses a serial format to report differences among files. Differences are presented in a line-by-line comparison with each line from one contributor, instead of in a side-by-side format. This option does not remain in effect after a deliver operation is interrupted.

Default

Prompts for user input.

–f/orce

Suppresses prompting for user input during the course of a deliver operation. The –force option does not remain in effect if the deliver operation is interrupted. You must include it again on the command line when you restart the deliver operation with –resume or –complete. The merge options for deliver are not affected by the –force option.