You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tuukka Mustonen (JIRA)" <ji...@codehaus.org> on 2012/06/11 17:30:21 UTC
[jira] (MRELEASE-771) release:prepare tries to push tag with
invalid Git URL
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://git@github.mydomain.com myproduct-1.0.0
{noformat}
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.
--
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
[jira] (MRELEASE-771) release:prepare tries to push tag with
invalid Git URL
Posted by "Andreas Lüdeke (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312491#comment-312491 ]
Andreas Lüdeke commented on MRELEASE-771:
-----------------------------------------
i was able to reproduce this issue in our setup. I was able to workaround it by moving the aggregator pom into the root of my project structure. Before that the aggregator pom was placed in a sub folder of our project structure.
> 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://git@github.mydomain.com myproduct-1.0.0
> {noformat}
> 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.
--
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
[jira] (MRELEASE-771) release:prepare tries to push tag with
invalid Git URL
Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315376#comment-315376 ]
Darryl L. Miles commented on MRELEASE-771:
------------------------------------------
Related MRELEASE-767 ? The original reporter did not convey the hierarchical organization of the projects he has. I would guess the affected project is one or two levels down in module hierarchy.
> 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://git@github.mydomain.com myproduct-1.0.0
> {noformat}
> 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.
--
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
[jira] (MRELEASE-771) release:prepare tries to push tag with
invalid Git URL
Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315010#comment-315010 ]
Darryl L. Miles commented on MRELEASE-771:
------------------------------------------
This works for me the <project><scm><connection> element setup with the full SCM URL including the path part. I have used 2.0 and 2.3.2 version of the plugin.
> 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://git@github.mydomain.com myproduct-1.0.0
> {noformat}
> 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.
--
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
[jira] (MRELEASE-771) release:prepare tries to push tag with
invalid Git URL
Posted by "Darryl L. Miles (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315022#comment-315022 ]
Darryl L. Miles commented on MRELEASE-771:
------------------------------------------
Maybe useful reference for you to verify you are configuring your project correctly ?
https://maven.apache.org/scm/git.html
There is provision for different fetch/push URLs.
I vote to close this bug and if the problem still exists please ensure to attach your actual Effective POM of the project that does not work for you so it can be checked as being a good configuration that should work.
> 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://git@github.mydomain.com myproduct-1.0.0
> {noformat}
> 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.
--
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