Dropping a Configuration Management Project
|
CLI EQUIVALENT
|
si dropproject
|
When a configuration management project has outlived its usefulness or just does not belong on the Integrity Lifecycle Manager server anymore, you can remove it.
To drop a configuration management project means that the project is no longer registered with the Integrity Lifecycle Manager server.
Project paths are referenced using the repository location. This allows you to reference checkpoints in dropped configuration management projects. If a checkpoint is currently referenced and the corresponding project is later dropped, the checkpoint remains accessible as read-only. For example, you can continue to open the referenced checkpoint from an SI project field or create a build Sandbox from the checkpoint for auditing purposes.
Dropped projects can also be accessed as read-only from the Change Package and Locks views until the project is purged or reclaimed by your administrator.
To drop a configuration management project, select a project in the Projects view, and select Drop Project.
|
|
If a project is dropped and any Sandboxes or variants are associated with it, those Sandboxes or variants no longer function.
Dropping a configuration management project unregisters it from the Integrity Lifecycle Manager server, but it does not delete the project. Dropped configuration management projects can be added back into Integrity Lifecycle Manager.
|
