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

POSIX paths are not converted to Windows with "Cygpath Plugin"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • cygpath-plugin
    • None
    • MASTER: Jenkins 1.558. Cygpath plugin 1.5; SLAVE: Windows 7 64 bit, Windows Java (32 bit): java.version 1.6.0_45, Cygwin (64 bit): 1.7.25(0.270/5/3), Windows slave version 2.36;

      == Steps to reproduce ==

      • Install Linux Master.
      • Install Windows/Cygwin Slave and start SSH server.
      • Connect the slave to Jenkins master.
      • Configure slave's to use POSIX-style path for jenkins, i.e.: /home/jenkins
      • Start a dummy job (just to let Jenkins create WORKSPACE directory on the Slave).

      == Expected Result ==

      Jenkins creates directories under Windows/Cygwin installation: C:\cygwin64\home\jenkins

      == Actual Result ==

      Jenkins Slave simply appends C: to the POSIX path which results in creating this directory (in the root of the drive): C:\home\jenkins

      == Other notes ==

      1. The issue is related to JENKINS-21770. It is considered solved, but it's not: there is just a workaround to use Windows-style paths instead of POSIX ones. Why would anyone need "Cygpath Plugin" if configuration still have to use Windows-style paths?

      2. The problem goes on. Environment variables like WORKSPACE are still pushed in its Windows-style: C:\home\jenkins\workspace\JOB_NAME which breaks Cygwin shell scripts.

      3. In fact, there is no apparent improvements before and after installing "Cygpath Plugin".
      What it supposed to solve then?
      Or is there an example to prove it actually works?

            Unassigned Unassigned
            uvsmtid Alexey Pakseykin
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: