[JIRA] [core] (JENKINS-26780) Auto-installer for JDK no longer works
Immo Huneke updated JENKINS-26780 Auto-installer for JDK no longer works Change By: Immo Huneke (10/Feb/15 5:20 PM) Attachment: access_jenkins.zip 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-26780) Auto-installer for JDK no longer works
Immo Huneke updated JENKINS-26780 Auto-installer for JDK no longer works Change By: Immo Huneke (10/Feb/15 5:12 PM) Attachment: jenkins.log-20150209.gz 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-26780) Auto-installer for JDK no longer works
Immo Huneke edited a comment on JENKINS-26780 Auto-installer for JDK no longer works Thanks for the last comment. Interesting that this happened simultaneously on two different installations, one of which has NEVER had a JDK installed previously. We only noticed the problem because we wanted to build a Java application for the first time. I checked the access log but I am unsure what to look for. We have Apache access logs showing every call to the Jenkins URL from outside the box, but of course if it's internally calling itself on port 8080 then this will be invisible. However, I have discovered the relevant archived Jenkins log and attach this for information. I won't try the script approach described above - we have a workaround. 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-26780) Auto-installer for JDK no longer works
Immo Huneke edited a comment on JENKINS-26780 Auto-installer for JDK no longer works Thanks for the last comment. Interesting that this happened simultaneously on two different installations, one of which has NEVER had a JDK installed previously. We only noticed the problem because we wanted to build a Java application for the first time. I checked the access log but I am unsure what to look for. We have Apache access logs showing every call to the Jenkins URL from outside the box, but of course if it's internally calling itself on port 8080 then this will be invisible. However, I have discovered the relevant archived Jenkins log and attach this for information, together with the filtered Apache access log (showing just accesses to /jenkins.*) for the relevant date range. There are a number of calls to /jenkins/descriptorByName/hudson.tools.JDKInstaller/checkId and similar URLs in the file. I won't try the script approach described above - we have a workaround of manually adding the JDK installer file to the cache. 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-26780) Auto-installer for JDK no longer works
Immo Huneke commented on JENKINS-26780 Auto-installer for JDK no longer works Thanks for the last comment. Interesting that this happened simultaneously on two different installations, one of which has NEVER had a JDK installed previously. We only noticed the problem because we wanted to build a Java application for the first time. I checked the access log but I am unsure what to look for. We have Apache access logs showing every call to the Jenkins URL from outside the box, but of course if it's internally calling itself on port 8080 then this will be invisible. Besides, I have just noticed that the log doesn't go back far enough - I'll have to see the archived ones. Will update this comment if I find anything significant. 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-26780) Auto-installer for JDK no longer works
Immo Huneke updated JENKINS-26780 Auto-installer for JDK no longer works Here's the file from one of two Linux servers on which I observed the same defect. NB Jenkins was installed using "yum install jenkins". Change By: Immo Huneke (09/Feb/15 1:02 PM) Attachment: hudson.tools.JDKInstaller.zip 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-26780) Auto-installer for JDK no longer works
Immo Huneke updated JENKINS-26780 Auto-installer for JDK no longer works Change By: Immo Huneke (05/Feb/15 8:57 AM) Description: InManageJenkins/ConfigureSystem,itisnolongerpossibletoviewapull-downlistofJDKversionswhenInstallfromjava.sun.comisselected.Instead,thereisatextboxintowhichtheversionmustbetyped.Itturnsoutthatonlyvaluesofversioncorrespondingtothenamesoffilesunder~jenkins/cache/jdks/LINUX/amd64arevalid.Itriedupgradingfrom7u72to7u75byalteringtheversionstringandthisiswhathappenedwhenItriedtorunthebuild:InstallingJDKjdk-7u75-oth-JPRjava.io.IOException:JDKdataisempty. athudson.tools.JDKInstaller.locate(JDKInstaller.java:361) athudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:134) athudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68) athudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) athudson.tools.ToolInstallation.translateFor(ToolInstallation.java:205) athudson.model.JDK.forNode(JDK.java:130) PSbymanuallydownloadingthelatestJDKgzfileintothecachefolderandrenamingittojdk-7u75-oth-JPR,theabovebuildthenworks. 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-26780) Auto-installer for JDK no longer works
Immo Huneke created JENKINS-26780 Auto-installer for JDK no longer works Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Feb/15 3:19 PM Description: In Manage Jenkins / Configure System, it is no longer possible to view a pull-down list of JDK versions when "Install from java.sun.com" is selected. Instead, there is a text box into which the version must be typed. It turns out that only values of "version" corresponding to the names of files under ~jenkins/cache/jdks/LINUX/amd64 are valid. I tried upgrading from 7u72 to 7u75 by altering the version string and this is what happened when I tried to run the build: Installing JDK jdk-7u75-oth-JPR java.io.IOException: JDK data is empty. at hudson.tools.JDKInstaller.locate(JDKInstaller.java:361) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:134) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:205) at hudson.model.JDK.forNode(JDK.java:130) Environment: Jenkins ver. 1.580.3 under AWS Linux 64bit Project: Jenkins Labels: jenkins Priority: Minor Reporter: Immo Huneke 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] [git-parameter-plugin] (JENKINS-23188) Tag List Empty
Immo Huneke edited a comment on JENKINS-23188 Tag List Empty I have just tried this with the latest versions (Git plugin 2.3.4, Git client plugin 1.15.0, Git parameter plugin 0.3.2) and still get a 401 (unauthorized) status back from github: Jenkins is fully up and running Jan 14, 2015 3:45:03 PM INFO hudson.model.DownloadService$Downloadable load Obtained the updated data file for hudson.tasks.Maven.MavenInstaller Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:04 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:47:46 PM INFO net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents generateContents contenttype PT_TAG RemoteConfig [https://github.com//.git] Jan 14, 2015 3:47:47 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.tagMap in /jenkins/job/auth-prototype-CI/build. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) ... at java.lang.Thread.run(Thread.java:745) Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git -c core.askpass=true fetch --tags --progress https://github.com//.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: remote: Invalid username or password. fatal: Authentication failed for 'https://github.com//.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1245) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:325) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.getTagMap(GitParameterDefinition.java:392) ... 161 more Jan 14, 2015 3:47:55 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default The parameter plugin does not seem to pick up the credentials configured for git access in the project. The git plugin itself however does so successfully. 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] [git-parameter-plugin] (JENKINS-23188) Tag List Empty
Immo Huneke commented on JENKINS-23188 Tag List Empty I have just tried this with the latest versions (Git plugin 2.3.4, Git client plugin 1.15.0, Git parameter plugin 0.3.2) and still get a 401 (unauthorized) status back from github: Jenkins is fully up and running Jan 14, 2015 3:45:03 PM INFO hudson.model.DownloadService$Downloadable load Obtained the updated data file for hudson.tasks.Maven.MavenInstaller Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:00 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:46:04 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Jan 14, 2015 3:47:46 PM INFO net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents generateContents contenttype PT_TAG RemoteConfig [https://github.com/elektron-technology/cloud-handheld.git] Jan 14, 2015 3:47:47 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.tagMap in /jenkins/job/auth-prototype-CI/build. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) ... at java.lang.Thread.run(Thread.java:745) Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git -c core.askpass=true fetch --tags --progress https://github.com/elektron-technology/cloud-handheld.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: remote: Invalid username or password. fatal: Authentication failed for 'https://github.com/elektron-technology/cloud-handheld.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1457) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1245) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:85) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:280) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:325) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.getTagMap(GitParameterDefinition.java:392) ... 161 more Jan 14, 2015 3:47:55 PM WARNING hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default The parameter plugin does not seem to pick up the credentials configured for git access in the project. The git plugin itself however does so successfully. 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.
