Details
Description
Suddenly, after no version change of maven-release-plugin, our release:prepare started to fail into:
[INFO] Unable to tag SCM Provider message: The git-push command failed. Command output: ssh: Could not resolve hostname : Name or service not known fatal: The remote end hung up unexpectedly
The reason appears to be that pushing of the tag uses invalid syntax for git command:
[INFO] Executing: /bin/sh -c cd "/jenkins/job1" && git push ssh://git@github.mydomain.com myproduct-1.0.0
The problem here is that the target URL (ssh://git@github.mydomain.com) is lacking the actual repository identifier (/MyOrganization/myproduct.git) - the plugin is using just ssh://git@github.mydomain.com while it should be using something like ssh://git@github.mydomain.com/MyOrganization/myproduct.git.
I cannot come up with a reason why it started to do this so I cannot give instructions on to how to reproduce it either. For us, it occurs in one repository, while in another one using the same plugin version and configuration the problem doesn't occur.
Apparently the behavior of using ssh-URL instead of origin as remote repository has been there for ages, added in SCM-498.
Attachments
Issue Links
- duplicates
-
MRELEASE-767 releasing flat multi-module projects using git
-
- Closed
-
- relates to
-
-
- Open
-
-
-
- Closed
-