[Buildbot-devel] buildbot-0.6.4 released

[Paul Warren]

Brian Warner wrote:
> I just finished releasing buildbot-0.6.4, which addresses the major bug that
> rendered 0.6.3 useless for new buildmaster installations. Sorry about that.
> 
> The release is available from the sf.net download page, accessible off
> http://buildbot.sourceforge.net/ as usual. It is signed with my GPG key
> (0x1514A7BD), and the md5/sha1 checksums are:
> 
>   md5: f04ca9e6eefad3992d37ef3537609e63  buildbot-0.6.4.tar.gz
>  sha1: 59f29f89ba5e1f19e83f3cc9c78ff96dfc07a12e  buildbot-0.6.4.tar.gz
> 
> In addition to this major bug, some less-significant ones were fixed. A
> number of non-fatal exceptions that occured during status updates were
> resolved, and the last couple of unixisms were removed, allowing most of the
> unit tests to pass under win32.
> 
> 
> win32 compatibility:
> 
> I finally installed a python/windows environment on my own machine, which (in
> addition to the amazing support of many participants on this list) has helped
> speed up the resolution of win32 compatibility issues. In 0.6.4, as long as
> you use '-r win32' (to get the win32reactor instead of the default one), all
> unit tests pass but one. test_web.WebTest.test_pathName_port fails under
> win32reactor, but strangely enough not the default one. I'm pretty sure this
> failure will not affect buildbot operations. I'm also pretty sure it's a
> Twisted bug. Investigations continue, and if I can characterize it better
> then I'll file a Twisted bug report about it, hopefully it can get fixed by
> Twisted-2.0.1 .
> 
> We've also changed the way commands are run under windows. As of 0.6.4, even
> list-based commands (those specified with an array of argument values, rather
> than one big string in need of splitting) are run with cmd.exe (or, rather,
> os.environ['COMSPEC']). I *think* this will improve matters (it allows the
> command to be searched on your PATH, for one). Please let me know.
> 
> I've taken Bear's installation notes, added a few of my own, and put the text
> in README.w32 . Perhaps it will be useful for future buildbot+windows folks.
> Please send fixes and additions: I'm the *last* person you want providing
> advice on how to run things under windows :).
> 
> 
> .buildbot directories:
> 
> The 'buildbot' tool has two subcommands (statusgui and debugclient) which
> need to talk to a buildmaster. Those subcommands now look for a .buildbot
> directory to find an 'options' file which can provide a default location for
> the buildmaster. The tool looks for this .buildbot directory in the current
> directory and all parents, and also in ~/.buildbot . (As a security
> precaution, it only looks in directories that you own).
> 
> The idea is that for each project you can put a .buildbot/options in the
> tree, and then when you're curious about how that buildbot is going, you just
> type 'buildbot statusgui'. In the next release the 'force' and 'watch'
> commands will probably make an appearance, and eventually the 'try' feature
> will use the same mechanism.
> 
> 
> Complete release notes are attached below. As usual, all bugs and questions
> should be sent to the buildbot-devel list.
> 
> Have a pass-the-brown-paper-bag day,
>  -Brian


Fixes my problems, thanks for the hard work Brian!

Cheers
-- 
Paul Warren                    |   UIN: 10374690
u3292467 at anu dot edu dot au |   MSN: qvack4 at hotmail.com
pwarren.homelinux.org          | SKYPE: p.a.warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <http://buildbot.net/pipermail/devel/attachments/20050429/d3fabda4/attachment.bin>