[Buildbot-devel] Multiple upstreams for Dependent scheduler

Quentin Arce qarce at yahoo.com
Tue Dec 4 19:17:45 UTC 2012

I would like to second the desire to have a multi dep build system.
This is the sort of thing needed to implement build workflows for products that include multiple build results.

 From: Andy Salnikov <a_salnikov at yahoo.com>
To: Buildbot <buildbot-devel at lists.sourceforge.net> 
Sent: Tuesday, December 4, 2012 11:06 AM
Subject: [Buildbot-devel] Multiple upstreams for Dependent scheduler

I'm trying to setup new build system with buildbot and one thing that I'd
like to do for it is to run some action when "all" builders have finished.
Dependent scheduler seems to the kind that I need, but its limitation
is that it only depends on a single upstream scheduler while I want to
wait for multiple schedulers (running in parallel) to finish. Would it be
possible to extend the Dependent scheduler to support multiple upstream
schedules (with an "AND" logic)? I gather this could be useful for other
people as well, I of course could (and maybe would) implement my own
scheduler but having this in standard code base could be useful.

Another thing that I'd like to have in Dependent scheduler is "forwarding"
of the properties (all or selected subset of them) from the upstream
scheduler. I have a special nightly scheduler which defines some special
properties used throughout the system. With that I had also subclass a
Dependent scheduler to pass properties defined in the nightly scheduler
down to the builders. Simpler solution that does not need subclassing
would be preferable to me.


LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
Buildbot-devel mailing list
Buildbot-devel at lists.sourceforge.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20121204/ce40e65c/attachment.html>

More information about the devel mailing list