The mkbl command creates baselines or composite baselines. A baseline represents a snapshot of the changes made to a particular component in the context of a particular stream: it is a version of a component. For each element in the component, the baseline records the version of that element selected by the stream's configuration at the time mkbl is executed. The baseline also records the list of activities in the stream whose change sets contain versions of the component's elements.
A baseline selects one version of each element of a component. You can create multiple baselines per component, just as you can create multiple versions of an element. A baseline is associated with only one component, and you can only create one baseline per component per invocation of mkbl.
By default, all components that have been modified since the last full baseline are considered as candidates for new baselines. You can also create baselines for a subset of components in the stream or for components modified by specific activities.
If your project team works on multiple components, you may create a composite baseline. A composite baseline is a baseline that selects baselines in other components. You can use a composite baseline to represent the entire project baseline; this is easier than keeping track of a set of baselines, one for each component. We recommend that you create a component for storing the composite baselines. (For information about how to create this type of component, see mkcomp.) In that component, create the composite baseline by adding member baselines with the –adepends_on option.
When you create an ordinary component (that is, one that contains directories and elements), it includes an initial baseline whose name is of the form component-name_INITIAL. This baseline selects the /main/0 version of the component's root directory and serves as a starting point for successive baselines of the component.
Use the –identical option to create a new baseline for a component that has not been modified. This can be useful in working with several components. You can create new baselines for a set of components regardless of whether they have been modified.
By default, all activities modified since the last baseline was made are captured in new baselines. You can select a subset of activities for inclusion in the baseline. If there are dependencies between the change sets of activities, you may not be able to include only the activity you want; you'll need to include the activities it depends on as well.
A single baseline is created if the selected activities are part of the same component. If an activity modifies more than one component, a new baseline is created for each component it modifies.
The operation of creating a new composite baseline is recursive. That is, the operation first creates baselines of its member components and then creates dependency references to those baselines in the composite. The result is a composite baseline that retains the dependency structure of its predecessor.
You can create or change the dependency relationships for a composite baseline by using the –adepends_on or –ddepends_on options. When a dependency reference to a component is added, a baseline of that component is made, if necessary. These operations apply only to direct members of a composite baseline and do not affect indirect members in a baseline hierarchy. A dropped component can still have a baseline that is lower in the dependency hierarchy.
Note: To change the existing dependency relationships, you must create a new composite baseline. You cannot change the relationships of an existing baseline with chbl.
You can recognize a VOB as a component with the mkcomp command. When you do this, the VOB is given an initial baseline that selects the /main/0 version of the component root directory. However, this baseline does not automatically enable access to files and directories that are already in the VOB.
You can create a new baseline that corresponds to a set of labeled versions in the VOB or one of the VOB's components. To do this, use the –import option. The mkbl command creates a baseline that selects the labeled versions, making them accessible to the UCM project.
Before creating the baseline, be sure that the label is unlocked and ordinary (not global) and that labeled elements are checked in. Once the baseline is created, the label cannot be moved or removed except by privileged users. Be certain the label selects some version of all visible elements.
By default, baseline identifiers are made up of two parts: a user-specifiable basename and a generated, unique numeric extension. However, if you have defined a baseline name template for your project, baseline names will be created using that template. For information about defining a baseline name template, see mkproject and chproject.
The exceptions to the above rule are initial baselines and baselines created from a label. The name of an initial baseline is of the form component-name_INITIAL. When you create a baseline by importing a label, the basename is derived from the label's type selector. For example, the label-type selector REL1@/vobs/baz generates a baseline basename of REL1 whose scope is the baz component.
You can choose whether versions of the baseline are to be labeled when the baseline is created. Baselines can be unlabeled, incrementally labeled, or fully labeled. After they are applied, baseline labels cannot be moved.
All baselines record a component's current configuration in a stream, but only labeled baselines can be used to configure other streams (by means of rebase or mkstream).
Choose a labeling scheme that suits your project's structure. Incremental baselines typically can be created more quickly than full baselines.
These options control labeling during baseline creation:
Each time when new baselines are made, mkbl checks to see whether any latest baselines are unlabeled. If any are found, mkbl issues a warning and displays the unlabeled baselines. You can change the labeling status for a baseline with the chbl command.
Baselines are marked with a promotion level that signifies the quality of the baseline. When created, a project VOB is assigned an ordered set of promotion levels, one of which is designated the default promotion level, which is the level assigned to new baselines when they are created.
For more information, see setplevel.
activity-selector is of the form [activity:]activity-name[@vob-selector] where vob-selector specifies the activity's project VOB.
You can use this option to include only a subset of the unrecorded changes in the new baselines. A baseline is created for each component that has unrecorded changes in the specified list of activities.
The list of activities must be complete. That is, they must not depend on the inclusion of any other activities. Activity A2 is dependent on activity A1 if they both contain versions of the same element and A2 contains a later version than A1. If the list of activities is incomplete, the operation fails and lists the required activities.
For example, if you are working in coyne_dev_view, but want to create a baseline from the configuration specified by the view coyne_integration_view, use –view coyne_integration_view. This option creates a baseline in the project's integration stream that includes all the checked-in versions contained in coyne_integration_view. If you do not specify view-tag, the current view is used.
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.
Note: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf—for example, /vobs/src. A single-component VOB tag consists of a leaf only—for example, /src. In all other respects, the examples are valid for ClearCase LT.
cmd-context mkbl CITTEST
Created baseline "CITTEST.BL14_mprent_mck.1_021903.1543" in
component "webo_modeler".
Begin incrementally labeling baseline
"CITTEST.BL14_mprent_mck.1_021903.1543".
Done incrementally labeling baseline
"CITTEST.BL14_mprent_mck.1_021903.1543".
Created baseline "CITTEST.BL14_mprent_mck.1_021903.1524" in
component "webo_gui".
Begin incrementally labeling baseline
"CITTEST.BL14_mprent_mck.1_021903.1524".
Done incrementally labeling baseline
"CITTEST.BL14_mprent_mck.1_021903.1524".
Copyright© 2003 Rational Software. All Rights Reserved.