[p4] Limiting users ability to create new branches

Robert Cowham robert at vaccaperna.co.uk
Wed Feb 27 14:53:23 PST 2008

As well as protections, you can use a pre-submit trigger to check on newly
branched files and their locations.

For example:


There are a couple of examples which ensure that people at least name their
branches in accordance with certain standards. Keeps the namespace clean and
tidy and prevents typos etc.

There is also the pro-active education side of things to find out why they
are creating so many, to show some of the issues and to educate them as to
the error of their ways. The latter can, on occasion, be helped by
application of said baseball bat :) 

> -----Original Messag-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> Jamison, Shawn
> Sent: 27 February 2008 14:22
> To: perforce-user at perforce.com
> Subject: [p4] Limiting users ability to create new branches
> I have the express need to limit a development groups ability 
> to create new branches.
> They seem to think that a new branch is the solution to every 
> development problem.  
> Has anyone experienced this before or have any suggestions on 
> how to accomplish this?  
> 	Besides sending a dude named Tony to visit them with at 
> baseball bat...

More information about the perforce-user mailing list