]
Nick Boldt commented on JBIDE-20062:
------------------------------------
Both forge builds are blue.
Server's tests are still running but I see this in the log, so $\{JAVA17} is being
resolved w/ the need for the Jenkins param:
{code}
Available JREs for testing:
jbosstools.test.jre.5=/qa/tools/opt/amd64/jdk1.5.0_last
jbosstools.test.jre.6=/qa/tools/opt/amd64/jdk1.6.0_last
jbosstools.test.jre.7=/qa/tools/opt/amd64/jdk1.7.0_last
jbosstools.test.jre.8=/qa/tools/opt/amd64/jdk1.8.0_last{code}
Therefore I've pushed changes to the remaining jobs too:
remove declaration of JAVA17 in forge and server jobs
-----------------------------------------------------
Key: JBIDE-20062
URL:
https://issues.jboss.org/browse/JBIDE-20062
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, forge, server
Affects Versions: 4.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.3.0.Beta1
Discovered tonight that some jobs were setting JAVA17 = java1.8.0_last, when the correct
value should have been java1.7.0_last.
But on most slaves this variable should be set automatically already; this is probably a
relic from a simpler time (when JDK 7 was first being rolled out across the slaves).
So... for the _master jobs, I've removed the parameter. And for the _4.3.mars jobs,
I've fixed the parameter.
If both forge and server are still blue in master after this change, we can push the same
change into the _4.3.mars jobs AFTER Beta1.
https://github.com/jbdevstudio/jbdevstudio-ci/commit/6c49750510357e2959c5...