[JIRA] (JENKINS-49631) git-plugin setup fails

1 view
Skip to first unread message

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 19, 2018, 11:12:02 AM2/19/18
to jenkinsc...@googlegroups.com
francesco labate created an issue
 
Jenkins / Bug JENKINS-49631
git-plugin setup fails
Issue Type: Bug Bug
Assignee: Mark Waite
Components: git-plugin
Created: 2018-02-19 16:11
Environment: Jenkins ver. 2.46.2
Git client plugin 2.7.1
Git plugin 3.7.0
and all related dependencies have been successfully installed
Git version on the RedHat node is 2.12.2
Bitbucket v4.14.2
Priority: Major Major
Reporter: francesco labate

When setting in Jenkins, into Job->Configuration->SourceCodeManagement->Git->RepositoryURL the following line: ssh://g...@myserver.mydomain:port.myrepository.git

I have following error displayed below immediatly in red by the Jenkins Git Plugin:

Failed to connect to repository : Error performing command: git ls-remote -h ssh://g...@myserver.mydomain:port.myrepository.git HEAD

The git.exe ls-remote <repo url> command also works correctly from git bash of the node and Git is in the path and its path is specified into tools in the node configuration; besides my permissions are set correctly and the clone of this repository works correctly so, it should be a bug with the Git Plugin.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 19, 2018, 11:18:02 AM2/19/18
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
Change By: Mark Waite
Assignee: Mark Waite

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 19, 2018, 11:22:02 AM2/19/18
to jenkinsc...@googlegroups.com
Mark Waite commented on Bug JENKINS-49631
 
Re: git-plugin setup fails

As far as I can tell, that is not a valid URL for a git repository that uses SSH protocol. You reported the repository URL as:

ssh://g...@myserver.mydomain:port.myrepository.git

The correct URL would be:

ssh://g...@myserver.mydomain:port/myrepository.git

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 20, 2018, 4:25:02 AM2/20/18
to jenkinsc...@googlegroups.com
francesco labate updated an issue
Change By: francesco labate
Priority: Major Critical

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 20, 2018, 4:27:01 AM2/20/18
to jenkinsc...@googlegroups.com
francesco labate commented on Bug JENKINS-49631
 
Re: git-plugin setup fails

yes, you are right, this is what I used:

ssh://g...@myserver.mydomain:port/myrepository.git

and the problem is the one described in this ticket.

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 20, 2018, 4:32:02 AM2/20/18
to jenkinsc...@googlegroups.com
francesco labate updated an issue
Change By: francesco labate
Environment:
Jenkins ver. 2.46.2
Git client plugin 2.7.1
Git plugin 3.7.0
and all related dependencies have been successfully installed as per attached screenshot.

Git version on the RedHat node is 2.12.2
Bitbucket v4.14.2

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 20, 2018, 4:32:03 AM2/20/18
to jenkinsc...@googlegroups.com
francesco labate updated an issue
Change By: francesco labate
Attachment: installed git plugins.jpg

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 21, 2018, 12:53:02 PM2/21/18
to jenkinsc...@googlegroups.com
Mark Waite commented on Bug JENKINS-49631
 
Re: git-plugin setup fails

It is quite unlikely that this is a bug in the git plugin. There are 130 000+ installations of the git plugin. It is more likely that there is a problem in your local configuration.

Diagnosing your configuration is best done through channels other than a bug report. Please use the chat system, or the Jenkins users mailing list rather than the bug tracker.

When you begin that discussion on one of those other channels, you'll have more people who might be able to help and a better chance of reaching an answer.

They will probably ask for information like:

  • What form of private key credential are you using with that ssh URL?
  • Confirm that you are not attempting to use a username/password credential with that ssh URL
  • When you say "git.exe" in your question, are you referring to a Windows agent or something different?
  • Is there any other message in the output besides "Failed to connect to repository"?
  • If you save that job and run the job, what is the output of the job?

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 21, 2018, 12:53:02 PM2/21/18
to jenkinsc...@googlegroups.com
Mark Waite resolved as Not A Defect
Change By: Mark Waite
Status: Open Resolved
Resolution: Not A Defect

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 21, 2018, 12:54:01 PM2/21/18
to jenkinsc...@googlegroups.com
It is quite unlikely that this is a bug in the git plugin.  There are 130 000+ installations of the git plugin.  It is more likely that there is a problem in your local configuration.

Diagnosing your configuration is best done through channels other than a bug report.  Please use the chat system, or the Jenkins users mailing list rather than the bug tracker.

When you begin that discussion on one of those other channels, you'll have more people who might be able to help and a better chance of reaching an answer.

They will probably ask for information like:
* What form of private key credential are you using with that ssh URL?
* Confirm that you are not attempting to use a username/password credential with that ssh URL
* When you say "git.exe" in your question, are you referring to a Windows agent or something different?
* Is there any other message in the output besides "Failed to connect to repository"?
* If you save that job and run the job, what is the output of the job?


If you can provide sufficient configuration instructions that others can duplicate your configuration and see the failure, then a bug report is the correct approach.

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 22, 2018, 4:23:02 AM2/22/18
to jenkinsc...@googlegroups.com
francesco labate commented on Bug JENKINS-49631
 
Re: git-plugin setup fails

Mark, I reopen the issue as I am available to provide sufficient configuration instructions to allow others to reproduce the issue, ask me the info you still need please, I start answering your questions:

1) there is a mistake in what I wrote in the bug description: from the windows server which guests Jenkins using bash is possible to clone the repository; it is also possible from the node Linux RH using git 2.12.2 command lline.

2) I am using in both cases a couple of private/pubblic ssh keys and they work.

3) there is no other message in the output;

4) the log of the console is attached, apparently it works.

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 22, 2018, 4:25:03 AM2/22/18
to jenkinsc...@googlegroups.com
francesco labate reopened an issue
 

Please let me know which information do you need to reproduce and debug the issue and i will provide you.

Change By: francesco labate
Resolution: Not A Defect
Status: Resolved Reopened

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 22, 2018, 4:26:02 AM2/22/18
to jenkinsc...@googlegroups.com
francesco labate updated an issue
Change By: francesco labate
Attachment: Output Console.txt

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 22, 2018, 4:51:02 AM2/22/18
to jenkinsc...@googlegroups.com
francesco labate updated an issue
Change By: francesco labate
Priority: Critical Major

francesco.labate@external.thalesaleniaspace.com (JIRA)

unread,
Feb 22, 2018, 6:18:02 AM2/22/18
to jenkinsc...@googlegroups.com
 
Re: git-plugin setup fails

Further details about the ssh-key, it has been generated using the command:

ssh-keygen -t rsa

and enabling the flag:

PubkeyAuthentication yes

in both files below:

/etc/ssh/sshd_config

/etc/ssh/config

then restarting the service jenkins.

As said this key works well using the git clone command from the node.

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 22, 2018, 7:32:02 AM2/22/18
to jenkinsc...@googlegroups.com
Mark Waite resolved as Not A Defect
 

Closing. Not a defect. User configuration error that needs to be investigated somewhere other than a bug report.

Change By: Mark Waite
Status: Reopened Resolved
Resolution: Not A Defect

mark.earl.waite@gmail.com (JIRA)

unread,
Oct 22, 2019, 9:34:26 PM10/22/19
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Not A Defect
Change By: Mark Waite
Status: Resolved Closed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages