[Fwd: Re: [p4] building with incremental syncs]

--
quis custodiet ipsos custodes -- Juvenal VI 347-8

--- Begin Message ---

Subject:	Re: [p4] building with incremental syncs

Adrian Kalaveshi wrote:

I see that this topic, in various forms, has been discussed in the past
but I thought I'd bring it to the surface again.  When building from
source files stored in Perforce, it seems the most sane to completely blow
away the contents on your local disk.  Optimizing for speed, I perform
these steps roughly like this:

  p4 flush ...#none
  rm -rf $BUILD_ROOT

After syncing to a changelist, I can be certain that what I'm building
with is exactly the same as what's in Perforce.  I have a need to make
this process faster, though.  I'd like to incrementally sync to a cache
area on the local disk and then copy it over to the $BUILD_ROOT.  Before
copying over, I'd like to validate the contents of the cache.  What's the
best way to do this while making sure that the validation step doesn't
consume more time than the transfer from Perforce would have been in the
first place?

Why not simply run a p4proxy instance on the build machine? That way, when you blow away your client and resync, the vast majority of the files will simply be copied from the local proxy cache, and since it's all under Perforce control, you don't (theoretically) have to worry about verification. Has anyone tried this?

Tony.

-adrian-
_______________________________________________
perforce-user mailing list  -  perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user

--
quis custodiet ipsos custodes -- Juvenal VI 347-8

--- End Message ---