On Mon, May 31, 2010 at 10:54, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > On Mon, May 31, 2010 at 11:37 AM, Gav... <ga...@16degrees.com.au> wrote: >> I would like the Master to just be the master and have no builds (ideally, >> we can see how it works out), and >> the accounts created on the machine will only be for Hudson Admins who >> intend to admin the Hudson instance, not folks administering builds - >> a strictly limited set in the same way we admin other boxes. > > Sounds good.
+1 >> Do we have any Hudson Admins (or wannabees) who would like to help >> tackle the migration? > > Count me in. I'd like to help out, but am pretty short on time these days :( so I'd better not put myself in the way just yet. >> Does anyone anywhere have any concerns about this move (like we will >> likely have to rename hudson.zones.a.o to something else like >> hudson-master.a.o) > > We probably should set up redirects from hudson.z.a.o to avoid > breaking links to specific build results. +1. If we can point hudson.z.a.o at an Apache somewhere, this can just be a matter of a .htaccess file with a few RewriteRules in it. 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. > 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. --j.
