[p4] Removing old files generated by Nightly Builds
william_ivey at bmc.com
Tue Aug 7 13:37:18 PDT 2007
The 2007.2 version supports a +Sn file type where n is the number
of revisions you want to keep. Previous versions only supported
a "keep latest" revision type, +S, but even that would do what
you want if you only need the head revision.
For build output we use a separate p4d server with lots of cheap
disk storage. That can be an option as well, although it may not
be as convenient depending on how you use the build output. (It's
great for complete, installable images, but not very convenient
for libraries and such.) It uses P4AUTH to authenticate off our
main server so any user with an account on the main server also
has one on the build product server.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Hugo Krapf
Q. What's the suggested method for removing Nightly Build generated
files? Obliterate them?!
I am new to Perforce. I've bought Laura Wingerd's "Practical Perforce".
In chapter 8, she talks about Nightly Builds, and check-ins of generated
files, and how to tag them with a rolling label.
I understand the reason behind checking-in generated files ("developers
can have up-to-date versions of shared libraries and other generated
files without having to build everything themselves"), but... it strikes
me as odd to keep all those generated files in the depot forever, even
after rolling the label to a new build!... If the nightly label is
moved to new files, there's no reason to keep the old ones, right?
Thanks in advance for any info.
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user