greg ward lsnognqkknnbnwqhgmailcom nov 19 2007 1123 stefan seefeld wrote suggested way share buildsteprelated data among builders master config file dont know official recommended best practice using good oldfashioned procedural abstraction eg mastercfg build trunk several recent release branches branch requires three builders linuxsetup windowsmain linuxmain avoid tedious repetition something like def create_setup_factorycheckout_source_opt bfactory mybuildfactory bfactoryaddstepshellshellcommand namecheckoutprojectslinux commandcheckoutprojects cvsroot checkout_source_opt build haltonfailuretrue workdir setup build steps build_factoriessetuptrunk create_setup_factoryltrunk branch active_branches build_factoriessetupbranch create_setup_factoryls branch likewise functions create_windows_main_factory create_linux_main_factory used populate dictofdicts build_factories fully populated build_factories many buildfactory objects stitch together buildbot def create_buildersname name branch name trunk return name setups name slavenames linux_slave builddir setups name factory build_factoriessetupname locks linux_slave_lock name windowsmains name slavenames windows_slave builddir windowsmains name factory build_factorieswindowsmainname locks windows_slave_lock name linuxmains name slavenames linux_slave builddir linuxmains name factory build_factorieslinuxmainname cbuilders create_builderstrunk branch active_branches cbuilders create_buildersbranch said find generates confusing waterfall page 9 builders today future add branches im hoping drastically simplify custom build properties patch ticket 87 fingers crossed greg fri 08 aug 2008 082849 0500 buildbotdevel sharing buildsteps