-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Jenkins 1.404, Jenkins Git 1.1.6.
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')?
- is duplicated by
-
JENKINS-9199 Git plug-in tries to use 'git.cmd' on Unix
- Resolved
-
JENKINS-9200 Git plug-in tries to use 'git.cmd' on Unix
- Resolved