[p4] Release branch protection
sshort at tabula.com
Thu Mar 13 09:47:58 PDT 2008
Can you explain that last sentence?
From: perforce-user-bounces at perforce.com [mailto:perforce-user-
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 ---
> 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
> we want, but we have some questions about it.
> 1) "p4 protect" can only be run by super-users. What we would like to
> have our Python build scripts protect the release branches when they
> completed. However, several users can be running build scripts at the
> time - building independent components. It would be ideal if the build
> scripts could 'protect' the release branches, yet the build scripts
> 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
> table could get large (we would have an extra entry for each release
> branch). I considered using wildcards to protect all release branches
> a single line in the protection table, but that prevents creation of
> new release branches.
> Question: Will this impact performance if our protection table gets
> Any suggestions?
> perforce-user mailing list - perforce-user at perforce.com
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user