si applycp
applies one or more change packages to an Integrity Lifecycle Manager configuration management project
Synopsis
si applycp [--[no]alreadyInProjectIsError] [--backFill=[cp|revision|error|skip|ask]] [--[no]useMaster] [--[no]failOnAmbiguousProject] [--[no|confirm]closeCP] [--[no]confirm] [--[no|confirm]createVariants] [--notify=[never|onCompletion|onError]] [--[no]ignoreBranches] [--[no]ignoreServer] [--[no]otherProjectIsError ] [--[no]spanProjects] [--[no]verbose] [(-P project|--project=project)] [(-S sandbox|--sandbox=sandbox)] [--devpath=path] [--hostname =server] [--port=number] [--password=password] [--user=name] [(-?|--usage)] [(-F file|--selectionFile=file)] [(-N |--no)] [(-Y|--yes)] [--[no]batch] [--cwd =directory] [--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]] [--status=[none|gui|default]] [--cpid=ID|--changePackageID=ID] [--[no]ignoreUpdateRevision] [--issueID=value] [--subprojectPropagation=[explicit|implicit]] issue|issue:change package id...
Description
si applycp propagates changes recorded in change packages from one project or development path to another. This enables you to propagate only the changes that you want to. The process updates member revisions and can also involve adding, dropping, renaming, and moving files. Additionally, it can involve creating, adding, dropping. or moving subprojects. The si applycp command is most useful for building software.
|
|
If you are using the si applycp command to propagate changes recorded in a change package to an extendable development path, the project configuration is updated automatically. Extenddevpath permission is required when operating against an extendable development path.
|
For more detailed information and examples for si applycp, see the Integrity Lifecycle Manager Help Center.
Options
This command takes the universal options available to all
si commands, as well as some general options. See the
options reference page for descriptions.
• --cpid=ID
• --changePackageId=ID
identifies a propagation change package to record the changes made as a result of the si applycp operation. Only open change packages can be used. This is not the change package that you want to apply to the project; it is the change package that you want to use to record the results of the operation.
• --[no]alreadyInProjectIsError
Causes Integrity Lifecycle Manager to terminate the operation if the change being applied has already been applied to the project. If this setting is negated --noalreadyInProjectIsError, then the information is displayed as a warning.
• --backFill=[cp|revision|error|skip|ask]
Specifies the way Integrity Lifecycle Manager treats historic revisions required by the specified change package.
◦ --backFill=cp
recursively chooses all historic revisions required by the specified change packages and applies them by updating member revisions, adding files, or dropping files.
◦ --backFill=revision
processes only the specified change package(s) and chooses only directly associated revisions. It does not process any change packages that are associated with intermediate revisions.
◦ --backFill=error
terminates the operation if other change packages are required but are not specified.
◦ --backFill=ask
allows you to specify the change packages you want to include.
• --[no]confirm
specifies whether to confirm the actions before starting them.
• --[no|confirm]createVariants
specifies whether to create new variant subprojects within the target variant project as required. This allows the subproject structure of the target variant to mirror the structure of the source project.
• --notify=[never|onCompletion|onError]
specifies whether to display a report when the command is complete. The report details the operations that were performed and any errors that were encountered.
◦ --notify=never
never displays the report.
◦ --notify=onCompletion
always displays the report.
◦ --notify=onError
displays the report if any errors were encountered.
• --[no]ignoreBranches
specifies whether to use the most recent revision when Integrity Lifecycle Manager encounters two revisions of the same member on different branches in the change package being applied.
• --[no]useMaster
operates on the top-level project if the target is a subproject. Changes are applied throughout the top-level project’s hierarchy.
• --[no]ignoreServer
specifies whether to perform the Apply CP operation even if the change package members reside on different servers.
|
|
The --ignoreServer 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.
|
• --[no]ignoreUpdateRevision
ignores update revision change package entries. Use this option when the change package contains backward revision updates, for example, from 1.4 to 1.2. The default is to include update revision entries for backwards compatibility with older version of Integrity Lifecycle Manager (formerly MKS Source).
• --[no]otherProjectIsError
specifies whether to terminate the command if the change is for a project other than the one you initially targeted. If this setting is negated --nootherProjectIsError, then the information is displayed as a warning.
• --[no]spanProjects
specifies whether to apply all changes in the change package, even if this involves a different project than the one you initially targeted. If you are applying a change package that contains move member or move subproject entries between two project, the --[no]spanProjects option must be used.
|
|
This is the only operation that has the potential to affect other projects.
|
• --[no]verbose
specifies whether to include additional information to track the current state of the command.
• --[no|confirm]closeCP
closes the change package after command completion.
• --subprojectPropagation=[explicit|implicit]
specifies how to apply subproject changes required by the specified change packages.
◦ --subprojectPropagation=explicit
creates, adds, drops, or moves a subproject only if there is a explicit command to do so in the change package.
◦ --subprojectPropagation=implicit
creates, 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 target project being updated, the subproject is added.
• --issueID=value
specifies the issue ID that corresponds to the change package that records the changes.
• issue...
issue identifies a specific issue that contains all change packages that you want to include; use spaces to specify more than one issue.
• issue:change package id...
issue:change package id identifies a specific change package to include; use spaces to specify more than one change package.
Diagnostics
See the
diagnostics reference page for possible exit status values.
Preferences
Using
si setprefs or
si viewprefs, you are able to set or view the preference keys for this command.
See Also
