[JIRA] [conditional-buildstep-plugin] (JENKINS-21491) Time restriction does not work if earliest >= latest
Title: Message Title Nikolay Diakov commented on JENKINS-21491 Re: Time restriction does not work if earliest >= latest It is worse - the plugin does not properly compare 12hr - 24hr clock. I will try setting the clock of Jenkins to 24hr (using the Locale language setting). 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-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Title: Message Title Nikolay Diakov commented on JENKINS-13864 Re: JDK auto installer installs to a different path than JAVA_HOME for a build uses We have moved the Jenkins under IT management since the original issue. I will see when I can test again locally. 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] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Nikolay Diakov commented on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses Ok, I have finally managed to cleanup the old config paths - these were in the registry at various locations, such as: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.6.0_31 ... What you need to do is search in all keys/values/data for the JDK signature, e.g., "1.6.0_31", also search the wrong JDK paths, e.g., "hudson" in this case. Then all remote installations from the master of JDKs will proceed in the proper places. I guess the headless installer that forces 'yes' on all questions, also uses any default suggestions that the installer may make for directories, and an existing one happens to override the instructed place to install argh! 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
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Nikolay Diakov edited a comment on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses We have this same situation too: Installing c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe [jdk-1.6.0_31] $ c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe /s /v /qn /L \"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe.install.log\" REBOOT=ReallySuppress INSTALLDIR=\"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\" However after that in the build: java.io.IOException: Cannot run program "c:\java\jenkins\tools\JDK\jdk-1.6.0_31/bin/java" (in directory "c:\java\jenkins\workspace\fas-windows\fas"): CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) at hudson.Launcher$ProcStarter.start(Launcher.java:338) The directory has only the .installedByHudson file marker. Now, I find a partial installation in the c:\java\hudson\tools\JDK\jdk-1.6.0_31 - which is the previous configuration for the node - I had changed it from c:\java\hudson to c:\java'jenkins and restarted it. I however did not restart the Master instance, could it be keeping the old config? 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
[JIRA] (JENKINS-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Nikolay Diakov edited a comment on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses We have this same situation too: Installing c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe [jdk-1.6.0_31] $ c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe /s /v /qn /L \"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe.install.log\" REBOOT=ReallySuppress INSTALLDIR=\"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\" However after that in the build: java.io.IOException: Cannot run program "c:\java\jenkins\tools\JDK\jdk-1.6.0_31/bin/java" (in directory "c:\java\jenkins\workspace\fas-windows\fas"): CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) at hudson.Launcher$ProcStarter.start(Launcher.java:338) The directory has only the .installedByHudson file marker. Now, I find a partial installation in the c:\java\hudson\tools\JDK\jdk-1.6.0_31 - which is the previous configuration for the node - I had changed it from c:\java\hudson to c:\java\jenkins and restarted it. I however did not restart the Master instance, could it be keeping the old config? 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
