![]() |
|
|
|
|
Change By:
|
Alexey Pakseykin
(17/Apr/14 5:06 AM)
|
|
Description:
|
== Steps to reproduce ==
- Install
Linux Master.
- Install Windows/Cygwin Slave
and start SSH server
on Windows + Cygwin
.
- 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?
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
