[Buildbot-devel] Handling changes in included files to master.cfg

Ben Hearsum bhearsum at wittydomain.com
Tue Sep 11 18:28:55 UTC 2007


I assume that you're just doing an 'from foo import *' to include 
additional files. Doing this should solve your issue:
import foo
reload(foo)
from foo import *

Kenneth Lareau wrote:
> Recently I refactored the master.cfg file we use at my company as it had
> become a bit difficult to follow; part of the solution was to break out
> sections of data (machines and what is built on each) and step infor-
> mation into separate files, making things far more maintainable as well
> as readable.
> 
> This has led to one minor issue; when I want to add/remove a builder
> from one of the buildslaves, I edit the data (data.py) file.  Previously
> with this information in the master.cfg file, I simply did a 'buildbot
> sighup .' and the new builder would show up, but with the refactoring
> the only way I can seemingly accomplish this is to do a full stop and
> restart of buildbot.  Normally this wouldn't be a big issue if it wasn't
> for the fact that we have 21 buildslave with 163 builders that take up
> to 10 minutes to stop and restart properly, as well as a set of builders
> that run nearly 16 hours a day (and really can't be interrupted) which
> highly limits when I can perform the restart.
> 
> So my question is... is there a way to accomplish what I need to do
> without doing a full stop/restart of the master buildbot process, and
> without re-merging the new files back into master.cfg?  Or am I pretty
> much stuck at this point?
> 
> 
> Ken Lareau
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
> 




More information about the devel mailing list