Dave Lewis <dlewis at vignette.com> writes:
I have of late taken to saving the have list when building a client
for our nightly build. The thought was that after saving the client
definition in a file, and the have list, it would be easy to archive
the build tree and later restore it and the client state. (assuming
the client was deleted in the intervening period)
This is all fine, but the restore process would also make it re-get
all the files as specified in the have list. (this would make an
incremental build impossible or difficult)
I realized recently that this could be "fixed" by feeding the have
list to p4 flush instead of p4 sync.
Anybody see any problems with this?
After doing so, you might want to refresh any files that p4 diff -sd
and -se report. Otherwise, no.
I wonder though, why don't you just keep the client around for the
next nightly build? What we do here is have the script do a "p4 sync"
on a dedicated "nightly build" client. If any files got changed, the
night make fires off.
---
matta
5 messages in com.perforce.perforce-userrestoring deleted client
