SSHLauncher does not respect Java related Node properties in DefaultJavaProvider

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      SSHLauncher uses an array of potential Java locations defined in the DefaultJavaProvider method. If the Java executable is not present in one of the listed locations, the SSH Slave fails to connect. (The linux slave I am attempting to connect to, for instance, has a JAVA_HOME of /opt/java1.5)

      DefaultJavaProvider should check slave configuration Node Properties that apply to java:

      • Environment Variables > JAVA_HOME
      • Environment Variables > PATH
      • Tool Locations > JDK

        1. SSHLauncher_javabytoollocation.patch
          3 kB
          danbeaulieu

            Assignee:
            Alan Harder
            Reporter:
            chris_r_harmoney
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: