The feature has caused problems on gitea instance; The gitea instance expects the username to be fixed "git". @pavog @lafriks

But it should still use git if no username is set in ssh credentials secret

@lafriks la Yes. But the jenkin configuration always provides a valid username; ssh://username@xxx does not work for ssh credentials with username; I am not sure why the behavior has changed. Is it due to gitea update?

@Piping Which Gitea plugin version do you use? 1.4.4 or 1.4.5?

@justusbunsi I used 1.4.4; Now I downgrade the plugin to 1.4.3 for the work purpose;

@Piping For narrowing down the issue it would be really helpful if you could file an issue on Jenkins' JIRA with details on this: (Gitea plugin version for completeness), other related plugins and their versions, Gitea version, Jenkins version, Jenkins configuration Screenshots and error logs.

As @lafriks said this should be a non-breaking change.
I myself use ssh checkout with the Gitea plugin every day and am not facing the issue. So it would be great to have your details to find the differences.