Creates a baseline or set of baselines
Product | Command Type |
---|---|
ClearCase | cleartool subcommand |
ClearCase LT | cleartool subcommand |
Platform |
---|
UNIX |
Windows |
Create a baseline of a component or set of baselines of components:
Create or change the dependency relationships for a composite baseline:
Create a baseline by importing a label type:
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. The label is locked when the baseline is created; you cannot move the label later. Be certain the label selects some version of all visible elements.
Baseline identifiers are made up of two parts: a user-specifiable root name and a generated, unique numeric extension. The same root name can be used for baselines of more than one component. However, a root name can be used only once per component per stream.
When you create a baseline by importing a label, the root name is derived from the label's type selector. For example, the label-type selector REL1@/vobs/baz generates a baseline root name 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.
For a full baseline, the time required is proportional to the number of elements in the component.
For an incremental baseline, the time required is proportional to the number of elements changed since the last full baseline.
These options control labeling during baseline creation:
The -nlabel option, which creates an unlabeled baseline. Unlabeled baselines cannot be used as foundation baselines to configure a stream. They can be used with the diffbl command.
The -incremental option, which labels versions of elements that have changed since the last full baseline was created.
The -full option, which creates a baseline by selecting and labeling a version of each element in the component.
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.
See setplevel for more information.
Identities: No special identity required.
Locks: An error is generated if there are locks on any of the following objects: the UCM project VOB, the component, the containing stream; and if you are importing a label type, the label type being imported.
Mastership: (Replicated VOBs only) Your current replica must master the stream where you make the baseline. When you create an imported baseline from a pre-UCM label, your current replica must master the component and label type.
EVENT RECORDS AND COMMENTS. Default: Creates one or more event records, with commenting controlled by your .clearcase_profile file (default: -cq). See the comments reference page. Comments can be edited with chevent.
SPECIFYING THE VIEW AND STREAM. Default: The stream to which the current view is attached.
SPECIFYING THE COMPONENTS OR ACTIVITIES. Default: -all.
SELECTING LABELING BEHAVIOR. Default: -incremental.
SPECIFYING THE BASELINE ROOT. Default: None.
CREATING OR CHANGING DEPENDENCY RELATIONSHIPS FOR A COMPOSITE BASELINE. Default: Creates a composite baseline that retains the dependency structure of its predecessor.
SPECIFYING A LABEL TO IMPORT. Default: None.
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. In Attache, cmd-context represents the workspace 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.
Create a baseline for a component xroutines by importing a label type.
cmd-context mkbl -c "Import BL2 label" -import BL2@/vobs/xroutines
Create baselines for all components in the project that have been modified since the last baseline was created.
cmd-context mkbl BL1
Created baseline "BL1.119" in component "webo_modeler".
Begin incrementally labeling baseline "BL1.119".
Done incrementally labeling baseline "BL1.119".
Created baseline "BL1.120" in component "webo_gui".
Begin incrementally labeling baseline "BL1.120".
Done incrementally labeling baseline "BL1.120".
Create baselines for the components modified by a particular activity.
cmd-context mkbl -activities line-lib@\pvob1 BL2
chbl, chstream, diffbl, lsbl, mkcomp, rmbl
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |