[p4] best way to prevent branching?

[Jay Glanville]

Thanks for the pointer Matt.  Can I pick your brain over the wording of
this undocumented feature?

I'm interpreting that by denying the "=branch" right to a branch tree,
I'm preventing it from being branched.  If this is correct, then it may
not be what I need as I still want to allow people to branch, but only
to the sandbox (other then the admin of course).

Does my interpretation make sense, or am I out in left field?

Thanks again for your suggestion.  

JDG

-----Original Message-----
From: Matthew Janulewicz [mailto:MJanulewicz at greendotcorp.com] 
Sent: June 9, 2006 2:56 PM
To: Jay Glanville; Perforce Users Mailing List
Subject: RE: [p4] best way to prevent branching?


I think this has been in perforce for a while, but I'm not sure.

>From 'p4 help undoc':

    Protections =read, =branch, =open, =write
        In addition to the normal protection levels (list, read, write,
        open, super, and review) there are four protection rights
        available in the 'p4 protect' table.  Unlike the levels, these
        '=rights' only include the specific right and not all the lesser
        rights.  This makes it possible to deny individual rights
without
        having to then re-grant lesser rights.

        Additionally, there is a new right =branch (normally included
        by level 'read' and above) that permits the files to be used as
        the source for 'p4 integrate'.  You can prevent files from being
        branched by denying the =branch right.


-Matt


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Jay Glanville
Sent: Friday, June 09, 2006 11:41 AM
To: Perforce Users Mailing List
Subject: [p4] best way to prevent branching?

Hello all.

What's the best way to prevent users from creating branches in the wrong
area?

Now for the specifics ... we have a branching structure that looks like
this:
  //depot/[product]/branches/[branch_name]/...
We also have a sandbox area for each product in which the developers can
create what I call "developer branches", one where developers are
encouraged to make branches for their own purposes, something like this:
  //depot/[product]/branches/developers/[branch_name]/...

What we would like to do is make it so that only user X and Y can create
branches under the product's branches, but anyone can make branches
under the sandbox location.  (Basically, X and Y are the release
managers.)

The reason for this need is because developers have mistakenly created
branches in the wrong location, causing problems.

What is the best way to setup such a rule structure?  I can't see how to
do it in the protections table.  Is a trigger the only way to go?

Thanks

JDG

---
Jay Dickon Glanville

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user