[Buildbot-devel] Status of the trac plugin

Matthieu Brucher matthieu.brucher at gmail.com
Thu Aug 16 19:32:51 UTC 2007


>
> In what way did it fail? Using the following snippet (taken directly from
> the
> master.cfg.sample that 'buildbot create-master' provides) seems to work
> for
> me here:
>
> from buildbot.buildslave import BuildSlave
> c['slaves'] = [BuildSlave("bot1name", "bot1passwd")]
>
> Note that c['slaves'] must be populated with BuildSlave instances. The
> deprecated c['bots'] can accept (name,passwd) tuples, but c['slaves'] will
> not.



OK, I used my old 0.7.5 sample, I did not create a new own and the displayed
warning did not help.


>    - my custom buildbot.css file is not accessible anymore
>
> Just copy it into public_html/buildbot.css, and it will be retrieved from
> there. Same with robots.txt .



OK, thanks :)

>    - I do not know how to use the XMLRPC server :( no sample anywhere
>
> Yeah, true. Take a look at buildbot/status/web/xmlrpc.py for now, that may
> give you a hint as to how to use it. I'd also suggest using a python shell
> and the 'xmlrpclib' library for testing:
>
> 24:warner at fluxx% python
> Python 2.4.4 (#2, Jul 21 2007, 11:00:24)
> [GCC 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import xmlrpclib
> >>> p = xmlrpclib.ServerProxy("http://localhost:8080/xmlrpc")
> >>> p.get_build(args..)



The trac plugin does not work with TRAC because the __init__.py prints
something instead of importing something from another module. I corrected
it, but it didn't show up in the webadmin panel :(


>    Are these future changes documented somewhere ?
>
> Not yet. Much of the remaining work for the upcoming 0.7.6 release is to
> document this stuff (and the upgrade process) well.
>
> Speaking of upgrade, I'm working on adding a 'buildbot upgrade-master'
> command, which would look at your existing buildmaster basedir and do
> whatever changes are necessary to bring it up-to-date. For 0.7.6, that
> would
> mean creating a public_html/ directory, populating it with the same
> (index.html, buildbot.css, robots.txt) files that 'create-master' does,
> and
> then checking your master.cfg file for deprecated elements. I think this
> sort
> of tool should help cover a couple of the problems you experienced.


That would be indeed great !

Thanks for the info

Matthieu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20070816/fb1e1401/attachment.html>


More information about the devel mailing list