Adding a Configuration Management Subproject
|
CLI EQUIVALENT
|
si addsubproject
|
You can add a subproject in the following two situations:
• A subproject was dropped from a project, the subproject’s historical information remains, and you need to add the subproject back.
• You want to add a shared subproject.
|
|
To add a dropped subproject, you must know where it previously existed. If you do not know, you can use the Locate command.
|
You can add a dropped subproject in several ways:
• Navigate to the project where the subproject previously existed. Select > > . Navigate to the project where the subproject used to reside. Use the Date selector to select the date when the subproject was a part of the parent project. Then select the subproject to be re-added.
• Open a date-based project configuration view from before the subproject was dropped. Then, select > > and select the project where you would like to add the subproject.
• From a checkpoint of the project that contained the subproject, open a build project view. Then, select > > and select the project where you would like to add the subproject.
Integrity Lifecycle Manager automatically determines if the subproject you specify is one that has been dropped. If the subproject exists, you are presented with the option to share it.
When adding a subproject, you can specify one of the following types:
• Normal adds a working subproject based on the mainline
• Variant adds a subproject based on a specific development path.
|
|
The Variant option is unavailable if there are no available development paths.
|
• Build adds a static subproject based on a specific checkpoint of the master project that is used for building or testing the project, but is not used for further development. You can specify the checkpoint through its checkpoint number or label.
• Default adds a subproject as the same type as the parent project.
|
|
Subproject type is pre-populated based on its configuration selected. It can be modified if a different type of subproject needs to be added.
|
