1

I made a branch with a cleartool cmd line utility with:

cleartool> mkbrtype BRANCH_NAME
cleartool> mkbranch BRANCH_NAME

Next I specified mkbranch in the configspec for the view I am working with like

element * .../BRANCH_NAME/LATEST
mkbranch BRANCH_NAME
element /vob_name initial_label
end mkbranch

Next I checked out files of interest, applied a patch of mine to it and checked the changes in with the UI utility.

Right after I've done with it I applied:

cleartool> mklbtype label_name
cleartool> mklabel -recurse label_name vob_name

Everything seems fine when I put this label instead of initial_label - I see the changes I made. Unfortunately its only me who can see the contents of vob with this my label.

Question: What I have done wrong and how I can fix this problem? PS: I created a different view with the same configspec and in this view the vob also empty for me.

Zorgiev
  • 794
  • 1
  • 7
  • 19

1 Answers1

0

Unfortunately its only me who can see the contents of vob with this my label

You can debug this by asking a colleague to do a version tree on one of the elements that you checked out/checked in in the new branch.
That version tree can be done from any version of that file.

If the new branch is visible in the version tree, and your colleague doesn't see your modification in his/her ClearCase view, that simply means their config spec isn't the same as yours, and isn't set top show the LATEST versions from that new branch.

The OP Zorgiev adds in the comment:

under different view I see my version as a RESERVED and the version number is not specified within the circle.
I suspect it thinks that the file is still checked out (RESERVED), but actually I checkd in my changes.

I confirmed: all files need to be checked in before setting up a label. Or only the view which has those files checked out would see them.

Beside the RESERVED should be the name of the view in which the version is checked out.

The OP adds:

We managed to get changes observable through the change in the configspec like: 

element /vob_name/... label_name -mkbranch BRANCH_NAME 
element /vob_name/... /main/LATEST -mkbranch BRANCH_NAME

What is the problem here? How do others make their branches/labels so that nobody needs to specify vob elemennt name twice like in this example? They make their labels so that I can just specify the label name once

I detail what kind of config rules are needed for branch creation in "ClearCase Branching using configspec".

In particular, a stop rule (one always true) like element /myVob /main/LATEST is very important.

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • But if they don't specify the branch name explicitly but rely only on the label I gave them, doesn't this mean they must automatically get the changes from the label I gave(I mean the branch I checked chanhes into)? – Zorgiev Feb 02 '15 at 16:05
  • PS: I created a different view with the same configspec and in this view the vob also empty for me. – Zorgiev Feb 02 '15 at 16:13
  • @Zorgiev they will only if *all* the parent folders (`/avob`, `/avob/folder1`, `/avob/folder1/folder2`, ...) have been labelled as well. If one level is mission, the view won't be able to access and display the versions below. – VonC Feb 02 '15 at 16:23
  • I tried to re-apply label with Apply Label Wizard(Set up "Move existing Label" option) and this have no effect. – Zorgiev Feb 02 '15 at 16:28
  • @Zorgiev yes, but the label needs to be applied from the very top as well (but not recursively or you would end up applying the label to *everything*). Once you now that you must label everything within `/avob/folder1/folder2`(which you can do with the Wizard), *then* you need to apply that label as well on `/avob/folder` (and just that folder, nothing else), and then on `/avob` (and just that vob root directory, and nothing else). – VonC Feb 02 '15 at 16:33
  • I need to label entire VOB with all the versions it contains. And so do I when I use Apply Label Wizard. – Zorgiev Feb 02 '15 at 16:42
  • Maybe something is wron with the branch/type I created? This very operation succeeded earlier. – Zorgiev Feb 02 '15 at 16:51
  • @Zor Simply do a version tree on each parent folder, all the way up to the vob root directory, and check if that label is there for a version of each folder. – VonC Feb 02 '15 at 16:58
  • Actually I see entire vob with the same configspec in another view as empty. But let me try checking your suggestion. – Zorgiev Feb 02 '15 at 16:59
  • under different view I see my version as a RESERVED and the version number is not specified within the circle. What does it mean? – Zorgiev Feb 02 '15 at 17:07
  • I suspect it thinks that the file is still checked out(RESERVED), but actually I checkd in my changes. – Zorgiev Feb 02 '15 at 17:18
  • @Zorgiev I confirmed: all files need to be checked in *before* setting up a label. Or only the view which has those files checked out would see them. – VonC Feb 02 '15 at 18:23
  • We managed to get changes observable through the change in the configspec like: element /vob_name/... label_name -mkbranch BRANCH_NAME element /vob_name/... /main/LATEST -mkbranch BRANCH_NAME What is the problem here? How do others make their branches/labels so that nobody needs to specify vob elemnt name twice like in this example? They make their labels so that I can just specify the label name once. – Zorgiev Feb 02 '15 at 19:31
  • @Zorgiev I have edited the answer. http://stackoverflow.com/a/4246525/6309 is an instructive read. – VonC Feb 02 '15 at 19:39
  • But in my main view where I checked chages in if I specify thils label name in configspec without additional branch information - I get my chenges fetched. – Zorgiev Feb 03 '15 at 10:22
  • @Zorgiev true, it needs to be tested in a separate view. – VonC Feb 03 '15 at 10:30