The setplevel command allows you to redefine the list of baseline promotion levels for a project VOB and to designate one of these levels as the default promotion level for new baselines.
Each project VOB includes an ordered set of promotion levels. Promotion levels are ordered from lowest to highest and can be assigned to baselines to indicate the quality or degree of completeness of the activities and versions represented by the baseline. When a project VOB is created, it includes the following ordered set of promotion levels: REJECTED, INITIAL, BUILT, TESTED, RELEASED. The default promotion level is INITIAL. This is the level that is assigned to newly created baselines.
A baseline's promotion level is used in computing a project's list of recommended baselines. The recommended baseline for a component is the latest baseline of that component in the project's integration stream that has a promotion level greater than or equal to the project's recommended promotion level (see the chproject reference page).
Ordered promotion levels can be used to filter lists of baselines. Promotion level is also used to populate the default list of baselines during a rebase operation on a stream. Each project defines a default rebase level. When a project is created, the default rebase level is set to the project VOB's default promotion level. For more information, see chproject.
When you delete a level that is in use, it is not completely removed from the project VOB. Instead, its place in order is changed so that it is considered to be lower than the lowest defined level. You can list information for baselines labeled with such a promotion level lsbl –level command.
The promotion levels available in a VOB can be listed by running the describe command on the project VOB object. Promotion levels can be used to filter lsbl output (see the lsbl reference page).
The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
Copyright© 2003 Rational Software. All Rights Reserved.