[Custom Tools Plugin] Tool path use Windows syntax instead of Unix syntax

[Ludovic Roucoux]

Hi,

My setup is the following :

I have a Jenkins master on Windows 7 and a Debian slave on the same machine but launched on a VM using VirtualBox.

To connect them, I use VirtualBox Plugin and JNLP connection in Jenkins. So, the slave is connected to the master.

I configured a job that installs a tool with Custom Tools Plugin. When I launch a build on the Debian slave, the Custom Tools Plugin setups a TOOL_HOME like : TOOL_HOME=/home/myName/Documents/tools/com.cloudbees.jenkins.plugins.customtools.CustomTool/myTool/

So, this home uses a unix syntax, all is ok for the moment.

During the build, when I try to run the installed tool, a IOException appears because it cannot find the program. Indeed, when I display the absolute path of the tool, I get : C:\home\myName\Documents\tools\com.cloudbees.jenkins.plugins.customtools.CustomTool\myTool\myTool.sh

So, this path uses a windows syntax and I don't understand why.

However, I launched my build on a Windows master and on a Debian master, and all is ok.

I think I have this behavior because I have my slave on a VM, but i'm not sure of that.