[p4] Release branch protection

Stephen Vance steve at vance.com
Thu Mar 13 06:50:55 PDT 2008

Put all of your release branches under a common directory in the 
Perforce server and protect that directory with a single protection 
line. Remember, the physical storage for your branches does not need to 
mirror the logical topology of them.


michael.kuitunen at kodak.com wrote:
> Relative Perforce newbie here.
> Our team builds several software 'components' which can be 'released'
> independently. This means we will have a lot of 'release' branches --- many
> components with many releases of each.
> What we would like to do is to protect our 'release' branches from
> accidental checkouts and code modifications. "p4 protect" looks like what
> we want, but we have some questions about it.
> 1) "p4 protect" can only be run by super-users. What we would like to do is
> have our Python build scripts protect the release branches when they are
> completed. However, several users can be running build scripts at the same
> time - building independent components. It would be ideal if the build
> scripts could 'protect' the release branches, yet the build scripts are not
> being run by super-users.
> Question: Any ideas on how we could handle this requirement?
> 2) If we did 'protect' each release branch, it sounds like our protection
> table could get large (we would have an extra entry for each release
> branch).  I considered using wildcards to protect all release branches with
> a single line in the protection table, but that prevents creation of any
> new release branches.
> Question: Will this impact performance if our protection table gets large?
> Any suggestions?
> Thanks,
> -Mike-
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

Stephen Vance

More information about the perforce-user mailing list