Correct... the evil job type is... evil... Freestyle will work just fine
You also should be able to make toolchains work, i.e. that Maven can use Java 7 or 8 to run and Java 6 to compile. Keep in mind that JDK 9 or JDK 10 will have a lower bound on the -target so that you will probably be only allowed to have your -target at 1.8 or higher so you would need to switch to toolchains if you still want to keep building for a Java version that was end-of-life in Feb 2013 On 17 December 2015 at 01:27, Indra Gunawan (ingunawa) <[email protected]> wrote: > Point #3 is not possible because of this new change in 1.625.1? > > 1.625.1 is the first Jenkins LTS release that requires Java 7 to run. If > you're using the Maven Project type, please note that it needs to use a > JDK capable of running Jenkins, i.e. JDK 7 or up. If you configure an > older JDK in a Maven Project, Jenkins will attempt to find a newer JDK and > use that automatically. If your SSH Slaves fail to start and you have the > plugin install the JRE to run them, make sure to update SSH Slaves Plugin > to at least version 1.10. > > > > If we patch the Jenkins to run 1.625.3, maven 2 type project using JDK 6 > won¹t work anymore? > > Thank you > -Indra > > On 12/16/15, 12:07 PM, "[email protected] on behalf of > Daniel Beck" <[email protected] on behalf of > [email protected]> wrote: > > > > >On 12.12.2015, at 18:44, Indra Gunawan (ingunawa) <[email protected]> > >wrote: > > > >> With the Java 7 to run requirement, I want to confirm the following: > >> 1. Jenkins master and all its slave needs to run JDK 7 or above (JDK7 or > >> above to run Jenkins master process and SSH slave to connect needs to > >>run > >> JDK 7 or above). > > > >It needs to be a JRE that runs Jenkins, but since the JDK includes one, > >JDK 7 is adequate. > > > >> 2. Maven type job then should work because SSH slave already runs JDK 7 > >>or > >> above. > > > >Yes (see previous item) and no (see next item). > > > >> 3. However, if the maven project still needs JDK 6, I can still set the > >> JDK in the job configuration or Injecting JAVA_HOME to JDK 6 and it will > >> use JDK 6 to build the pom.xml and project right? > > > >No. If it is actually a Maven Project, not a freestyle project, there is > >no way to run it using JDK 6 in Jenkins 1.612 and up. I think toolchains > >(a Maven feature) may work, but have never tried it. > > > >-- > >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 [email protected]. > >To view this discussion on the web visit > > > https://groups.google.com/d/msgid/jenkinsci-users/30EE23F8-7344-4C15-8C04- > >53BE75776FDF%40beckweb.net. > >For more options, visit https://groups.google.com/d/optout. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/D2974ECC.3E7D5%25ingunawa%40cisco.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMyPh19pha%2BjtPv-FWT6kL-rMsne18RHbX_J6J6Tqy1%2BBg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
