si mergechilddevpath
merges development path into its parent revision
Synopsis
si mergechilddevpath[--issueId=value][--sourcedevpath=value][--[no]failOnAmbiguousProject] [(-S sandbox|--sandbox=sandbox)][--hostname=server][--port=number][--password=password][--user=name][(-?|--usage)][(-F file|--selectionFile=file)][(-N|--no)][(-Y|--yes)][--[no]batch][--cwd=directory][--forceConfirm=[yes|no]][--quiet] [(-g|--gui)][--settingsUI=[gui|default]][--status=[none|gui|default]]
Description
si mergechilddevpath merges all changes from a branch into that branch's immediate parent revision.
Integrity Lifecycle Manager provides you with a streamlined method of merging a development path into its parent development path. The parent development path may be mainline, or it may be a development path itself. The merge destination just needs to be the parent of the child being merged into it. For detailed information on merging a child development path, see the Integrity Lifecycle Manager Help Center.
|
|
To run the si mergechilddevpath command in batch mode from the CLI or API, set the desired merge preferences on si resynccp using the options for --onMergeConflict and --mergeType.
|
• --sourcedevpath=value
specifies the development path to merge into the parent project revision. Only children of the previously selected project can be specified. This option can only be specified if the integration between configuration management, and workflow and document management is enabled.
• --[no]failOnAmbiguousProject
This option does not currently function for the si mergechilddevpath command.
• --sandbox=sandbox or -S sandbox
specifies the location of the target Sandbox. Locations that include spaces must be enclosed by quotes.
• --issueID=value
specifies the item to use to store the propagation change package information.
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
