-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I run git push from a Jenkins-initiated shell, I get an error 'SSH-2.0-OpenSSH_9.6' is not recognized as an internal or external command #4926
Comments
It's hard to deduce from the provided information what is going on. The problem might be a configuration setting. Look at the output of Another possible way to find out more is to call |
So I did the GIT_TRACE commands.
There's still nothing remotely pointing to why it's using that as a command from Jenkins. |
Okay, so that means
And this makes it look as if it is not Git's
It might help to configure it, hard-coding the path to Git for Windows' But you could at least write a shell script that outputs all kinds of interesting information such as the contents of the |
Setup
64 bit
$ git --version --build-options
git version 2.44.0.windows.1
cpu: x86_64
built from commit: ad0bbff
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
Windows 2022 server
$ cmd.exe /c ver
Microsoft Windows [Version 10.0.20348.2340]
One of the following:
Editor Option: Notepad
Custom Editor Path:
Default Branch Option:
Path Option: Cmd
SSH Option: OpenSSH
Tortoise Option: false
CURL Option: OpenSSL
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Git Pull Behavior Option: Merge
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Disabled
Enable Pseudo Console Support: Disabled
Enable FSMonitor: Disabled
to the issue you're seeing?
It works when running directly as a user, but fails when running from a jenkins ssh agent
Details
CMD (also fails in powershell)
Minimal, Complete, and Verifiable example
this will help us understand the issue.
The text was updated successfully, but these errors were encountered: