[Buildbot-devel] Force scheduler and codebases

[Hugh Sorby]

Hi All,

I'm looking for some help as to what is going wrong with my setup, all information and insight is greatly appreciated.

my setup (obviously not valid Python code but hopefully it conveys the situation):

force_scheduler = ForceScheduler(name=bob, codebases=[name=dan])

triggerable_scheduler_1 = TriggerableScheduler(name=1, builders=[test])
triggerable_scheduler_2 = TriggerableScheduler(name=1, builders=[compare])
triggerable_scheduler_3 = TriggerableScheduler(name=1, builders=[evaluate])

f = factory.addStep(Trigger(scheduler=triggerable_scheduler_1))
f = factory.addStep(Trigger(scheduler=triggerable_scheduler_2))
f = factory.addStep(Trigger(scheduler=triggerable_scheduler_3))

test_factory = compare_factory = evaluate_factory = factory.addStep(Git(repourl=Property(repository, default=http://somewhere)))

test = BuilderConfig(name=test, factory=test_factory)
compare = BuilderConfig(name=compare, factory=compare_factory)
evaluate = BuilderConfig(name=evaluate, factory=evaluate_factory)
all = BuilderConfig(name=all, factory=f)

What I am trying to do is allow the force scheduler to trigger the  all BuilderConfig which in turn triggers the triggerable schedulers to run the test, compare, and evaluate BuilderConfigs.  But when the triggered build starts the first step which is a git step, it says there is no codebase named 'dan' and fails.  If I skip the intermediate BuilderConfig all and get the force scheduler to activate the test, compare, and evaluate BuilderConfigs directly it works i.e. the codebase named 'dan' is known.

So my question is what is stopping the ForceScheduler from getting the 'dan' codebase through to the test, compare, and evaluate BuilderConfigs in the first scenario?

Many Thanks,
Hugh.