[p4] Using a label to "lock" a branch
Chuck O'Neill
4chuck.oneill at comcast.net
Thu Oct 9 22:02:11 PDT 2008
One approach I've used is to set a submit trigger on the branch and
have it check the value of a counter. You can then lock/unlock
submits to the area by setting the value of the counter.
>
>Date: Thu, 9 Oct 2008 07:05:41 -0700
>From: Steve_Mitchell at capgroup.com
>Subject: [p4] Using a label to "lock" a branch
>To: perforce-user at perforce.com
>Message-ID:
>
> <OFEB51BF8B.1E874998-ON882574DD.004C35D1-882574DD.004D6CDB at capgroup.com>
>
>Content-Type: text/plain; charset="US-ASCII"
>
>Hi,
>
>I've been reading this forum for about a year, and want to thank everybody
>for sharing their knowlege; it has been a real help. I have a question for
>the group:
>
>Is it possible to add a trigger in Perforce, which will disallow any
>commits on a branch, as long as a certain label exists on that branch?
>
>It seems like (if this is feasible) this would allow us to "lock" a branch
>without using p4 protect.
>
>Thanks
>
>Steve
--
Chuck O'Neill
510-529-9299
More information about the perforce-user
mailing list