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

Slava Imeshev imeshev at yahoo.com
Mon Aug 17 18:00:00 PDT 2009

p4 sync -f a bullet-proof way of having a clean build 
workspace, which is a good idea for release/QA builds.

The problem you have outlined can be easily addressed 
by installing a p4proxy right on the build machine. If
you combine it with adding an option not to update
the have list, the syncs should be pretty fast.

Hope this helps.


Slava Imeshev

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Roy Smith
> Sent: Monday, August 17, 2009 8:14 AM
> To: perforce-user at perforce.com
> Subject: [p4] Is there a way to audit a workspace?
> 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

More information about the perforce-user mailing list