[jbosstools-issues] [JBoss JIRA] (JBIDE-20062) remove declaration of JAVA17 in forge and server jobs

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-20062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078457#comment-13078457 ] 

Nick Boldt commented on JBIDE-20062:
------------------------------------

kicked https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4.3.mars/ >=25 
and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_master/ >=785

kicked https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-forge_4.3.mars/ >=24
and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-forge_master/ >=889




> 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
>
> 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/6c49750510357e2959c56b1340e0579d40c2bd3d



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)