Steps for building a branch in Windows using clearcase

1. Tag previous jobs, and set the clearcase-> apply label as prompted.
2. Create a branch code
In types release E, select branch type, and right-click --> create... write the name of the branch you want to create and add the necessary comments to create the branch that belongs to this vob.
3. Create a view for the branch and edit the config spec of the branch. The format is as follows:
Method 1:
Element * checkedout
Element */main/branch code/latest
Element * tag name-mkbranch branch code
Element * tag name
Element */main/latest
Load/vob name/location of the folder under vob
Simple explanations:
The first sentence indicates the version of the element to be checkout; this sentence is always at the beginning;
Last sentence: select the latest version of the main branch of the element.

When we use "add to source control"
When a file or directory is put into vob, it will become an element in the vob library. The meaning of vob is version object base,
The element is a version concept, and there will always be a main trunk that allows you to check in
The main form a version, so this statement can be considered as a garbage collector. You can always see the metadata
The latest content on the main branch.

Note that if you have several
Vob, you must ensure that all of these vob have ver1.00 label type (vob does not have the label type and cannot
Add the label instance). When creating the vob, we can specify that the label is a global range and belongs to the same
All sub-vob under vob will have such label.
Method 2:
Element * checkedout
Element */main/dev_branch/latest
Element */main/latest-mkbranch dev_branch
Element */main/latest
Explanation:
First, find the checkout version;
In the second sentence, find the latest version of the dev_branch branch under the main trunk;
The third statement is to find the latest version of the primary master. If the element is checked out, it will be triggered to create the latest version of the element.
Dev_branch. Because the branch of the created element is the modification of the element, it will be triggered only when it is checked out. Then
Re-interpret the content of running config spec for this element. In this case, check is selected on the/main/dev_branch branch.
Out version. If the element version checked out on the branch is checked in, the view selects/main/dev_branch.
The latest version on the branch, that is, the result of using the second sentence rule. (By the way, the branch type of dev_branch should be
Created in advance ).
When the configuration spec of the view is modified to Example 1. You can use the clearcase composite command for a vob
Next (assuming VOB is TRYIT_VOB), perform a Check Out operation for all elements, and then Check In will be
Element to generate the branch of dev_branch. Use the Config Spec of this view to work under the dev_branch branch. Reference command
Is:
Cleartool find Z:/TRYIT_VOB-exec "cleartool checkout-nc % CLEARCASE_PN %"

About ConfigSpec
In many cases, each statement in ConfigSpec is divided into three parts,
Part 1: Element type selection. We almost always use Element;
The second part, scope (or pattern matching), we often use "*" to match all element channels, and there are also comparisons
More often, it is similar to "/CC_TEST/train_folder/..." to match the first part of all the directory paths, that is, to limit the specific
. In addition, "*. txt" "/CC_TEST/test.txt" and so on can also be used, but rarely used.
The third part is version selection. For example, if We append the tag REL2 to the element version, we can use
REL2 is used as the basis for version selection. For example, ".../mybranch/LATEST" indicates that the LATEST version under the mybranch branch is selected.
No matter where the branch is created, "..." (three vertices) indicates a pattern match, such
/Main/mybranch/LATEST
/Main/testbranch/mybranch/LATEST
You can use ".../mybranch/LATEST" to indicate and match.