|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Just ran into this as well and a bit of googling led me here. However, my wants are slightly different: I'd also like an option to tell Jenkins to explicitly use the System provided JDK. Mainly because the Jenkins I currently maintain should use the same JDK/JRE we have in production and we maintain the JDK/JRE with puppet, outside of the Jenkins eco-system.
I do agree that the current way to work with JDK's in Jenkins is a bit confusing and it does not tie all plugins together (maven job with sonar's 'inherit from job' when the job's JDK is 'Default' is one such example).