Apply Change Package Options: Advanced

Apply CP Advanced Command Option

Function

Use Master

Causes Integrity Lifecycle Manager to operate on the top-level project if the target is a subproject. Changes are applied throughout the top-level project’s hierarchy. If this option is not set, changes are only applied to the target project and its subprojects; other changes are ignored.

When spanning variant projects with the Use Master option enabled, the variant of the top-level project associated with the spanned project is evaluated and the subproject, if missing in the variant, is added.

Span Projects

Applies all changes in the change package, even if this involves a different project than the one you initially targeted.

If this option is not set, any changes for other projects are ignored.

This is the only command option that has the potential to affect other projects.

Raise error if member is already in project

Causes Integrity Lifecycle Manager to terminate the operation if the change being applied has already been applied to the project.

If this option is not set, then the information displays as a warning.

Raise error if member of other project

Terminates the command if the change is for a project other than the one you initially targeted.

If this option is not set, then the information displays as a warning.

Ignore Server in Change Package

Causes Integrity Lifecycle Manager to perform the Apply CP operation even if the current server does not match the server specified in the change package entries.

If this option is not set, any mismatches are treated as errors.

This option is useful when a server is the same but is now identified differently, for example, the server name has changed. This option is required because projects are defined by their server and path. Use this option with caution.

Ignore Cross-Branch Entries

Causes Integrity Lifecycle Manager to use the most recent revision when members with revisions on multiple branches are being applied.

If this option is not set, member revisions being applied from multiple branches are treated as errors.

Ignore Update Revision Entries

Ignores update revision entries in a change package. There is no user prompt.

This option is to support compatibility with older versions of Integrity Lifecycle Manager.

Propagate Subprojects

Determines how Integrity Lifecycle Manager treats subproject operations required by the specified change packages.

You can select from the following options:

• Explicitly adds, drops, or moves a subproject only if there is a explicit command to do so in the change package.

• Implicitly adds, drops or moves a subproject if the operation is implicitly required based on the change package entries. For example, if you are adding a member that is part of a subproject that does not exist in the larger project being updated, the subproject is added.