CLI Reference > Configuration Management Commands > si deactivatedevpath
si deactivatedevpath
deactivates a development path
si deactivatedevpath [--devpath=value] [(-P project|--project=project)] [(-S sandbox|--sandbox=sandbox)] [--hostname=server] [--port=number] [--password=password] [--user=name] [(-?|--usage)] [--[no]failOnAmbiguousProject] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory] [--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]] [--status=[none|gui|default]]
When a development path is no longer active, but you do not want to permanently delete it, you can deactivate the development path. si deactivatedevpath enables you to mark a development path as inactive.
If you want to permanently remove a development path, you can delete it instead. For more information, see "Removing a Development Path" in the Windchill RV&S Help Center.
Inactive development paths are filtered out of most views and commands. This command requires that you specify either the mainline project and a development path, or a variant project or variant sandbox.
Once a development project has been deactivated, it cannot be modified. The only actions that you can take are dropping or activating the development path. Change packages for a deactivated development path can be discarded.
Later, you can reactivate the development path if necessary using the si activatedevpath command.
The following is an example for deactivating a development path:
si deactivatedevpath --project=c:/Aurora_Program/bin/Libra/project.pj --devpath=DevStream
While you cannot rename a development path directly, you can use the Deactivate action to achieve the same result by performing the following steps:
1. Checkpoint the development path that you plan to deactivate.
2. From the checkpoint that you created, create a new development path using the new name.
3. Copy permissions from the deactivated development path (with the old name) to the new development path (with the new name). For more information, see "Copy Project Permissions" in the Windchill RV&S Help Center.
4. Deactivate the development path that you want to rename.
Optionally, if you want to reuse the old development path name on the same project, remove the deactivated development path. For more information, see "Removing a Development Path" in the Windchill RV&S Help Center.
Before Deactivating a Development Path
Before you deactivate a development path, you must ensure that there is no work in progress and restrict any further work on the variant project:
1. Identify and remove any change packages, locks, and pending operations:
Ensure that there are no locks that are not under change packages using the si projectlocks command.
If you use change packages, do the following:
Confirm that there are no open change packages for the variant project using the si viewcps command:
si viewcps --filter=variant:devpathname
Verify that there are no pending operations using the si viewproject command:
si viewproject --filter=pending --filtersubs --project=project
2. Restrict the variant project to ensure that no more changes are made using the si restrictproject command.
This command takes the universal options available to all si commands, as well as some general options. See the options reference page for descriptions.
the name of the development path to deactivate.
the name of the target project. You must specify either this option or --sandbox; the two options are mutually exclusive.
the name of the sandbox, which can be used to redirect to a project. You must specify either this option or--project; the two options are mutually exclusive.
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
Commands: si activatedevpath, si archiveinfo, si createsandbox, si dropdevpath, si memberinfo, si projectinfo, si revisioninfo, si rlog
Miscellaneous: ACL, diagnostics, options, preferences