Will give it a try tomorrow then ;) On a side not: on Win am I better off spinning up a Linux box to hack away?
On Thu, Mar 3, 2016 at 3:41 PM, Pierre Tardy <[email protected]> wrote: > Oh yes it's very feasible and would be a nice be feature! > > Le jeu. 3 mars 2016 15:40, Francesco Di Mizio <[email protected]> > a écrit : > >> I know it's not yet possible but I can make it work I believe. >> >> If you mean it's not possible code-wise, then I'll just take your word. >> >> On Thu, Mar 3, 2016 at 3:38 PM, Pierre Tardy <[email protected]> wrote: >> >>> Unfortunately this is not possible yet. >>> >>> The solution is to make two trigger steps. >>> The first with waitforfinish = false and containing your optional tests >>> >>> Le jeu. 3 mars 2016 15:32, Francesco Di Mizio < >>> [email protected]> a écrit : >>> >>>> when specifying the scheduler names to kick, I'd like to choose which >>>> ones are crucial, as in they're going to fail the step if they fail. >>>> >>>> So something like >>>> >>>> Trigger( >>>> ..... >>>> schdulerNames = [ >>>> ("sched_1", will_fail_the_step = False) >>>> ("sched_2") # will_fail_the_step defaults to True >>>> ], >>>> other ctor params >>>> ) >>>> >>>> and this would also affect getSchedulersAndProperties(). and which >>>> would have to return a list of tuples with one more True/False param. >>>> >>>> I am just gonna work on this though if it's something you pips think >>>> might be a 'good to have' as I do not want to have custom code. >>>> >>>> >>>> Cheers! >>>> >>>> _______________________________________________ >>>> users mailing list >>>> [email protected] >>>> https://lists.buildbot.net/mailman/listinfo/users >>> >>> >>
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
