6 messages in com.perforce.perforce-user[p4] building with incremental syncs| From | Sent On | Attachments |
|---|---|---|
| Adrian Kalaveshi | 13 Dec 2004 14:25 | |
| jab | 13 Dec 2004 14:43 | |
| Grills, Jeff | 13 Dec 2004 15:20 | |
| Ken....@thomson.com | 14 Dec 2004 07:10 | |
| Adrian Kalaveshi | 14 Dec 2004 11:55 | |
| Douglas Palmer | 14 Dec 2004 12:00 |
| Subject: | [p4] building with incremental syncs |
|---|---|
| From: | Grills, Jeff (jgri...@soe.sony.com) |
| Date: | 12/13/2004 03:20:19 PM |
| List: | com.perforce.perforce-user |
Validation is pretty quick. The server only needs to send MD5 signatures to the client, and the client has to read each file and compute the signatures and compare them to what the server sent. I have a script in my public directory that handles that, which can be found here:
http://public.perforce.com:8080/@md=d&cd=//guest/jeff_grills/misc/&cdf=/ /guest/jeff_grills/misc/p4consistency.pl&ra=s&sr=3625&c=1I7@//guest/jeff _grills/misc/p4consistency.pl
(or here for a shorter URL):
The script will tell you how your client differs from what the server thinks your client should look like. You could pretty easily pull them back in sync by deleting extra files, and force resyncing different or missing files.
j
-----Original Message----- From: perf...@perforce.com [mailto:perforce-user-admin at perforce.com] On Behalf Of Adrian Kalaveshi Sent: Monday, December 13, 2004 4:26 PM To: perforce-user at perforce.com Subject: [p4] building with incremental syncs
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?
-adrian-
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user