Hi, 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. > Do we have any Hudson Admins (or wannabees) who would like to help > tackle the migration? Count me in. > 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. Ideally I'd set up HTTP proxying [1] at http://ci.apache.org/hudson/ to avoid including any deployment details in Hudson URLs. Other than that the migration shouldn't cause too much trouble. PS. Do you think the new server could handle Sonar as well (see INFRA-2551)? I'd be happy to set it up. [1] http://wiki.hudson-ci.org/display/HUDSON/Running+Hudson+behind+Apache BR, Jukka Zitting
