Revert CP Overview

You can use the Revert CP command to revert changes made by the entries in a specified change package. This command reverts the changes by performing new changes, which may result in new revisions of members. Even though the changes are reverted, they still appear in the history where applicable.

The Revert CP command does not perform a revert operation for every type of entry in the specified change package. The following entry types are supported:

• Add (results in a pending Drop operation)

• Drop (results in a pending Add operation)

• Update (results in the need for a merge)

• Update Revision (results in the need for a merge)

• Add From Archive (results in a pending Drop operation)

Even if an entry type is supported, there may be legitimate reasons why the changes needed to revert the entry could not occur (such as insufficient permissions assigned to you). If Integrity Lifecycle Manager cannot perform the changes needed to revert an entry, the information is reported to you after the command completes. You can use that information to manually make the needed changes where possible.

• This command only reverts a single closed change package.

• A propagation change package is required, to record the operations needed to revert the change package.

• This command requires a sandbox context to perform the operations needed to revert the change package.

• You may need to manually revert some of the changes yourself. The command returns a list of change package operations that could not be reverted.

• If the merges are for revisions on the same member in the same sandbox (contiguous merges), they are collapsed into one operation.

• For reverting a change package that contains an update revision, if the revision of the member being updated to in a change package is the same or later in the current project configuration, the result is a merge of the differences out of the working file. If the revision in the change package is earlier in the member history than the member revision of the current project configuration, then the result is a merge in instead of merge out. For example, if the change package has an update revision to 1.1, the revision of the member in the project is 1.3, the result is a merge in the member history. If the change package has an update revision to 1.2 and the revision of the member in the project was 1.2 (or 1.1) the result is a merge out in the member history.

• The Revert CP command does not implicitly extend subprojects in an extendable development path. Before using this command, you must manually extend the extendable development path to the appropriate subprojects. For more information, see Extending an Extendable Development Path.