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

Matrix project using labels cannot locate the workspace on Windows slave launched via SSH

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Critical Critical
    • artifactdeployer-plugin, matrix-project-plugin, slave-setup-plugin
    • None
    • Master runs on Mac OS 10.6. Slave is Windows XP with Cygwin launched via SSH (username and password; no key files). Slave's remote fs: 'C:\jenkins'. Windows slave uses label 'windows' and master node uses label 'mac'.

      A matrix project is configured with the Slaves axis and two labels are checked; 'windows' and 'mac'. There is one slave labeled 'mac' on the master and one slave labeled 'windows' on a remote windows machine. The windows machine has cygwin installed and the jenkins node configuration specifies that it's started via SSH. Jenkins successfully starts the windows slave and when the build runs executes a shell script on both 'mac' and 'windows' nodes.

      My project's configuration specifies artifacts as: 'label/mac/MacInstaller/.pkg, label/windows/WinInstaller/.msi'

      When the job completes on the mac, it correctly archives the artifacts as specified in the configuration. When the job completes on the windows machine it fails to find any artifacts.

      Checking the workspace on the windows slave using $WORKSPACE and I see a forward slash preceding the label name:
      ===================================
      + echo 'C:\jenkins\workspace\Project-Name\label/windows'
      C:\jenkins\workspace\Project-Name\label/windows
      + pwd
      /cygdrive/c/jenkins/workspace/Project-Name/label/windows
      ====================================

          [JENKINS-11457] Matrix project using labels cannot locate the workspace on Windows slave launched via SSH

          Gregory Boissinot added a comment -

          Could you attach your job configuration file (config.xml) in order I try to reproduce the issue.

          Gregory Boissinot added a comment - Could you attach your job configuration file (config.xml) in order I try to reproduce the issue.

          Frederik Fromm added a comment -

          Is this issue still a problem? If not, please close it.

          Anyway, is his really related to the slave setup plugin? The plugin doesn't influence any job executions. It is used on slave startup or on system configuration save to prepare slaves with needed environment, etc. I think, it is not responsible if artifacts can be copied back to the master after a job run. If you disagree, please comment. Thanks!

          Frederik Fromm added a comment - Is this issue still a problem? If not, please close it. Anyway, is his really related to the slave setup plugin? The plugin doesn't influence any job executions. It is used on slave startup or on system configuration save to prepare slaves with needed environment, etc. I think, it is not responsible if artifacts can be copied back to the master after a job run. If you disagree, please comment. Thanks!

          Frederik Fromm added a comment -

          Could you please have a look at the comments. If you agree, please close the issue or move it tho a plugin that copies artifacts after a job run. Thanks.

          Frederik Fromm added a comment - Could you please have a look at the comments. If you agree, please close the issue or move it tho a plugin that copies artifacts after a job run. Thanks.

          Gregory Boissinot added a comment -

          Without any new inputs, closing this issue.
          Please reopen if there are news

          Gregory Boissinot added a comment - Without any new inputs, closing this issue. Please reopen if there are news

            bleonard Brad Leonard
            bleonard Brad Leonard
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: