[JIRA] [git-plugin] (JENKINS-26680) Extraneous Forward-Slash in ssh:// path to repository

Thu, 16 Apr 2015 06:45:32 -0700

 
Mark Waite edited a comment on Bug JENKINS-26680

I performed some further tests with multiple versions of git. I can't find a way to make any of them work with a relative path in an ssh URL. The tests used git / operating system versions:

  • git 1.7.1, CentOS 6.6, "git clone ssh://mwaite@mark-pc1:bin/" fails and reports "ssh: Could not resolve hostname mark-pc1:bin: Name or service not known"
  • git 1.7.2.5, Debian 6, "git clone ssh://mwaite@mark-pc1:bin/" fails and reports "ssh: Could not resolve hostname mark-pc1:bin: Name or service not known"
  • git 1.7.10.4, Debian 7, "git clone ssh://mwaite@mark-pc1:bin/" fails and reports "ssh: Could not resolve hostname mark-pc1:bin: Name or service not known"
  • git 2.1.4, Debian Testing, "git clone ssh://mwaite@mark-pc1:bin/" fails and reports "fatal: '/' does not appear to be a git repository"
  • git 2.2.1, Ubuntu 14.04, "git clone ssh://mwaite@mark-pc1:bin/" fails and reports "fatal: '/' does not appear to be a git repository"

What git version are you running which passed that test? Are you using command line git or JGit?

Later investigations in JENKINS-27483 showed that msysgit on Windows allows that syntax. It seems to be the only platform which allows it.

I agree that this is a bug (the plugin should not rewrite the ssh URL), but even if that bug is fixed, the URL syntax being used is not platform portable. It only works on msysgit on Windows.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to