[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Hudson Slave server ready for testing
|
We need to install a JDK 6.0 installation on the Slave machine.
We can then setup the appropriate configuration in the Slave, so that
when an installation is using "Base Java 6.0 Installation", it will
pickup the appropriate installation.
The hudson slave has a Tooling configuration that just needs to be setup
appropriately to know where to pickup the particular JDK being requested.
Dave
On 05/12/2010 08:15 AM, Webmaster(Matt Ward) wrote:
> On 05/12/2010 03:25 AM, Matthias Sohn wrote:
> >> > I tried to build egit on build2 but this fails immediately
since the
>> > configured JAVA_HOME
>> > which is called "Base Java 6.0 installation (/shared/common)" in the
>> > Hudson job configuration
>> > doesn't exist:
>> >
>> > It seems the build2 x86_64 box is trying to use the PPC binaries.
> Dave/Matt, is this a setting on Hudson on the slave, or do projects
> define this in their job?
> Based on the documentation I've been able to find, projects will
have to select the 'desired' JDK from the drop list(I added it). The
other
option I see is projects could try using the 'parameterized' build
option and specifying a JAVA_HOME with that.
I have seen a few posts that indicate if JAVA_HOME is set as part of
the slave configuration(it is now) then selecting the 'default' JDK in
the
project drop down will use the JDK in JAVA_HOME. But I've also seen
some posts indicating that using 'default' will use the first JDK in the
list.
Is someone willing to test with their build? I suggest trying the
'default' JDK first, and selecting the slave JDK second.
-Matt.
