[users at bb.net] Trigger new build/scheduler when two related builds are finished

[Ulrich Teichert]

Hi,

[don't know about the idsDeferred and triggers - deleted this part]

>As mentioned earlier, the Dependent scheduler is not useful, not just
>because it cannot limit the waiting to a fewer builders than all for the
>upstream scheduler, but actually the Dependent scheduler is IMO *useless*
>for any production environment except a single branch environment. Normal
>projects will tend to have *multiple* release branches (just consider a
>project with an alpha, beta, and stable branches, or  a Linux distro
>maintaining multiple LTS releases, and we ourselves have multiple release
>branches for various product lines, normally three for the platform I am
>working on for this project). This means that the Scheduler needs to be
>aware of everything going on in the parent scheduler, including the
>properties and sourcestamp(s) of the resulting builds.
[del]

Well, I don't know if the dependent scheduler should know about
everything of the upstream scheduler, but when the properties
of the upstream scheduler would be available in the dependent scheduler,
that would be good. I looked into that briefly (my idea was to copy the
properties and prefix the keys with "upstream.") but I got lost in the
property class... I fixed my problem with some shell scripting in the end,
but it remains fragile.

Sorry that I can not provide a solution, but at least you know that you're
not alone ;-)

CU,
Uli

Mit freundlichen Grüßen / Kind regards

Dipl.-Inform. Ulrich Teichert
Senior Software Developer

kumkeo GmbH
Heidenkampsweg 82a
20097 Hamburg
Germany

T: +49 40 2846761-0
F: +49 40 2846761-99

ulrich.teichert at kumkeo.de
www.kumkeo.de

Amtsgericht Hamburg / Hamburg District Court, HRB 108558
Geschäftsführer / Managing Director: Dipl.-Ing. Bernd Sager; Dipl.-Ing. Sven Tanneberger, MBA