> Does that help? Just barely. Yes it is a Maven project. It is clear from the execution that the build ultimately succeeds. We are aware of the JDK compatibility issue. We spent a couple of months updating maven projects to configure toolchains in the poms. After investing significant effort to build projects in JDK 1.8 using toolchains to configure the JDK needed to compile/test, we were surprised that jobs that had not been updated still run successfully. This raises a few questions: 1. If the builds will work without being updated, what was the point of upgrading projects to use toolchains? 2. has Jenkins taken steps to solve the issue by running these jobs in a slave? 3. If jenkins has addressed the issue, what is the point of the error message? It seems to be unnecessary. 4. Is there a performance issue, or other reason that would justify us continuing the effort to update the remaining (1000+) projects to build w/ JDK 1.8 using toolchains to configure the JDK needed to compile/test the project?
If Jenkins is handling the issue, it seems the error message is unnecessary. On Friday, November 18, 2016 at 12:48:56 PM UTC-7, Mark Bidewell wrote: > > In short, Jenkins after a certain point Uses Java 1.7+. It appears you > are using the Maven project type. This project type injects Jenkins > behaviors into the Maven build. These behaviors must run with Java 1.7+. > The error you are getting is to to Jenkins attempting to use its behaviors > with Java 1.6. In this case the behavior is to run Maven using the JDK on > which Jenkins itself is running then set Maven properties for Java to point > @ JDK 1.6. > > Does that help? > > On Friday, November 18, 2016 at 12:46:48 PM UTC-5, Michael Giroux wrote: >> >> Thanks Daniel. But I'm still not clear on what is going on under the >> covers. The job is NOT configured to run on a slave, but the message >> indicates that the build was retried on a slave. Is there a default slave >> that runs on the Jenkins host to support this retry? >> >> On Friday, November 18, 2016 at 8:46:22 AM UTC-7, Daniel Beck wrote: >>> >>> >>> > On 18.11.2016, at 15:46, Michael Giroux <[email protected]> wrote: >>> > >>> > Could someone either explain, or point me to documentation that >>> explains what is really happening here? Specifically what does >>> > "Retrying with slave Java ..." mean since we do not have a slave named >>> "Java". >>> >>> This refers to the Java runtime used to run the slave (now called build >>> agent) process. >>> >>> -- 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/1c6b2ac5-3643-493e-ac13-fddac2909ee9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
