Resync CP Overview

You use the Resync CP command to preview the changes listed in change packages in the context of a sandbox before propagating them to the project. The Resync CP command searches all files related to a selected change package and all change packages that are possibly associated with the related files. The Resync CP command is most useful for incorporating new software features or bug fixes during the software development process.

The Resync CP command provides additional options beyond those available for the Apply CP command. For example, options exist for allowing open change packages, merging, resolving conflicts, and continuing the resync operation when errors are encountered. Integrity Lifecycle Manager allows you to run the Apply CP command first and then, if required, run the Resync CP command to perform any required merge operations.

• If you attempt to use the Resync CP command on a member that was previously dropped from a project, Integrity Lifecycle Manager instructs you to manually re-add the member.

• When using the Resync CP command to propagate changes to an extendable development path, the development path is automatically extended to subprojects that are to be modified. For more information, see Extending an Extendable Development Path. This automatic extension occurs at the beginning of the Resync CP operation. If you cancel the operation, the extendable development path is not reverted to its previous unextended state. For subprojects configured as variant or normal in the base checkpoint of the development path, creation of the extendable development path freezes those subprojects to the checkpoint contents. Development path extension restores the live content, so those subprojects are typically extended immediately after extendable development path creation. If the live version of those subprojects is no longer the desired behavior, you can manually configure the subproject back to the desired build.

• Assume that subproject sub/project.pj and a shared subproject pointing to subproject sub/project.pj share the same parent. A change is then performed on one of the subprojects in a change package on a full development path. When performing the Resync CP operation onto an extendable development path, the operation is executed on either subproject or the shared subproject, and that subproject is automatically extended. The extended subproject is not necessarily the one mentioned in the change package. However, you can manually extend the other subproject so that the propagated change is present in that subproject.