32-bit or 64-bit JRE for Windows 64-bit slave?

1,747 views
Skip to first unread message

David Aldrich

unread,
Jun 7, 2013, 3:35:29 AM6/7/13
to jenkins...@googlegroups.com

Hi

 

We run several Jenkins slaves on Windows XP 64-bit and are now build a Windows 7 64-bit slave.

 

We found it necessary to install both 32-bit and 64-bit JRE on Windows XP 64-bit in order to get the Jenkins slave to launch.

 

I doubt that installing both JRE’s is really necessary.  Please can anyone tell me which JRE to install and tell me of anything to specially take note of?

 

Best regards

 

David

 

Louis Roché

unread,
Jun 7, 2013, 3:52:05 AM6/7/13
to jenkins...@googlegroups.com, david....@emea.nec.com
Hi,

I'm also using Windows 7 64-bit on my slaves. And I have only Java 64-bit.

The configuration to choose which version of java should be used to run the slave is un JENKINS_HOME/jenkins-slave.xml

There is a line:
<executable>C:\Program Files\Java\jre7\bin\java.exe</executable>

And you can change this line to pick the good java.

L.

David Aldrich

unread,
Jun 10, 2013, 4:50:03 AM6/10/13
to Louis Roché, jenkins...@googlegroups.com

Hi Louis

 

Ø  The configuration to choose which version of java should be used to run the slave is un JENKINS_HOME/jenkins-slave.xml

My Jenkins folder is empty.  The Launch Slave process must have failed before getting to the point where it writes jenkins-slave.xml to the slave.

 

Can anyone advise me of the correct way to configure a Win 7 64-bit Jenkins slave please?

 

David

 

Click here to report this email as spam.

Richard J

unread,
Jun 10, 2013, 3:44:29 PM6/10/13
to jenkins...@googlegroups.com, david....@emea.nec.com
Setting up a Windows slave using a default install of Windows Server 2008R2 x64 involves a number of steps. 
I've finally gotten to the point where I can do it successfully on multiple machines.
 
If you are just having the problem of x64 and x86 java, then you probably forgot the workaround that allows the Jenkins client app find the Java x64.
As someone else said, you can specify a java version in the xml, but that assumes that you have already connected.
 
To start the process, after you've installed java x64, adjusted the registry key permissions etc, etc, do the following
 

mklink /H "c:\windows\syswow64\java.exe" "c:\windows\system32\java.exe"

David Aldrich

unread,
Jun 11, 2013, 6:32:37 AM6/11/13
to jenkins...@googlegroups.com

Hi Richard

 

Thanks for your reply.  Actually, we have both 32-bit and 64-bit JRE installed and the slave still will not launch.

 

We will work through the suggestions here:

 

https://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM

 

But it would be nice to have a definitive ‘how-to’ for configuring a Win 7 64-bit slave

 

BR

 

David

 

From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Richard J
Sent: 10 June 2013 20:44
To: jenkins...@googlegroups.com
Cc: David Aldrich
Subject: Re: 32-bit or 64-bit JRE for Windows 64-bit slave?

 

Setting up a Windows slave using a default install of Windows Server 2008R2 x64 involves a number of steps. 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply all
Reply to author
Forward
0 new messages