CLI Reference > Configuration Management Commands > si extenddevpath
si extenddevpath
extends an extendable development path
si extenddevpath [--extendRecursively] [(-P project|--project=project)] [(-S sandbox|--sandbox=sandbox)] [--devpath=path] [--[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]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]] [--status=[none|gui|default]]
si extenddevpath takes selected build subprojects and extends the closest enclosing development path down to these subprojects. This command, which requires ExtendDevpath permission, creates the variant on the specified subproject and its ancestors. The configuration of sibling subprojects is left intact. If every subproject in the tree is included in a development path, an extendable development path is equivalent to a full development path.
For more information, see "Extending an Extendable Development Path" in the Windchill RV&S Help Center.
This command takes the universal options available to all si commands, as well as some general options. See the options reference page for descriptions.
--extendRecursively extends the extendable development path with full recursion below the selected subproject in a multi-transactional way that does not lock the project for other users. When this option is used, the specified subproject can be either a variant subproject or a build subproject.
To specify the subproject to extend, you can use any of the following methods:
-P configPathToBuildSubInVariantHierarchy
where configPathToBuildSubInVariantHierarchy is the configuration path to the build subproject in the variant hierarchy
-P legacyPathToParentProject--devpath legacyDevpath subName/project.pj
where legacyPathToParentProject is the legacy path to the parent project and legacyDevpath subName/project.pj is the legacy development path subproject name followed by a backward slash and the project name
-P configPathToParentProject subName/project.pj
where configPathToParentProject subName/project.pj is the configuration path to the parent project followed by the path subproject name, a backward slash, and the project name
If you do not specify the -P option, you will be prompted and should specify the configuration path to the subproject.
When using the -g option, you need to select the build subproject in the variant hierarchy. The -g option does not support selecting multiple subprojects to extend from the GUI.
The optional --devpath option and subproject name selection are never prompted. You must specify them upfront if you plan on using them.
Examples of Extending Extendable Development Paths
Extendable development paths can be extended using configuration paths, legacy syntax, and sandbox context. Several examples follow:
To extend an extendable development path from "path1" to "sss1" using a configuration path:
si extenddevpath --project=#/demo1#d=path1#s1#ss1#sss1
To extend an extendable development path from "path2" to "s1" using legacy syntax:
si extenddevpath --project=/demo1/project.pj --devpath=path2 s1/project.pj
To extend an extendable development path from "path3" to "s1" in a sandbox context:
si extenddevpath --sandbox=c:/sandbox/demo1path3/project.pj c:/sandbox/demo1path3/s1/project.pj
To extend an extendable development path from from "path4" to "sss1" in a sandbox context under a sandbox directory:
C:\sandbox\demo1path4>si extenddevpath s1/ss1/sss1/project.pj
To extend an extendable development path from "path5" to multiple subprojects ("s1" and "s2") that have the same parent:
si extenddevpath --project=#/demo1#d=path5 s1/project.pj s2/project.pj
See the diagnostics reference page for possible exit status values.
Using si setprefs or si viewprefs, you are able to set or view the preference keys for this command.
See Also
si createdevpath
ACL, diagnostics, options, preferences