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. slave-agent.jnlp
          0.8 kB
        2. image-2017-11-06-12-07-48-879.png
          image-2017-11-06-12-07-48-879.png
          89 kB

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

          Denys Digtiar created issue -
          Giuseppe Landolfi made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: slave-setup-plugin [ 15929 ]
          Assignee Original: Giuseppe Landolfi [ peppe ]
          Denys Digtiar made changes -
          Description Original: [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 and the following two arguments are added no matter what is in the fields

          {{ <argument>-workDir</argument>}}
          {{ <argument/>}}
          {{ <argument>-internalDir</argument>}}
          {{ <argument/>}}

          This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such case.           		New: [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 plugin and the following two arguments are added no matter what is in the fields

          {{<argument>-workDir</argument>}}
          {{<argument/>}}
          {{<argument>-internalDir</argument>}}
          {{<argument/>}}

          This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such case.
          Oleg Nenashev made changes -
          Component/s New: slave-setup-plugin [ 15929 ]
          Oleg Nenashev made changes -
          Component/s Original: core [ 15593 ]
          Oleg Nenashev made changes -
          Epic Link New: JENKINS-44108 [ 181734 ]
          Oleg Nenashev made changes -
          Component/s New: core [ 15593 ]
          Component/s New: libvirt-slave-plugin [ 15985 ]
          Component/s Original: slave-setup-plugin [ 15929 ]
          Oleg Nenashev made changes -
          Labels New: remoting
          Denys Digtiar made changes -
          Component/s New: slave-setup-plugin [ 15929 ]
          Denys Digtiar made changes -
          Description Original: [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 plugin and the following two arguments are added no matter what is in the fields

          {{<argument>-workDir</argument>}}
          {{<argument/>}}
          {{<argument>-internalDir</argument>}}
          {{<argument/>}}

          This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such case.           		New: [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 plugin|https://plugins.jenkins.io/slave-setup] and the following two arguments are added no matter what is in the fields

          {{<argument>-workDir</argument>}}
           {{<argument/>}}
           {{<argument>-internalDir</argument>}}
           {{<argument/>}}

          This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such case.
          Denys Digtiar made changes -
          Description Original: [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 plugin|https://plugins.jenkins.io/slave-setup] and the following two arguments are added no matter what is in the fields

          {{<argument>-workDir</argument>}}
           {{<argument/>}}
           {{<argument>-internalDir</argument>}}
           {{<argument/>}}

          This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such case.           		New: [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|https://plugins.jenkins.io/slave-setup] and/or [Libvirt Slaves|https://plugins.jenkins.io/libvirt-slave] plugins which results the following two arguments are added no matter what is in the fields

          {{<argument>-workDir</argument>}}
           {{<argument/>}}
           {{<argument>-internalDir</argument>}}
           {{<argument/>}}

          This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such case.

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

              Created:
              Updated:
              Resolved: