[Buildbot-devel] buildbot-0.7.6 released

Benoit Sigoure tsuna at lrde.epita.fr
Tue Nov 6 05:15:30 UTC 2007


On Oct 1, 2007, at 10:13 AM, Brian Warner wrote:
> I am pleased (and somewhat relieved :-) to finally announce the  
> release of
> buildbot-0.7.6

Hello Brian, list,
I'm in the process of upgrading the buildfarm of my company to  
0.7.6.  Actually, we're still running 0.7.4.  Before going through  
the upgrade, and since I was asked to deploy another buildbot based  
buildfarm in my R&D lab, I'm now trying to install that new buildfarm  
with my existing scripts/configuration templates/build factories to  
see what changes I'll have to apply on my company's buildfarm for the  
upgrade.  My company is building 20 different projects/branches on  
more than 10 different sets of OS/compiler, so I ended up writing  
lots of script to easily create new buildfarms, which must now be  
updated for 0.7.6.

I did not find any clear list of changes to apply, especially for the  
configuration file and custom build steps.  Your mail mentionned some  
changes but not all.  The `NEWS' file is basically a copy of that  
mail (or maybe it's the other way around :P) so it's not helping me  
much either.  Actually, while I'm at it, I'd like to report a minor  
inconsistency.  At some point, it says "c['bots'] has been replaced  
by c['buildslaves']" and later it goes like "c['slaves'] =  
[ BuildSlave ... ]", so I don't know which one to use.  Hmm, actually  
upgrade-master just complained "unknown key 'buildslaves' defined in  
config dictionary" so I guess it's 'slaves'.

I'm currently trying to port my build factories (https:// 
www.tsunanet.net/~tsuna/buildfactory.py) but stumbled one some issues  
that are worth mentioning in the NEWS.  For instance, how was I meant  
to know that WithProperties is now under  
buildbot.process.steps.shell?  I know 0.7.5 renamed all the build  
steps, but I fail to see why this class is in there ;)  For some  
reason, RemoteShellCommand isn't documented on http://buildbot.net/ 
repos/release/docs/reference/buildbot.steps.shell-module.html

The new class WebStatus no longer accepts a `css' argument the way  
Waterfall did.  I used to share a common css for all my buildmasters  
this way:
c['status'].append(html.Waterfall(http_port="tcp: 
8042:interface=127.0.0.1",
                                   css=os.path.expanduser("~/ 
buildbot.css")))
but I guess I can just put symlinks in all the new public_html  
directories...  this should be mentioned in the NEWS too ;)

Other than that, here are some minor nits:
   - When we click the "Ping Builder" button. it gets us back to the  
index.html page.  I think it'd be more convenient to redirect us back  
to the waterfall.
   - Ditto for the "Force Build" button.
   - I seem to remember that since 0.7.[56], it's possible to trigger  
a build on all builders from the web interface, but I can't find  
where's the big red button.
   - I also seem to remember that it was possible to request a build  
with a given patch, but the feature doesn't seem to be there.  Am I  
blind?  Or is my memory tricks on me?
   - When a force a build, the builder remains "idle" even though it  
has "1 pending" build.  How is that possible?  (I can ping it, and  
see the ping the builder's log, but nothing else)

Anyways, thanks for Buildbot, it's really great, I've been using it  
for more than a year now and I can't live without it :D
I would just like better / more accurate NEWS entries, especially  
because Buildbot tend to change a lot across releases, and backward  
compatibility does not seem to be preserved for a long time.

Cheers,

-- 
Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL: <http://buildbot.net/pipermail/devel/attachments/20071106/735fc2e1/attachment.bin>


More information about the devel mailing list