[Buildbot-devel] Multiple upstreams for Dependent scheduler

[Andy Salnikov]

Hi Charles,

thanks for pointing out Triggerable option. I never used that before and
needed tolearn how it works. My impression that it should work well
even though configuration may become a bit more complex.

Meantime I wrote simple MultiDependent scheduler for myself, it works
but it's not very trivial. If anybody is interested I could post it here.

Cheers,
Andy

On 12/4/2012 5:23 PM, Charles Lepple wrote:
> On Dec 4, 2012, at 2:06 PM, Andy Salnikov wrote:
>
>> 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.
> Can you make the upstream schedulers into Triggerable schedulers, and have another builder trigger those schedulers synchronously? Then, after the Trigger step, you perform the action that depends on all of the other actions.
>
> Scheduler:
>
> http://buildbot.net/buildbot/docs/current/manual/cfg-schedulers.html#triggerable-scheduler
>
> Trigger step:
>
> http://buildbot.net/buildbot/docs/current/manual/cfg-buildsteps.html#triggering-schedulers
>
>> 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.
> I haven't used the set_properties option with Interpolate, but the older copy_properties worked for me.
>