[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-755 Re: Default JDK meaning in project options is confusing. Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/JDK.java core/src/main/java/jenkins/model/Jenkins.java core/src/test/java/jenkins/model/JDKNameTest.java http://jenkins-ci.org/commit/jenkins/730d6ecb2d29b25ef69f5cf49e097fb09dbfc3a6 Log: Merge pull request #1528 from Wilfred/better_default_text JENKINS-755 Describe the built-in JDK as '(System)'. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-755 Default JDK meaning in project options is confusing. Change By: Jesse Glick Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Title: Message Title Jesse Glick assigned an issue to Wilfred Hughes Jenkins / JENKINS-755 Default JDK meaning in project options is confusing. Change By: Jesse Glick Assignee: Wilfred Hughes Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Title: Message Title mwebber commented on JENKINS-755 Re: Default JDK meaning in project options is confusing. The fix for this problem, which was released in Jenkins 1.635, appears to have caused a new bug JENKINS-31217 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-755 Re: Default JDK meaning in project options is confusing. Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/0cc465e706f69b7ee0389749233ab2f33ca47eed Log: Noting fix of JENKINS-755 in https://github.com/jenkinsci/jenkins/pull/1528 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Title: Message Title Oleg Nenashev commented on JENKINS-755 Re: Default JDK meaning in project options is confusing. Fixed in https://github.com/jenkinsci/jenkins/pull/1528 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Title: Message Title dogfood commented on JENKINS-755 Re: Default JDK meaning in project options is confusing. Integrated in jenkins_main_trunk #4340 JENKINS-755 Describe the built-in JDK as '(System)'. (Revision ff021d3c374a067d622fdb078a4e391149df7d41) Result = SUCCESS whughes : ff021d3c374a067d622fdb078a4e391149df7d41 Files : core/src/main/java/hudson/model/JDK.java Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Wilfred Hughes commented on JENKINS-755 Default JDK meaning in project options is confusing. I've opened a pull request to improve the wording here: https://github.com/jenkinsci/jenkins/pull/1528 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Vladimir Kralik commented on JENKINS-755 Default JDK meaning in project options is confusing. Dragomir said I do not see any workaround to get out of this nasty situation easily. Or am I wrong? By using Configuration Slicing Plugin there is possible to change JDK in a lot of jobs in simple way. 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Daniel Beck commented on JENKINS-755 Default JDK meaning in project options is confusing. Dragomir Nedyalkov: That one is easy: Add a second explicit JDK (that no job will be using) and configure the two jobs to explicitly use the first explicit JDK. OTOH if you already had 1 configured JDK that was used by default by 100 jobs, and then add a second, and all jobs then back to System Default, that is a PITA. Either reconfigure a lot of jobs, or be stuck at 1 JDK forever. 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.
[JIRA] [maven-plugin] (JENKINS-755) Default JDK meaning in project options is confusing.
Dragomir Nedyalkov commented on JENKINS-755 Default JDK meaning in project options is confusing. Not sure, in which direction the issue resolving is going to, but ... Imagine the scenario when you have environment with hundreds of already setup build jobs, running with the one and only (default in this case) JDK available for the CI server . Then comes a day you need to setup 2 new build jobs to run against the latest and greatest Oracle JDK. What practically happens – The latest and greatest JDK installed on the system and configured for the Jenkins, becomes the “Default” one for all available build jobs. And one needs to manually reconfigure hundreds of build jobs, and explicitly to tell them to use the former JDK…. I do not see any workaround to get out of this nasty situation easily. Or am I wrong? 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.
