On 06/Jan/2010 11:15, Aristedes Maniatis wrote: > On 6/01/10 9:56 PM, Tim Ellison wrote: >> We currently have a number of tools (e.g. JDKs, Ant, Maven, etc) defined >> globally, in the 'Manage Hudson' configuration page. >> >> Some are already a bit dubious, being declared as "on Ubuntu only", so >> not really global at all. Now we have a Windows client the paths are >> totally wrong there, so specifying a build to use 'latest' is not going >> to work.
I should correct this, since we can override the 'latest' locations. So we would just 'push down' the platform specific tools to the specific nodes. >> I think the only option is to push the tool location definitions down to >> individual nodes. That will require some duplication across the Ubuntu >> nodes, but will allow us to specify the actual tools available on a >> node, and the correct paths for Windows. >> >> WDYT? Any better option? > > Will that work on parameterised builds? [1] Don't know -- I'm guessing that the parameter choices will be limited to those that are declared in the global configurations. We can try with a single JDK version and see if you can use it in a parameterized build. Regards, Tim > And as I think I emailed before, 'maven (latest)' is already quite old, > so any improvements here will certainly help. > > > > [1] eg. http://hudson.zones.apache.org/hudson/job/Cayenne-trunk/ > >
