Topic
  • 4 replies
  • Latest Post - ‏2013-05-14T13:50:05Z by Dilip.J.Mansukhani
vernK
vernK
15 Posts

Pinned topic User in dev stream not allowed to add files to source control

‏2013-05-07T18:54:44Z |

We have a developer with a dev view in a UCM V8 project.  He added some folders and files to a versioned folder in the source tree then tried to select "Add to Source Control"  and got a refusal saying he did not have permissions to "create branch.'  I had him try checking out the containing versioned folder and then do "add to source control" on one of the files inside but we got the same error message referring to no permissions to "cleate branch." even during the "right-click-->Check Out" operation on the versioned file.  Has anyone run into this situation?  Thanks in advance for your help.  VernK

  • Dave-Robinson
    Dave-Robinson
    116 Posts

    Re: User in dev stream not allowed to add files to source control

    ‏2013-05-08T09:27:18Z  

    http://publib.boulder.ibm.com/infocenter/cchelp/v8r0m0/topic/com.ibm.rational.clearcase.cc_ref.doc/topics/ct_mkbranch.htm

    Restrictions

    Identities

    You must have one of the following identities:

    • Element group member
    • Element owner
    • VOB owner
    • root (UNIX and Linux)
    • Member of the ClearCase administrators group (ClearCase on Windows)

     

  • vernK
    vernK
    15 Posts

    Re: User in dev stream not allowed to add files to source control

    ‏2013-05-08T16:04:46Z  

    http://publib.boulder.ibm.com/infocenter/cchelp/v8r0m0/topic/com.ibm.rational.clearcase.cc_ref.doc/topics/ct_mkbranch.htm

    Restrictions

    Identities

    You must have one of the following identities:

    • Element group member
    • Element owner
    • VOB owner
    • root (UNIX and Linux)
    • Member of the ClearCase administrators group (ClearCase on Windows)

     

    HI Dave,  Thanks for the reply.  We had this developer added to all groups on the VOB and he is still getting the same error that refers to "no permission to make branch"  The error is thrown when we does "RClick" (on the containing folder)  in order to check it out so that he can "RClick" on the file itself and select "Add to Source Control."

    Do you know why CC looks at this as a "make branch" scenario?

    Thanks again,

    Vern

  • Dave-Robinson
    Dave-Robinson
    116 Posts

    Re: User in dev stream not allowed to add files to source control

    ‏2013-05-13T07:28:00Z  
    • vernK
    • ‏2013-05-08T16:04:46Z

    HI Dave,  Thanks for the reply.  We had this developer added to all groups on the VOB and he is still getting the same error that refers to "no permission to make branch"  The error is thrown when we does "RClick" (on the containing folder)  in order to check it out so that he can "RClick" on the file itself and select "Add to Source Control."

    Do you know why CC looks at this as a "make branch" scenario?

    Thanks again,

    Vern

    Hello Vern,

    The config spec of the view being used has an auto-mkbranch rule so that all checkouts shall be to the branch that is associated with the user's stream.

    Obviously this is the first time that the developer has tried to checkout this branch to this stream, so the branch does not already exist.

    NOTE: "We had this developer added to all groups on the VOB"

     The developer needs to logout and login to create an Access Token (assuming Windows here) that picks up the group membership changes you have made.

    If you have a huge number of group memberships, be aware that ClearCase can use only the "first 32".

    Do a technote search about the CLEARCASE_GROUPS environment variable. The only group relevant for this issue is the actual group of the directory element.

  • Dilip.J.Mansukhani
    Dilip.J.Mansukhani
    99 Posts

    Re: User in dev stream not allowed to add files to source control

    ‏2013-05-14T13:50:05Z  

    Hello Vern,

    The config spec of the view being used has an auto-mkbranch rule so that all checkouts shall be to the branch that is associated with the user's stream.

    Obviously this is the first time that the developer has tried to checkout this branch to this stream, so the branch does not already exist.

    NOTE: "We had this developer added to all groups on the VOB"

     The developer needs to logout and login to create an Access Token (assuming Windows here) that picks up the group membership changes you have made.

    If you have a huge number of group memberships, be aware that ClearCase can use only the "first 32".

    Do a technote search about the CLEARCASE_GROUPS environment variable. The only group relevant for this issue is the actual group of the directory element.

    if the client is using os which is 64-bit then there are changes that CC will not evluate the CLEARCASE_GROUPS correctly if that user id is part of more than 32 groups.

     

    Thanks

    Dilip