Search code examples
clearcasecleartool

ClearCase label problems: nobody except me can observe the files I labeled

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.

Solution

  • 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.