On Tue, Oct 13, 2009 at 8:07 AM, Nigel Daley <ni...@apache.org> wrote: > Looks like the Port Allocator Plugin will only help if everyone uses it > (unlikely) or your port conflicts are *within* your same job.
Ok, if it's like that (which wasn't obvious from the docs [2]) then it's not very useful in our case, we'll just try to select unique ports then, or build in a simple port selection mechanism if needed. -Bertrand [2] http://wiki.hudson-ci.org//display/HUDSON/Port+Allocator+Plugin > > Nige > > On Oct 12, 2009, at 2:29 AM, Bertrand Delacretaz wrote: > >> Hi, >> >> Sling builds on hudson.zones.apache.org need a free HTTP port, 8888 is >> our default and recently started clashing with other builds. >> >> I've moved to another port (9362) for now, but it looks like the Port >> Allocator Plugin [1] could help here. >> >> Is anyone opposed to installing that plugin? I don't know Hudson well, >> no idea if that can have side effects. >> >> IIUC the plugin can be installed directly from >> http://hudson.zones.apache.org/hudson/pluginManager/available, it is >> listed there. >> >> -Bertrand >> >> >> [1] http://hudson.zones.apache.org/hudson/pluginManager/available > >
