Daniel Beck commented on Bug JENKINS-24788

I found this label mismatch was killing Maven jobs and Freeform jobs using the "Invoke Maven 3" Build Task, but Freeform jobs using the "Invoke top-level Maven targets" step were running fine. I'm not sure what JDK they were using, though. Certainly not the JDK we set (which the mismatch should ignore) or the default /bin/java (which doesn't exist). This could be a nasty bug to people who use that build step and want to control the version of Java on a per-job basis.

As it's a freestyle project, just run a batch or shell build step and print environment variables. Look for JAVA_HOME.

While the problem was on our end, there were no errors or warnings to point us in the right direction. Something along the lines of "Label Mismatch: ${yourDesiredJDKSetting} has no valid JDK installers for ${thisSlave}. Using default JDK settings." would have been fantastic. Even something as simple as "No valid JDK installers found. Using default JDK settings." would have been a clue.

File an improvement against the core component. Assign it to me.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to