Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47834

Add the support for Remoting work dir configuration of JNLP Launcher

    XMLWordPrintable

Details

    Description

      https://jenkins.io/doc/upgrade-guide/2.73/ see Remoting Working Directories section

      See screenshot for the new fields that were introduced to the JNLP Launcher.

      These appear to be ignored by the Slave Setup and/or Libvirt Slaves plugins which result in the following two arguments being added empty no matter what is in the fields

      <argument>-workDir</argument>
      <argument/>
      <argument>-internalDir</argument>
      <argument/>

      This seems to break the JNLP launcher since it appears to be defaulting to the `/` as a path in such case.

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-18149 Enable manually start of a JNLP-Controlled Slave without automatically shutdown

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-50427 Libvirt Slaves Plugin needs updating to 2.x

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 4 older comments
            oleg_nenashev Oleg Nenashev added a comment -

            duemir sorry for removing the component. The issue description does not refer "Slave Setup Plugin" at all, and I assumed that it is just a wrong component. All slave-* components are being misused heavily, and I cleanup them sometimes

            oleg_nenashev Oleg Nenashev added a comment - duemir sorry for removing the component. The issue description does not refer "Slave Setup Plugin" at all, and I assumed that it is just a wrong component. All slave-* components are being misused heavily, and I cleanup them sometimes
            duemir Denys Digtiar added a comment -

            oleg_nenashev no worries, completely understandable. I updated the description a bit.

            duemir Denys Digtiar added a comment - oleg_nenashev no worries, completely understandable. I updated the description a bit.
            gbburkhardt Glenn Burkhardt added a comment -

            See also:  https://issues.jenkins-ci.org/browse/JENKINS-50427

            gbburkhardt Glenn Burkhardt added a comment - See also:   https://issues.jenkins-ci.org/browse/JENKINS-50427
            gbburkhardt Glenn Burkhardt added a comment -

            I was able to patch "libvirt-slave" to fix this.  The "slave.jar" file on the Windows guest needed to be updated with the one generated by Jenkins 2.108.  I posted the patched files on this thread:

            https://groups.google.com/forum/#!topic/jenkinsci-dev/w66m_3LTAxs

            gbburkhardt Glenn Burkhardt added a comment - I was able to patch "libvirt-slave" to fix this.  The "slave.jar" file on the Windows guest needed to be updated with the one generated by Jenkins 2.108.  I posted the patched files on this thread: https://groups.google.com/forum/#!topic/jenkinsci-dev/w66m_3LTAxs
            bgermann Bastian Germann added a comment -

            The Java Web Start does not work with Java 11, so I do not think that this needs to be fixed anymore. If there is demand, please reopen.

            bgermann Bastian Germann added a comment - The Java Web Start does not work with Java 11, so I do not think that this needs to be fixed anymore. If there is demand, please reopen.

            People

              bgermann Bastian Germann
              duemir Denys Digtiar
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: