WIthProperties uses properties from builders, schedulers and slaves

[hollowman]

In order to customize steps, we should be able to have external properties depending on the builder, schedulers or slaves.

For example, if I want to use the same builder on different platforms, I may wish to use slave dependent properties/options for my steps.

Furthermore, I sometimes might want to do a full build with a full checkout.

   slave('linux1','pw1',properties={'os':'linux','arch':'x86','p':'32'})
   slave('linux2','pw2',properties={'os':'linux','arch':'ia64','p':'64'})
   slave('aix1','pass',properties={'os':'aix','arch':'ppc','p':'64'})

   scheduler(...,properties={'clean','none'})
   scheduler(...,properties={'clean','libs'})
   scheduler(...,properties={'clean','full'})

    
   addStep(...,["make",WithProperties("%s","clean")])
   addStep(...,["build",WithProperties("%s","os")]
   

[warner]

I like it. I'd also like to have the 'buildbot force' command (which doesn't quite exist yet) to let you set properties too.

[gward]

Doesn't ticket #87 (custom build properties) address this request? (That is, I think this ticket is a duplicate.)

[dustin]

gward, yes, it overlaps signficantly with #87. What #87 doesn't include is specification of properties from slaves, schedulers, and steps. Schedulers are set to be added in #87, but let's keep this ticket open for sourcing properties in steps and slaves, as that's somewhat more challenging, and requires some additional thought.

[gward]

Ahh, got it. I did not fully understand this feature request when I first looked at it. I retract my "isn't this a dupe?" comment.

[dustin]

I think I'm going to move that work into #87, though, since there are some loose ends still to tie up on that bug.