[JIRA] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Title: Message Title Daniel Beck resolved as Duplicate Duplicates JENKINS-24788, let's continue there. Jenkins / JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate 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-26940) JAVA_HOME is empty when no installer is available for a JDK
Daniel Beck commented on JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK How about this? Started by user anonymous Building in workspace /Users/danielbeck/Projects/Jenkins/jenkins_daniel-beck/war/work/jobs/JENKINS-26940/workspace Tool installer "Install from http://archive.apache.org/dist/ant/binaries/apache-ant-1.9.4-bin.tar.gz" cannot be run on the node "Jenkins" FATAL: Cannot find executable from the chosen Ant installation "foo" Build step 'Invoke Ant' marked build as failure Finished: FAILURE I added the third line. The issue is that the label _expression_ does not match. Unfortunately, ToolInstallers can check for any number of constraints, so I cannot just write "The label doesn't match". 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] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Daniel Beck assigned JENKINS-26940 to Daniel Beck JAVA_HOME is empty when no installer is available for a JDK Change By: Daniel Beck (17/Mar/15 9:41 PM) Assignee: DanielBeck 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] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven updated JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK Change By: Wilco Greven (13/Feb/15 8:25 AM) Issue Type: Bug Improvement 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] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven commented on JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK What bothers me is that the behaviour of the job is changed unexpectedly. When I configure a job to use a specific JVM, I expect that it will always use that JVM. This is especially important for test jobs. Logging it would already be a big improvement. BTW, I do think the fact that JAVA_HOME is set empty is an actual bug. If Jenkins falls back to the system JDK, JAVA_HOME should be set accordingly. 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] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven updated JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK Change By: Wilco Greven (13/Feb/15 8:29 AM) Description: InoticedthatwhenthereisnoinstalleravailableforaJDK,theJAVA_HOMEenvironmentvariablewillbeemptyintheenvironmentofabuild.ThiswillhappenforexamplewhenthereisnoinstallerconfiguredforaJDK.Inthatcaseitsnothardtofindthecause.ButforthecaseIdescribebelowitsmuchhardertofindoutwhyJAVA_HOMEisempty.ThereforeIthink abuild logging should failorJAVA_HOMEshouldnot be set improved whenaspecificJDKisconfiguredforthatbuildandnoinstallerisavailableforthatJDK. FurthermoreJAVA_HOMEshouldbesettomatchthedefaultJVM. Herearethestepstoreproduce:-ConfiguretwoJDKs,namedJDK1andJDK2(becauseifyouhaveonlyoneJDKyoucantselectoneinajob)-AddanExtract*.zip/*.tar.gzinstallertoJDK1andsetthelabelforthisinstallertojdk1,soitwontbeavailableforinstallationonnodestowhichthislabelisnotassigned-CreateafreestylejobandselectJDK1asJDK-RunthejobandcheckthatJAVA_HOMEisempty 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] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Daniel Beck commented on JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK BTW, I do think the fact that JAVA_HOME is set empty is an actual bug. If Jenkins falls back to the system JDK, JAVA_HOME should be set accordingly. The 'Default' or 'System' option of all tools means it uses whatever is on PATH. This has been discussed to death before. For reference see e.g. JENKINS-755, https://github.com/jenkinsci/jenkins/pull/1528, https://github.com/jenkinsci/jenkins/pull/1451. When I configure a job to use a specific JVM, I expect that it will always use that JVM. This is especially important for test jobs. Logging it would already be a big improvement. Try the following: Configure a JDK, set it to NOT auto-install, and leave the path empty. That's what you're effectively doing here. I would be very surprised if the behavior is different from what you're seeing. 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] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Wilco Greven created JENKINS-26940 JAVA_HOME is empty when no installer is available for a JDK Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Feb/15 6:16 PM Description: I noticed that when there is no installer available for a JDK, the JAVA_HOME environment variable will be empty in the environment of a build. This will happen for example when there is no installer configured for a JDK. In that case it's not hard to find the cause. But for the case I describe below it's much harder to find out why JAVA_HOME is empty. Therefore I think a build should fail or JAVA_HOME should not be set when a specific JDK is configured for that build and no installer is available for that JDK. Here are the steps to reproduce: Configure two JDK's, named JDK1 and JDK2 (because if you have only one JDK you can't select one in a job) Add an 'Extract .zip/.tar.gz' installer to JDK1 and set the label for this installer to 'jdk1', so it won't be available for installation on nodes to which this label is not assigned Create a freestyle job and select JDK1 as JDK Run the job and check that JAVA_HOME is empty Environment: Jenkins 1.580.1 Project: Jenkins Priority: Minor Reporter: Wilco Greven 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] [core] (JENKINS-26940) JAVA_HOME is empty when no installer is available for a JDK
Daniel Beck
commented on JENKINS-26940
JAVA_HOME is empty when no installer is available for a JDK
Why is this a bug? It's not difficult to imagine this being a deliberate setup ("If not on a 'jdk1' node, use the system default JDK").
Maybe logging could be improved (if there's really none), but that's it.
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.
