Hi, On Mon, May 31, 2010 at 12:27 PM, Justin Mason <j...@jmason.org> wrote: > Another issue: we should send out a warning asap for anyone still using the > master for builds (ie those 20 tied jobs). I'll take care of that if you > like.
Go for it. >> Ideally I'd set up HTTP proxying [1] at http://ci.apache.org/hudson/ >> to avoid including any deployment details in Hudson URLs. >> [1] http://wiki.hudson-ci.org/display/HUDSON/Running+Hudson+behind+Apache > > for what it's worth, I ran a buildbot install behind mod_proxy for a while > and eventually abandoned it -- it could not handle the "tail-style" log file > output mode, where small trickles of data were output every few seconds. > This may have similar issues, or possibly Hudson or recent mod_proxy releases > have fixed/avoided the bug, I don't know, but just fyi. AFAIUI Hudson avoids this problem as long as the context path of the Hudson webapp matches the local part of the proxy base URL. So we should we fine as long as we use .../hudson in both places. I can check that on a local Hudson installation to be sure. BR, Jukka Zitting
