[p4] best way to prevent branching?

Stephen Vance steve at vance.com
Fri Jun 9 12:35:06 PDT 2006


So all developers should be able to develop on the product branches, but 
not create new branches there? Sounds like a job for triggers. You would 
check for "branch/sync" (be careful about downgraded branching) 
operations in the file list and reject it if it was in the wrong 
location by the wrong users. It would make it easier if your 
"developers" tree was not a subset of what you were trying to protect, 
but that's only a simplification and optimization.

Steve

Jay Glanville wrote:
> 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
>
>   


More information about the perforce-user mailing list