Mark Waite edited a comment on Bug JENKINS-26327

I assume the problem is related to the use of relative paths in the ssh protocol URL.

When I enter an absolute path into the "Repository URL" field (ssh://mwaite@mark-pc1/home/mwaite/git/jenkins/git-client-plugin), the field is accepted and the ls-remote successfully uses the assigned credentials.

When I enter a relative path into the "Repository URL" field (ssh://mwaite@mark-pc1:git/jenkins/git-client-plugin), the git ls-remote command fails (from the job configuration UI) with the message:

Failed to connect to repository : Command "git -c core.askpass=true ls-remote -h ssh://mwaite@mark-pc1:git/jenkins/git-client-plugin HEAD" returned status code 128:
stdout: 
stderr: fatal: '/jenkins/git-client-plugin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Note that the error message is that "/jenkins/git-client-plugin" does not appear to be a git repository. I believe the command line git process (on my Linux master) is interpreting the first field after the colon as a port number or port name, not as the first element of a relative path.

I don't think the relative path syntax is supported by git using ssh protocol, unless you use the scp style syntax. Refer to this stackoverflow article for more detail on the investigations done by others.

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to