[Buildbot-devel] Ignoring offline builders/slaves

[Pierre Tardy]

Its not an easy problem.

My first idea would be to have a custom trigger step which would skip some
of the builders, if the slaves are disconnected.
That would be very hacky, but may work for you.


Le ven. 13 mars 2015 à 02:50, Jason Edgecombe <jason at rampaginggeek.com> a
écrit :

> Hi Jim,
>
> As a volunteer project, we have some challenges with getting enough
> slaves to cover the desired OS's, let alone having redundant slaves.
> Even if we had redundant slaves, I doubt that we would have identical
> slaves. Your're correct in that I want to relax the constraints on
> either the Gerrit status plugin or alter the Gerrit scheduler to use a
> dynamic pool.
>
> Thanks,
> Jason
>
> On 03/12/2015 01:19 AM, Jim Rowan wrote:
> > Jason,
> >
> > Many of your builders have only one buildslave that is servicing that
> builder.  If that buildslave is offline, then that build can’t proceed.
> The normal way to avoid this is to have more than one buildslave servicing
> each builder.  If one of them is down, one of the other slaves will handle
> it.   This doesn’t really have anything to do with gerrit.
> >
> > You have a policy coded in your config that all the builds for a
> particular change have to succeed in order to gain a +1 verified vote in
> gerrit.  Your goal seems to be to relax that policy such that only some
> subset of builds are required.   I can’t think of a particularly reasonable
> way to do that.
> >
> > The fundamental problem is that GerritStatusPush won’t call it’s summary
> callback until all of the builds in the buildset have completed.  If some
> of the builds are blocked, you’re stuck waiting.
> >
> > I suppose the most straightforward way to approach this is to write a
> custom scheduler that dynamically checks to see which of the builders have
> at least one buildslave that is online at the time a change comes in, and
> to only trigger those, rather than the whole list.   Another approach might
> be to have something that recognizes when builds are queued for builders
> that have no online buildslaves, and to cancel those builds.   (I’m not
> sure that is effective in removing them from the buildset …but  that’s the
> objective.)
> >
> >
> >
>
>
> ------------------------------------------------------------
> ------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> 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/20150313/8e1704d1/attachment.html>