Buildbot streams those out over its webserver, written in Twisted. Check the buildbot manual for more info.
It's on my list to upgrade buildbot to the latest version (ours is several major versions old). I would have done it already but it requires an upgrade of the aforementioned Twisted library, which I didn't have time to investigate. If anyone our there would like to help w/ this and/or other sysadmin/rel-eng related tasks, please contact me off-list and we'll get started. (As it stands I have one or two things Adium related in the queue ahead of messing w/ buildbot.) -Colin On Dec 28, 2010, at 4:39 PM, Ken Raeburn <raeb...@raeburn.org> wrote: > On Dec 28, 2010, at 17:00, Peter Hosey wrote: >> Every buildbot log is huge. The plain text of the most recent build's log is >> 9.2 MB. If I gzip that -1, it's 504 K. >> >> Any chance we can get some zlib stream compression on the buildbot's web >> server? It'd make it a metric *...@#!ton easier to download a log. > > Depending on the web server, its configuration, etc., you might also be able > to just store the file compressed, and having it magically translated into a > transfer encoding, so browsers supporting compressed transfers (most of them, > I think) just pull down the file with no extra CPU cycles wasted on > compressing, and the server only has to do work for clients that don't > support it (and the work is uncompressing, which is probably cheaper than > compressing). Saves disk space on the server; should save CPU cycles on the > server, depending on the particular clients. > > I had such a thing set up at my last job for automated test results, under > Apache I think, but I'm afraid I don't remember the details of how we got it > set up.... > > Ken
