[JIRA] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Daniel Beck resolved as Fixed Fixed towards 1.637. Jenkins / JENKINS-31217 No JDK named ‘null’ found in Jenkins 1.635 Change By: Daniel Beck 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 Code changed in jenkins User: Wilfred Hughes Path: core/src/main/java/hudson/model/JDK.java core/src/test/java/jenkins/model/JDKNameTest.java http://jenkins-ci.org/commit/jenkins/707d4ba135ec9e3e6a681f1acb4e243e2b5aa9b6 Log: JENKINS-31217 Treat null as a default JDK name. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/JDK.java core/src/test/java/jenkins/model/JDKNameTest.java http://jenkins-ci.org/commit/jenkins/a2d9b797ec269e92a01a111887bef93e023a5f24 Log: Merge pull request #1896 from Wilfred/jenkins-31217 JENKINS-31217 Treat null as a default JDK name. Compare: https://github.com/jenkinsci/jenkins/compare/505fde00125c...a2d9b797ec26 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Wilfred Hughes commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 Opened https://github.com/jenkinsci/jenkins/pull/1896 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Sverre Moe commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 I have the same problem with a Multi-configuration project where there is no option of selecting a JDK. Its output is right after starting builders and publishers from a template project (which are also a Multi-configuration project). [TemplateProject] Starting builders from: template-project No JDK named ‘null’ found [TemplateProject] Starting publishers from: template-project-publishers No JDK named ‘null’ found 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-31217 No JDK named ‘null’ found in Jenkins 1.635 Adjusting priority as this only generates a useless message in the log, and has a workaround. Change By: Daniel Beck Priority: Critical Minor 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Thales Vieira commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 Temporary workaround: as Jesse Glick mentioned, go to the Global Settings, create add a JDK and not use it by default. With the JDK Plugin you can select the "Default" and it will stop failing. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Igor Polubelov commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 If I explicitly configure JDK its JAVA_HOME is used by master and slave nodes. I can't have different JAVA_HOME for slaves. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Jesse Glick commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 For the workaround you might need to create a dummy JDK so you can not select it. See JENKINS-10191 and JENKINS-17373. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Vincent Caboara commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 I am still getting the error, but the failures were from a different issue which I've identified and fixed. Thanks. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Vincent Caboara edited a comment on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 I have never had to set or install configure a JDK for my Jenkins configurations, so I do not see a JDK option in the job. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Vincent Caboara commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 I have never had to set or install a JDK for my Jenkins configurations, so I do not see a JDK option in the job. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Jesse Glick commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 Workaround should be to explicitly configure the JDK for the job. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title mwebber commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 I rolled back to 1.634. However, the message might be benign (I'm not sure), in which case you could just ignore it. I can't say whether or not it's a real problem or not. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Vincent Caboara commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 Is there any sort of work around in the meantime? Thanks! 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title ct323i commented on JENKINS-31217 Re: No JDK named ‘null’ found in Jenkins 1.635 Seeing No JDK named ‘null’ found between every step of the build. 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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title Jesse Glick assigned an issue to Wilfred Hughes Yes, the patch was incorrect. An original null check was dropped. I have commented in the PR. Jenkins / JENKINS-31217 No JDK named ‘null’ found in Jenkins 1.635 Change By: Jesse Glick Component/s: maven-plugin Assignee: Wilfred Hughes Priority: Minor Critical Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title
mwebber updated an issue
Jenkins / JENKINS-31217
No JDK named ‘null’ found in Jenkins 1.635
Change By:
mwebber
Theory: This problem was introduced in Jenkins 1.635, as a result of the fix for JENKINS-755.I observer observe numerous {{No JDK named ‘null’ found}} messages in the job log for many jobs. The message looks like it is generated during the post-build steps.
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] [core] (JENKINS-31217) No JDK named ‘null’ found in Jenkins 1.635
Title: Message Title mwebber created an issue Jenkins / JENKINS-31217 No JDK named ‘null’ found in Jenkins 1.635 Issue Type: Bug Assignee: Unassigned Components: core, maven-plugin Created: 28/Oct/15 9:18 AM Environment: Jenkins 1.635 Priority: Minor Reporter: mwebber Theory: This problem was introduced in Jenkins 1.635, as a result of the fix for JENKINS-755. I observer numerous No JDK named ‘null’ found messages in the job log for many jobs. The message looks like it is generated during the post-build steps. Add Comment
