[Buildbot-devel] ForceScheduler and property order-of-precedence
agentm at themactionfaction.com
Wed Feb 11 19:01:39 UTC 2015
We have hit a case where the property order-of-precedence application isn't
practical. The order is documented here:
"If the same property is supplied in multiple places, the final appearance
takes precedence. For example, a property set in a builder configuration
will override one supplied by a scheduler."
For the ForceScheduler, however, this doesn't seem to make sense as in the
test_factory = BuildFactory()
test_builder = BuilderConfig(name='force_sched_test',
test_scheduler = ForceScheduler(name='f_sched',
In this case, "test_property", set by the ForceScheduler, is effectively
ignored when the ForceScheduler is forced because the property's value is
superseded by the BuilderConfig's "test_property" while "test_property2"
can be set by the ForceScheduler as desired.
In all cases, what we would like is for the properties set by the
ForceScheduler (usually a human) to override what we view as the
BuilderConfig's defaults. This is useful, for example, when QA is testing
something new and want to kick off a slightly different build through the
ForceScheduler. We can empty the BuilderConfig of properties, but then we
have to pass these properties from every invoking scheduler, which seems
Basically, we want BuilderConfig properties which apply as defaults only if
nothing else sets them.
Is there an obvious workaround which we are missing?
Thanks for any advice.
More information about the devel