[Buildbot-devel] Triggerable getting triggered but stays in idle state

[Amber Yust]

Hm. I have a similar setup on one of our buildbots (one build that triggers
~5 others, waits for those to complete, and then continues), and it seems
work work fine. We're currently running 0.8.3 though, so I'm not sure if
it's an issue with 0.8.2 that you're experiencing, or some other factor?

~Amber

On Fri, Feb 11, 2011 at 9:15 AM, Andreas Johnsson <
andreas.johnsson at tarsier.se> wrote:

> First let me explain what i'm trying to do:
> I'm trying to build 6 different build factories and when all those are
> completed I
> want a final build factory with build steps to run.
>
> What I did was to set it up like this:
> * Scheduler A gets triggered by a poller (P4)
> * Scheduler A has a trigger.Trigger build step that triggers Scheduler B
> which is a triggerable.Triggerable.
>    the trigger is set up with waitForFinish=True
> * Scheduler B contains the 6 build factories
> * When the trigger build step is completed in Scheduler A (i.e. Sceduler B
> is completed)
>   a final build step is run (packaging).
>
> The problem I have is that when A triggers B, B gets triggered and a build
> step is triggered BUT
> ends up in idle state (and just sits there indefinitely). However, if I set
> waitForFinish=False the B's build steps is executed without any problem, but
> that makes the last build step in A executing directly instead of waiting
> for B's build steps to be completed.
>
> I run on windows with version 0.8.2 of buildbot.
>
> Also, there seems be no feedback from the trigger to see if the build steps
> in B failed or succeeded (like in the Dependent scheduler). Not a big
> problem, but that would be helpful information of course.
>
>
> Thank you for your help.
>
> //
> Andreas
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> 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/20110211/0b5facb5/attachment.html>