[
https://issues.jenkins-ci.org/browse/JENKINS-9201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sogabe resolved JENKINS-9201.
-----------------------------
Resolution: Not A Defect
> Git plug-in tries to use 'git.cmd' on Unix
> ------------------------------------------
>
> Key: JENKINS-9201
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9201
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Affects Versions: current
> Environment: Jenkins 1.404, Jenkins Git 1.1.6.
> Reporter: Arve Knudsen
> Assignee: abayer
>
> If I don't explicitly configure the Git tool location for a slave, the Git
> plug-in assumes the command to be 'git.cmd' regardless of the platform.
> Example from job log on Solaris 5.10:
> ERROR: Cause: Error performing command: git.cmd clone -o origin ssh://<repo>
> <workspace>
> git.cmd: not found
> It should be noted that this behaviour is seen in a matrix project, with both
> Windows and Unix slaves. It's possible that the "mother" job Jenkins uses to
> trigger the jobs on the slaves runs on Windows, and that this confuses the
> Git plug-in somehow.
> Why is Git's tool location parameter called 'Home' btw (that's the parameter
> I have to set to 'git')?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
