[Buildbot-devel] P4Sync / P4, etc.

Alex Escott AE at malaspina-labs.com
Tue Apr 2 23:57:11 UTC 2013

Sounds exactly like what I'm looking for... will take a peek, thanks a lot.

From: Bill Deegan [mailto:bill at baddogconsulting.com]
Sent: April-02-13 3:42 PM
To: Alex Escott
Cc: buildbot-devel at lists.sourceforge.net
Subject: Re: [Buildbot-devel] P4Sync / P4, etc.


I've got a pull request in for a new master side P4 source step which may take care of your needs.

You can specify a tuple of tuples of depot/client mappings to make your client spec.

On Tue, Apr 2, 2013 at 1:18 PM, Alex Escott <AE at malaspina-labs.com<mailto:AE at malaspina-labs.com>> wrote:
Hi all, I'm on 0.8.3. I've got a build that requires P4 workspace with more than one mapping path (the build pulls from about 4 places, vendor branches, etc.). The stock P4 buildstep creates a client spec based on a root depot path and does an update. Since it's only one path, I can't use it.

So I'm using P4Sync and manually creating the workspace, which is ok... but it copies the whole tree from <builder_name>/source to <builder_name>/build every time it syncs, overwriting all the files. This means my "quick" incremental builds are now slow full ones.

Any suggestions on how I should do things differently? I was thinking I'll just not use the Buildbot build step and just do a shell command for the update portion.

Thanks -


Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
Buildbot-devel mailing list
Buildbot-devel at lists.sourceforge.net<mailto:Buildbot-devel at lists.sourceforge.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20130402/d65fab79/attachment.html>

More information about the devel mailing list