[Buildbot-devel] buildbot-0.6.2: need to change master.cfg?

Justin Mason jm at jmason.org
Tue Dec 14 17:37:47 UTC 2004

Hash: SHA1

Brian Warner writes:
> > > BTW, I'm seeing these errors using my 0.6.1 master.cfg with 0.6.2:
> > 
> > fixed, patch below.  However, I still get errors from all the slaves;
> > is it necessary to recreate slave directories every time buildbot
> > is upgraded?   (I'm about to try deleting and recreating one now.)
> Well, sometimes. Specifically it may be necessary to re-create the .tap file
> on each upgrade (in general you can leave the rest of the directory alone).
> Sometimes I try to avoid that requirement: the ideal fix would either be to
> add 'bots' as a class-level attribute, or to bump the styles.Versioned number
> and provide an upgrade method. However, ever since the build status was moved
> out of the buildmaster-shutdown.tap file, the need to keep a .tap around has
> gone away, so I haven't been as conscientious about maintaining an upgrade
> path for old .taps. This sort of problem happens when new attributes are
> added: the old serialized application instance doesn't have them, the new
> code expects them to be in place.
> In the case of 0.6.2, you need to re-create both the master and the slave
> taps upon upgrade. One way is to run 'buildbot master --force
> /PATH/TO/MASTER' and such. Another way is to run mktap directly. For the next
> release, I plan to add a 'tap' target to the convenience Makefile which will
> re-create the .tap file using the same arguments that were used originally,
> which should make this somewhat more straightforward.
> Sorry for the inconvenience. I could either put more energy into making old
> taps usable with newer code, or I could put more energy into mentioning the
> occasional need to re-create the .tap files in the docs. Thoughts?

hmm -- I think if it was clearer that they needed to be recreated,
and a quick command to do that, that'd do...   it was a bit of a surprise
to me, that's all. ;)

- --j.
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS


More information about the devel mailing list