si createsubproject
creates a subproject or adds an existing project as a subproject
Synopsis
si createsubproject [ --[no|confirm]reuseDroppedSubproject] [ --[no]createSubprojects] [(-P project| --project=project)] [--[no]failOnAmbiguousProject] [(-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|confirm]closeCP] [--issueId=value] subproject location...
Description
si createsubproject creates a subproject on the server in a specified directory, which must be under an existing project specified by the -P project or --project=project options. For example,
si createsubproject --project=c:/Aurora_Program/project.pj c:/Aurora_Program/bin/Libra/project.pj
This command works with Regular and Variant sandboxes, but not with Build sandboxes.
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.
• --[no|confirm]reuseDroppedSubproject
controls whether to add an existing subproject to the named project. This can be useful if the existing subproject had been dropped from a project.
|
|
While si addsubproject is the recommended command for adding an existing subproject to a project, this option is available for backwards compatibility and any scripts you may use. |
• --[no]createSubprojects
controls whether to create one subproject for each directory encountered when creating subprojects.
• --cpid=ID
• --changePackageId=ID
identifies a change package that is notified of this action, for example, 1452:1.
|
|
• This option can only be specified if change packages are enabled.
• If the integration is enabled, but it is not mandatory to specify a change package, or if no change package is applicable, you can specify --changePackageId=:none.
• The next time you are prompted for a change package ID, the last used change package ID is displayed by default, if :none was specified or at least one change package was successfully updated from the last operation.
|
• --[no|confirm]closeCP
closes the change package after command completion.
• --issueId=value
specifies the issue ID that corresponds to the change package that records the changes.
• subproject location...
identifies a location on the Integrity Lifecycle Manager Server for the new subproject. Regardless of your operating system, all paths are specified here using forward slashes (/), and may be server relative or absolute paths. You must also specify the name of the project file as part of the location; typically this is project.pj.
|
|
Subprojects must be added "in tree", that is, in the project directory or a subdirectory.
|
As with the
si createproject command, remember that server-side restrictions may exist controlling where you are permitted to locate any subprojects on the
Integrity Lifecycle Manager Server. Contact your system administrator for permitted locations.
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
• Commands:
si checkpoint,
si createproject,
si createsandbox,
si drop,
si dropproject,
si projectinfo,
si projects,
si viewproject,
si configuresubproject,
si addsubproject,
si movesubproject,
si sharesubproject
