Just installed git 2.31.0 - Unable to fetch

[the.n...@gmail.com]

We installed git 2.31.0 today and are now getting the following exception on every repo. Our Jenkins is 2.263.4 in Docker with Git Client 3.6.0.

hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- g...@bitbucket.org:XXX +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: Invalid option value for 'SENDENV'. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2450) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2051) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:84) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:573) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:802) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:375) 

etc....

Help! Our DevOps environment is down.

[the.n...@gmail.com]

This also happens on git 2.29.2 with Git Client 3.7.0. There is no issue with either version git when attempting the same operations.

[Mark Waite]

I see a mention of SENDENV in ssh configuration options.  Have the ssh configuration options been modified in the account that runs the Jenkins agent?

If that hunch is correct, then you could switch from ssh authentication to https username/password authentication or you could use a Bitbucket access token with username.

There is also a mention of SendEnv in the git ssh source code to communicate the git protocol version.  Since git protocol 2 is a relatively recent addition, that might be involved in the issue.  If that were the issue, it would also be resolved by using https rather than ssh.

I'm using portable git for Windows 2.31.0 to access Bitbucket from 5+ different Windows machines with ssh and https authentication.  Both are working for me.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6ff9a768-bb3b-447e-aea5-583e03fe786dn%40googlegroups.com.

[the.n...@gmail.com]

Mark,

We've moved to HTTPS for the builds. It looks like an issue with the platform's SSH version. Seems to be working well now. We've seen this happen with repos get large and complex.

Thanks,

Randall