-
Bug
-
Resolution: Fixed
-
Critical
-
1.398
We have migrated from Hudson to Jenkins. We decided to create a new buildmaster, since we also faced some issue with the old master.
On the new master we defined only 1 JDK.
All builds try to install the new JDK (1.6.23) and on a number of systems (windows) this gave an issue.
The JDK gets installed in ../tools/1.6.23, but the public JRE get installed in C:\Program Files\Java\jre6
That influences already installed Java installation(s).
On a number of machine we had to remove all Java installation and do a manual installation again to get it back up and running.
For windows the public JRE has to be skipped I think.
That can be done with the following command: ADDLOCAL="ToolsFeature,DemosFeature,SourceFeature"
Or the install directory of the public JRE has to be defined as well: /INSTALLDIRPUBJRE=...
That is not done right now.
More info: http://www.oracle.com/technetwork/java/javase/install-windows-189425.html
This issue is very frustrating and causing a lot of issue and loss of time.
- is blocking
-
JENKINS-7186 Master Cannot Start slave.jar on Windows Slaves
- Closed
- is related to
-
JENKINS-2452 Cannot install slave agent as Windows service
- Resolved
-
JENKINS-6957 Windows slave fails to find java
- Resolved
-
JENKINS-7186 Master Cannot Start slave.jar on Windows Slaves
- Closed
-
JENKINS-7701 error launching slave agent to w2k8 server
- Closed
-
JENKINS-11856 Jenkins Slave fail to start on Windows 2008 R2 64-bit as windows service
- Closed
-
JENKINS-7701 error launching slave agent to w2k8 server
- Closed