[p4] Is there a way to audit a workspace?

Jeff A. Bowles jab at pobox.com
Mon Aug 17 10:52:41 PDT 2009

It might be helpful to follow up with a couple of related questions:(1) Does
this 'build workspace' have a clean way to remove all derived files
(objects, class files, etc) that is auditable?  Can you really say that
"make / build / ant / etc" against a new-workspace is the same result as
from a cleaned-up workspace?  (For builds where the derived objects are put
into an easily-disposable tree, the answer is "sure". A purist likes the
new-workspace build, and rightly so, but the real question is about making
things easy-to-recreate.)
(2) I assume that "p4 diff -sd" and "p4 diff -se" are helpful, somehow.

As a reminder - don't write a script that loops through a list of files,
running a 'p4' command on each file. There are ways to optimize such things,
so that the requests don't tie up the server's time in bad ways.

Jeff Bowles - jeff at vizim.com

On Mon, Aug 17, 2009 at 8:51 AM, Michael Delaney <mdelaney at upromise.com>wrote:

> You could try to use 'p4 diff' or 'p4 have' to get an what's there and if
> there's anything new.
> Roy Smith wrote:
>> We have a very large workspace where we keep our entire build toolchain
>> (compilers, tools like perl and python, libraries, etc).  Our build team
>> wants to run "p4 sync -f" every day because they don't trust "p4 sync"
>> (without the -f) to keep it up to date.  I'm trying to convince them that
>> this is silly.  It's certainly very expensive, as it takes several hours to
>> complete.  Worse, the act of doing a "sync -f" touches the files on disk, so
>> any build that's currently running can be impacted as files change out from
>> underneath it.
>> Is there some way to have p4 audit the files on disk and confirm that
>> what's there is what's supposed to be there, without actually deleting and
>> re-creating every file?
>> -------------------
>> Roy Smith <smith_roy at emc.com>
>> Software Guy, EMC
>> 1133 Westchester Ave, 3rd floor
>> White Plains, NY 10604
>> +1 914 461 3597
>> AIM: roysmith649
>> _______________________________________________
>> perforce-user mailing list  -  perforce-user at perforce.com
>> http://maillist.perforce.com/mailman/listinfo/perforce-user
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

More information about the perforce-user mailing list