[Buildbot-devel] errors after upgrading 0.7.4 -> 0.7.6

Brian Warner warner-buildbot at lothar.com
Wed Nov 21 23:59:09 UTC 2007

On Fri, 16 Nov 2007 14:13:19 -0600
Timothee Besset <ttimo at idsoftware.com> wrote:

> I upgraded my bbot install to 0.7.6 and restarted my masters:
> First had to figure out that I needed to copy the new public_html/
> directory. There should be an 'upgrading' section somewhere mentioning
> that kind of stuff.

The first paragraph of the NEWS file lists the following:

 * Release 0.7.6 (30 Sep 2007)
 ** Things You Need To Know
 *** 'buildbot upgrade-master'
 Each time you install a new version of Buildbot, you should run the new
 'buildbot upgrade-master' command on each of your pre-existing buildmasters.
 This will add files and fix (or at least detect) incompatibilities between
 your old config and the new code.

I'll see about changing the README and the buildbot.net front page to make
this file more prominent, as well as add some pointers in the user's manual.
In general, each time you install a new buildbot release, please read the top
of the NEWS file to find out what has been changed and how you need to deal
with those changes.

In this case, the 'buildbot upgrade-master' command will copy those
public_html/ files into your buildmaster directory, as well as informing you
about the c['bots'] and c['sources'] changes.

The NEWS file for 0.7.5 also described the buildbot.process.step ->
buildbot.steps change that Benoit mentioned.

In general, I'd recommend upgrading to the latest buildbot version one
release at a time. I make it a policy to provide deprecation warnings for
features that are to be removed for a few releases before actually removing
them, and upgrading partway first will give you a chance to see those
warnings and update your config to match.

> Next I had an error when clicking on one of my builders:
>             values = {'class': css_classes[results],
>         exceptions.KeyError:

Yeah, I think I'm going to try to release 0.7.7 in the beginning of December
to get this fix into a real release (as well as a few other really annoying


More information about the devel mailing list