[Buildbot-devel] Forcing on a given buildslave

Pierre Tardy tardyp at gmail.com
Wed Sep 12 16:27:54 UTC 2012


Hi georges,

You can see this pull request, that has the proposal of solution for this
problem

https://github.com/buildbot/buildbot/pull/523

It has example code in the doc for your particular problem, but the
solution is flexible enough to handle mines,

for example I use this in my conf:

def myNextBuildSlave(builder, slavebldrs, buildrequest):
    #first check on location
    location = buildrequest.properties.getProperty('preferred_site')
    variant = buildrequest.properties.getProperty('variant')
    if variant == "autobuild":
        return cfg.random_slavebldr_or_none_by(unlockedSlaveBldrs,
                                               location=location,
                                               speed="slow")
    elif variant in ["maintainers",
"engineering","mergerequest","weekly","latest"]:
        choosenslave = cfg.random_slavebldr_or_none_by(unlockedSlaveBldrs,
                                                       location=location,
                                                       speed="fast")
         # in the maintainer, engineering case, we should not be so peeky
about speed..
        if choosenslave == None and variant in ["maintainers",
"engineering"]:
            choosenslave =
cfg.random_slavebldr_or_none_by(unlockedSlaveBldrs,

 location=location)
        return choosenslave

Regards,
Pierre


On Sun, Sep 9, 2012 at 10:04 PM, Pierre Tardy <tardyp at gmail.com> wrote:

>
>> Pierre: any chance to see your code, even if not ready for proper
>> integration ?
>>
> That's my next thing on my upstreaming plate. I hope to pull request
> something this week or the week after.
>
> Regards,
> Pierre
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20120912/8f3429a8/attachment.html>


More information about the devel mailing list