[Buildbot-devel] svn_buildbot.py troubles

[Brian Warner]

You're close, it's just that you're pointing svn_buildbot.py at the wrong
port.

> /home/svnuser/Scripts/svn_buildbot.py --repository ~/AGDeviceControl/
> --revision 270 --bbserver hobo.anu.edu.au --bbport 8008

That tells svn_buildbot to connect to port 8008...

> c['sources'] = []
> c['sources'].append(PBChangeSource(prefix="trunk"))
> c['slavePortnum'] = 9989
> c['status'] = []
> c['status'].append(html.Waterfall(http_port=8080))
> c['status'].append(client.PBListener(port=8008))

The PBChangeSource (for accepting Changes from things like svn_buildbot.py)
shares port 9989 with the buildslaves. You want "--bbport 9989" instead.

(incidentally, PBChangeSource is supposed to take a port= argument, which
would let you have it listen on whatever port you wanted, maybe sharing the
slaveport, maybe not. But that isn't implemented yet: for now, it must always
share the slaveport.)

The client.PBListener you have on port 8008 is for delivering status
information to special-purpose status clients (like the one you get when you
do 'buildbot statuslog' or 'buildbot statusgui'). You might think of it as
the "output" of the buildbot, whereas the PBChangeSource is the "input".

I'll agree, the error message is unfortunate and unhelpful. We're using a
handful of ports for various purposes (PBChangeSource, slaves, PBListener,
and web.distrib all use the Perspective Broker protocol, Waterfall speaks
HTTP). I haven't yet figured out a good way to clean this up.. probably
having all the PB services share the same port is a good idea, and it's on
the drawing board (the master.Dispatcher class is intended for this purpose).
But, on the other hand, you might want to have them use separate ports so you
can firewall them independently

So, in brief, just change your svn_buildbot.py invocation to use --bbport
9989 and it should work ok.

cheers,
 -Brian