#2129: Support unix domain sockets for build slaves.
------------------------+-----------------------
Reporter: simpletoon | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: undecided
Version: 0.8.5 | Keywords:
------------------------+-----------------------
I'm using build-bot for a simple single-machine continuous build system.
I don't really care to have TCP sockets open if not really needed. I have
noticed that both status and slave ports can work with unix domain
sockets:
c [ 'slavePortnum' ] = "unix:/home/user/build/master/slaveconnect"
c [ 'status'
].append(html.WebStatus(http_port="unix:/home/user/build/master/status"))
This way it doesn't open any TCP ports on the host system. When I desire
to view the status I can start as simple socat connection to redirect to
the socket and use any web browser.
socat -v tcp-l:<portnum>,fork,reuseaddr,bind=127.0.0.1
unix:/home/user/build/master/status
I would like to find a way to configure the build slave
(/home/user/build/slave) to connect to the master by using unix domain
sockets instead of requiring a TCP connection. The
buildbot.slave.bot.BuildSlave code uses internet.TCPClient so it can't do
this. It seems like a simple check could be done on hostname (if it
starts with unix:) and then use internet.UnixClient instead.
--
Ticket URL: <http://trac.buildbot.net/ticket/2129>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
