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

Add the support for Remoting work dir configuration of JNLP Launcher

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Won't Do
    • Icon: Minor Minor
    • core, libvirt-slave-plugin
    • None
    • LTS 2.73.x and newer

      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.

        1. image-2017-11-06-12-07-48-879.png
          image-2017-11-06-12-07-48-879.png
          89 kB
        2. slave-agent.jnlp
          0.8 kB

          [JENKINS-47834] Add the support for Remoting work dir configuration of JNLP Launcher

          Glenn Burkhardt added a comment -

          We're seeing the same problem with Jenkins ver. 2.108.

          Glenn Burkhardt added a comment - We're seeing the same problem with Jenkins ver. 2.108.

          Glenn Burkhardt added a comment -

          Mr. Digtiar - are you seeing this with a libvirt slave?  I suspect that for us it's due to an incompatibility between the libvirt plugin and Jenkins.

          Glenn Burkhardt added a comment - Mr. Digtiar - are you seeing this with a libvirt slave?  I suspect that for us it's due to an incompatibility between the libvirt plugin and Jenkins.

          Oleg Nenashev added a comment -

          The ticket has been created to a wrong component, so it has never been triaged.

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

          Oleg Nenashev added a comment - The ticket has been created to a wrong component, so it has never been triaged. Related email thread: https://groups.google.com/forum/#!topic/jenkinsci-dev/w66m_3LTAxs

          Denys Digtiar added a comment -

          gbburkhardt I have only observed it in the Slave Setup Plugin. Therefore, I only placed in the slave-setup-plugin component which for some reason is being persistently removed. If you observe similar behavior with Libvirt Slaves plugin then it might be affected as well.

          Denys Digtiar added a comment - gbburkhardt I have only observed it in the Slave Setup Plugin. Therefore, I only placed in the slave-setup-plugin component which for some reason is being persistently removed. If you observe similar behavior with Libvirt Slaves plugin then it might be affected as well.

          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 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

          Denys Digtiar added a comment -

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

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

          Glenn Burkhardt added a comment -

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

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

          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

          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

          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.

          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
            duemir Denys Digtiar
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: