• Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Blocker Blocker
    • ssh-slaves-plugin
    • None

      With SSH slave plugin, I have the following issue:

      On the target machine, we still have JDK 1.7 as default java (the software running is rather old). As Jenkins needs 1.8, it is installed in addition to this. I then tried to start the slave, with the following output:

      (some ugly shell script code here...)
      [06/11/18 16:11:02] [SSH] Starting sftp client.
      [06/11/18 16:11:02] [SSH] Copying latest slave.jar...
      [06/11/18 16:11:04] [SSH] Copied 767,078 bytes. Expanded the channel window size to 4MB
      [06/11/18 16:11:04] [SSH] Starting slave process: cd "/home/baker/jenkins" && /opt/jdk1.8.0_162/bin/java -Xmx1572m -jar slave.jar
      bash: /opt/jdk1.8.0_162/bin/java: No such file or directory Slave JVM has terminated.
      Exit code=127

      That is wondering me, because directory /opt/jdk1.8.0_162 doen't even exist. I also tried to set the JAVA_HOME in the config of the node and also tried to add the JDK7 tool location, but that does not change anything. It would be great if I could configure it here.

          [JENKINS-51866] launcing slave detects non existing JDK

          Daniel Held created issue -
          Ivan Fernandez Calvo made changes -
          Link New: This issue is related to JENKINS-47586 [ JENKINS-47586 ]
          Ivan Fernandez Calvo made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            ifernandezcalvo Ivan Fernandez Calvo
            dheld Daniel Held
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: