Perforce Cache Online

[mmorse]

Hey Developers,

The public perforce cache (codes.zimbra.com:2666) is back up after the datacenter move & ACL fixes.

Current available branches:
//depot/ZCS/FRANK/
//depot/ZCS/FRANKLIN-506/
//depot/ZCS/FRANKLIN-507/
//depot/ZCS/FRANKLIN-508/
//depot/ZCS/FRANKLIN/
//depot/ZCS/main/

Building Zimbra using Perforce - Zimbra :: Wiki & Franklin README - Zimbra :: Wiki

Example sync against yesterday's 5.0.x code:
p4 -u public -P public1234 -c public-view sync -n //depot/zcs/FRANKLIN/...@2008/07/17:13:49:17
-n just let's you see the changes
-f is force sync

[dijichi2]

great stuff, thanks.

is there a way to diff sync against current codebase like cvs/svn? i think if you do a sync without -f it does updates what has changed since the checkout, and if lots of people use the public account it's meaningless. so we have to do -f for each checkout and can't merge changes etc.

[brian]

create a new client and you won't have to worry about the state of the public-view client.

p4 client -t public-view brian-public-view

[mmorse]

Though last I checked I think we had only 5 licenses on that box; if that's the case I think some of the 'things you could do' were to use a BUILD_HOME/Root/AltRoots that everyone would have, or leave the host blank, or remove client workspaces server side when you're done I guess... (Should be client -d to remove old.) I remember creating dev1-4 on there but certainly don't care if you remove them in favor of another.