[Buildbot-devel] Waiting for two builders to finish before triggering a third

[Amber Yust]

Philippe's suggestion is also what I would recommend.

~Amber

On Thu, Jul 7, 2011 at 12:27 PM, Philippe McLean
<philippe.mclean at gmail.com>wrote:

> (a suggestion)
>
> introduce a new builder A that is scheduled by commits.
> A has steps:
>
> 1. trigger [X, Y], wait for finish
> 2. trigger T, wait for finish
> 3. report
>
> The waterfall display will look a bit more confusing but A would be your
> 'master build'.
>
>
>  On Thu, Jul 7, 2011 at 12:00 PM, Alec Douglas <AD at malaspina-labs.com>wrote:
>
>> Hello,****
>>
>> ** **
>>
>> My problem is as follows: I have two builders (let’s call them X and Y)
>> that are triggered simultaneously when code is committed. X and Y build two
>> different versions of the committed code. I also have a third builder (call
>> it T) that runs tests on both versions which is currently triggered on the
>> completion of X. The problem is, it is difficult to guarantee that Y has
>> finished before T begins, and if the tests are run before Y is done then the
>> tests will fail unnecessarily (by that I mean: failing based on not being
>> built yet, not based on a problem in the code). ****
>>
>> ** **
>>
>> What I would like to do is only have T run after *both* X and Y have
>> finished. ****
>>
>> ** **
>>
>> I would like to refrain from simply moving the buildsteps from Y onto X,
>> as the builds take a bit of time and running them sequentially instead of
>> simultaneously would slow things down considerably. I would also like to
>> avoid splitting the tests into two builders (T1 running on X and T2 running
>> on Y), as that would cause a great deal of bloat.****
>>
>> ** **
>>
>> Any suggestions?****
>>
>> ** **
>>
>> Thanks,****
>>
>> Alec Douglas****
>>
>>
>> ------------------------------------------------------------------------------
>> All of the data generated in your IT infrastructure is seriously valuable.
>> Why? It contains a definitive record of application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2d-c2
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> 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/20110707/b7699c69/attachment.html>