> On 18.11.2016, at 18:46, Michael Giroux <[email protected]> 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?
No. Probably just a badly worded message and the assumption based on best practices that builds should run on slaves. Same behavior change though -- the configured JDK cannot build the project, so Jenkins will try to use the JRE/JDK that runs Jenkins itself. > 1. If the builds will work without being updated, what was the point of > upgrading projects to use toolchains? You're building using a newer JRE. Builds may fail even though they should succeed in your desired configuration, and vice-versa. > 2. has Jenkins taken steps to solve the issue by running these jobs in a > slave? No, see above. > 3. If jenkins has addressed the issue, what is the point of the error > message? It seems to be unnecessary. To inform you that possibly undesired magic is happening. > 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? See above. The project isn't actually built using the JDK you want building the project. -- 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/D0A3816E-A523-4C2F-90C3-DB8134C7FF9A%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
