User Guide - MKS

Key Apply CP
Concepts
How Apply CP
Works
Using the Apply CP Command
The following outlines the key concepts associated with the Apply CP
command:
The Apply CP operation occurs in the project (whereas the Resync CP
operation occurs only in the sandbox). You can perform the Apply CP
operation from a sandbox, but this only acts as a redirector to the
project.
In principle, change packages are applied through a revision process.
By applying a change package, you can incorporate only those
changes that you want to include in the project.
Apply CP cannot address changes that require merging. Apply CP can
only make changes based on complete files—it can only add files,
drop files, and update a file revision. For more information on
resolving merge questions, see “Using the Resync CP Command” on
page 375.
Apply CP only works with closed change packages; therefore, you
must close the change package before you apply it. The Apply CP
operation is committing changes directly to a project and, for this
reason, it is important that the entire change package is treated as a
single, indivisible change. If a change package is not closed, it may not
stand alone and may break the build.
Source Integrity 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 an Apply CP operation is not successfully completed,
Source Integrity tells you what you need to do to apply the change
package successfully.
The Apply CP backfill list presents you with all the change packages
that the selected change packages depend on. To run the command,
you must accept the entire list.
The Apply CP operation adds and drops files, and updates file revisions to
include specific content in a project. For example, consider a simplified
application of the command in the main trunk of development for the
Aurora project (Aurora_Project.pj). The project member, main.c,
includes a bug fix that allows the printing of version information. Issue 21
addresses the bug fix and is associated with the file main.c (revision 1.2)
through change package (CP) 21:1.
The buildmaster wants to pick up the changes that address the bug fix and
apply these to a variant project, Aurora_Variant_1_0. In the variant
project, main.c is at revision 1.1.
357