[Buildbot-devel] Fwd: Using an output .exe from one builder for another

[Amber Yust]

Whoops, forgot to reply-all.

---------- Forwarded message ----------
From: Amber Yust <ayust at yelp.com>
Date: Mon, Jan 24, 2011 at 2:11 PM
Subject: Re: [Buildbot-devel] Using an output .exe from one builder for
another
To: Alex Escott <AE at malaspina-labs.com>


Try the alwaysUseLatest flag to your Source step (assuming that's the
behavior you want).

~Amber


On Mon, Jan 24, 2011 at 2:03 PM, Alex Escott <AE at malaspina-labs.com> wrote:

> Ah yes, that’s what I’m looking for. I’ll give that a go.
>
>
>
> Another issue I’m running into is that the BuilderB does a SVN checkout on
> a different repository than BuilderA (it updates test data, no code). Since
> the sourceStamp is passed on from BuilderA to BuilderB, the SVN checkout
> step fails because it’s looking for rXXX which doesn’t exist in our data
> repository.
>
>
>
> Is there any way to get the triggered build to ignore the sourceStamp? I’ve
> looked at *updateSourceStamp *but that doesn’t seem to do what I’m talking
> about…
>
>
>
> *From:* Amber Yust [mailto:ayust at yelp.com]
> *Sent:* January-24-11 1:53 PM
> *To:* Alex Escott
> *Cc:* buildbot-devel at lists.sourceforge.net
> *Subject:* Re: [Buildbot-devel] Using an output .exe from one builder for
> another
>
>
>
> Depending on how big the built executable is, you might be able to use
> FileUpload and FileDownload steps to transfer it between slaves. Don't do
> that if the executable is significantly large, though.
>
>
>
> ~Amber
>
> On Mon, Jan 24, 2011 at 1:47 PM, Alex Escott <AE at malaspina-labs.com>
> wrote:
>
> Hi all,
>
> I've got 3 buildslaves setup on different machines - they are all capable
> of doing builds, tests, etc.
>
> One of my builders builds an .exe from C++ sources (BuilderA), and another
> builder runs batch unit tests (BuilderB). Problem is, BuilderB needs the
> output .exe from the other build step... so I've set it up so that the unit
> test builder can *ONLY* run on the same slave that runs the compilation
> .exe. i.e. as a first step, it copies the .exe from
> ../../BuilderA/build/<path to exe>. Then it runs the .exe from its own build
> directory. This seems to work (I'm using Triggers) but I think there's a
> better way of doing this?
>
> Thoughts appreciated - thanks!
>
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110124/2474fab9/attachment.html>