-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.146
Default plugins
When I run Jenkins from the war file on Windows with the default plugins, it defines the git implementation as "git.exe" instead of "git".
When I add a Linux agent, it incorrectly attempts to use "git.exe" as the git executable on the Linux agent.
It should use "git" as the default git implementation on Linux agents even when connected from a Windows master.
Preferred solution is to use a Linux controller rather than a Windows controller because more Jenkins users run Linux controllers than Windows controllers. If that solution is not viable, then an alternate solution is to define a new git implementation like "git-linux" with the path to the git executable on the Linux agents (typically /usr/bin/git or git).
- is duplicated by
-
JENKINS-72416 There's no such executable C:\Program Files\Git\bin\git.exe in PATH: /opt/java/openjdk/bin, /usr/local/sbin, /usr/local/bin, /usr/sbin, /usr/bin, /sbin, /bin.
-
- Closed
-
[JENKINS-54053] Git plugin uses git.exe as default on Windows server, even for Linux agents
Assignee | Original: Mark Waite [ markewaite ] |
Description |
Original:
When I run Jenkins from the war file on Windows with the default plugins, it defines the git implementation as "git.exe" instead of "git". When I add a Linux agent, it incorrectly attempts to use "git.exe" as the git executable on the Linux agent. It should use "git" as the default git implementation on Linux agents even when connected from a Windows master. |
New:
When I run Jenkins from the war file on Windows with the default plugins, it defines the git implementation as "git.exe" instead of "git". When I add a Linux agent, it incorrectly attempts to use "git.exe" as the git executable on the Linux agent. It should use "git" as the default git implementation on Linux agents even when connected from a Windows master. Preferred solution is to use a Linux master rather than a Windows master because more Jenkins users run Linux masters than Windows masters. If that solution is not viable, then an alternate solution is to define a new git implementation like "git-linux" with the path to the git executable on the Linux agents (typically /usr/bin/git). |
Priority | Original: Minor [ 4 ] | New: Critical [ 2 ] |
Attachment | New: image-2020-08-27-11-35-00-215.png [ 52447 ] |
Priority | Original: Critical [ 2 ] | New: Minor [ 4 ] |
Description |
Original:
When I run Jenkins from the war file on Windows with the default plugins, it defines the git implementation as "git.exe" instead of "git". When I add a Linux agent, it incorrectly attempts to use "git.exe" as the git executable on the Linux agent. It should use "git" as the default git implementation on Linux agents even when connected from a Windows master. Preferred solution is to use a Linux master rather than a Windows master because more Jenkins users run Linux masters than Windows masters. If that solution is not viable, then an alternate solution is to define a new git implementation like "git-linux" with the path to the git executable on the Linux agents (typically /usr/bin/git). |
New:
When I run Jenkins from the war file on Windows with the default plugins, it defines the git implementation as "git.exe" instead of "git".
When I add a Linux agent, it incorrectly attempts to use "git.exe" as the git executable on the Linux agent. It should use "git" as the default git implementation on Linux agents even when connected from a Windows master. Preferred solution is to use a Linux controller rather than a Windows controller because more Jenkins users run Linux controllers than Windows controllers. If that solution is not viable, then an alternate solution is to define a new git implementation like "git-linux" with the path to the git executable on the Linux agents (typically {{/usr/bin/git}} or {{git}}). |
Link |
New:
This issue is duplicated by |