[Buildbot-devel] Questions: edit the standard pages and use osx server to serve Buildbot pages trough it

[Charles Lepple]

On Thu, Jan 27, 2011 at 12:36 PM, tom fogal <tfogal at sci.utah.edu> wrote:
> One alternative approach is to use apache or whatever you'd like
> (i.e. OS X's builtin stuff) to serve up the directories buildbot
> creates, so users could view all the log files on the standard http
> port.  You get ultimate customization that way.. but of course a lot
> more work, too :)

With the current design of buildbot, you could serve up the static
content with a normal web server, but the log files on disk are not
suitable for sending straight out to a HTTP client. For one thing,
they are encoded: stdout and stderr are intermixed in the log files,
and would need to be converted to either text or HTML. A nice feature
about the logs is that buildbot will keep the HTTP connection open
until the slave finishes the step (streaming new log information as it
arrives), which is something that a regular web server won't detect
while reading a flat file.

It sounds like Fulvio might be interested in setting up a proxy
service on the OS X web server. In that case, you would set up
buildbot to listen on its usual port, and maybe even firewall it so
that only localhost can get to it. Then, you would proxy URLs from the
OS X web server to the buildbot web interface.

It's been a few years since I set up the OS X Server version of
Apache, and I hope they've upgraded past Apache 1.x, but you should be
able to use some configuration directives like this:

   ProxyPass        /your-public-URL/ http://localhost:8010/
   ProxyPassReverse /your-public-URL/ http://localhost:8010/
   # Speed up logfile streaming:
   ProxyIOBufferSize 512

The configuration GUI might make this more complicated than it needs
to be. Also, be sure that you don't turn your web server into an open
proxy for the world. I put "ProxyRequests Off" at the top level of the
apache.conf tree; YMMV.

-- 
- Charles Lepple