User Guide - MKS

Apply CP Backfill Options
Using the Apply CP Command
The Apply CP command operates recursively. To apply a change package,
Source Integrity searches the specified change packages for revision
changes between the current revision and the target revision.
Backfill
Option (GUI)
Entire Change
Packages
Back
Revisions Only
Backfill
Option (CLI)
Function
cp Selected by default for the Apply CP
command. Recursively finds all historic
revisions required by the specified change
packages and applies them. It does not ask
the user to confirm the backfill list.
revision Processes only the changes in the specified
change package(s). Any change packages
associated with intermediate revisions are
not picked up.
Note: Processing by revision reduces the
total number of changes you bring into the
variant; however, this option may result in
broken builds because indirectly associated
files are not picked up.
Error error Results in an error if other change packages
are required but not specified.
Skip Revisions skip Results in an error if any backfill revisions are
specified during the Apply CP operation.
Ask to Specify ask Displays the backfill list. To complete the
Apply CP operation, you must accept the
entire list. If you decline the list, the Apply CP
operation fails.
In the Apply CP operation, you must accept the entire backfill list or the
operation fails. If you do not want to accept the entire backfill list, you
must instead perform a Resync CP operation. The Resync CP command
allows you to merge around unwanted revisions in your sandbox. For
more information on resynchronizing change packages, see “Using the
Resync CP Command” on page 375.
The next example illustrates how Apply CP handles a more complex
change package—one that contains code modifications that are dependent
on a new file. In this example, main.c is revised to call a value defined in a
new file, main.h.
363