verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
<dol-sen> Foxboron, you need to launch them all in the same trigger step
<dol-sen> not using a for loop in the factory code
<dol-sen> that is because the data you pass it is future data that the factory does NOT have when the code is booted at master boot time
<dol-sen> the only way you can use a for loop is inside a custom step or scheduler
<dol-sen> that code will run using run time data, not boot time data
<dol-sen> a for loop in factory definition is boot time only and can be useful, but it will never have run time data that can be used at boot time
koobs has quit [Ping timeout: 246 seconds]
<dol-sen> you may need to sub-class a scheduler to start the list of builds with some custom code to do exactly what you want
<dol-sen> I did that some years ago to start a list of jobs, then create a new list of successes from those to use in another scheduler to run the tests on those from previous builds scheduler
koobs has joined #buildbot
jcbsv has joined #buildbot
<Foxboron> Right, this makes sense. Thanks dol-sen
vladbogo has joined #buildbot
vladbogo has quit [Quit: Connection closed for inactivity]
jcbsv has quit [Quit: Textual IRC Client: www.textualapp.com]
ska has joined #buildbot
alicef has quit [Quit: install gentoo]
alicef has joined #buildbot
<dol-sen> Foxboron, no problem. It took me some time to wrap my head around this. get things working properly.
<dol-sen> If you do any C programming, think of the factory definition as compiler directives. those factory.add_step() are only ever run at master boot time like the #ifdef... in a compiler
<dol-sen> it changes the final compiled code, but does not ever contain run time data for the #ifdef...
<Foxboron> You are trying to describe macros :p
<Foxboron> But they are more a lisp thing then they are C things really
<dol-sen> yeah, macros
<dol-sen> eg you can pass the factory a variable(s) to add the same step or group of steps x times in a for loop. The result will show x number of steps in the running builder
<dol-sen> that way you don't need to copy/paste the step x times in a row
<dol-sen> Foxboron, another alternative might be to make use of the dynamic addStep(). I've never used it myself, but it can add steps dynamically using run time data