setplevel

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.

When you run chstream –recommended –default to let UCM compute a stream's list of recommended baselines, a baseline's promotion level is used in the computation. The recommended baseline for a component is the latest baseline of that component in the stream that has a promotion level greater than or equal to the project's recommended promotion level (see the chproject and chstream reference pages).

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 system and Linux examples in this section are written for use in csh. If you use another shell, you might 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 might 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 system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.

• From the project VOB directory, modify a new project VOB's set of promotion levels by removing the INITIAL level and adding a START level. Change the default level for new baselines to BUILT.

  cmd-context  setplevel -default BUILT REJECTED START BUILT TESTED

• Replace the promotion level UNIT_TEST with U_TEST.
  1. Add the new level to the current set of promotion levels:

     cmd-context setplevel -default NEW  NEW BUILT UNIT_TEST U_TEST

  2. Find baselines that use the old promotion level:

     cmd-context  lsbl -level UNIT_TEST  mybaseline

  3. Change the promotion level from UNIT_TEST to U_TEST:

     cmd-context  chbl -level U_TEST the-baselines-listed-in-step-2

  4. Remove the obsolete promotion level from the project VOB:

     cmd-context  setplevel -default NEW NEW BUILT U_TEST

chbl, chproject, describe, lsbl, mkproject