Tuukka Mustonen created MRELEASE-771:
----------------------------------------
Summary: release:prepare tries to push tag with invalid Git URL
Key: MRELEASE-771
URL: https://jira.codehaus.org/browse/MRELEASE-771
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: Git, prepare, scm
Affects Versions: 2.3.1
Environment: Debian 6, run form shell
Reporter: Tuukka Mustonen
Suddenly, after no version change of maven-release-plugin, our
{{release:prepare}} started to fail into:
{noformat}
[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
{noformat}
The reason appears to be that pushing of the tag uses invalid syntax for git
command:
{noformat}
[INFO] Executing: /bin/sh -c cd "/jenkins/job1" && git push
ssh://g...@github.mydomain.com myproduct-1.0.0
{noformat}
The problem here is that the target URL ({{ssh://g...@github.mydomain.com}}) is
lacking the actual repository identifier ({{/MyOrganization/myproduct.git}}) -
the plugin is using just {{ssh://g...@github.mydomain.com}} while it should be
using something like
{{ssh://g...@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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
