Git plugin not able to clone

[Aaron Boxer]

Hello!

I am trying to get a new Jenkins install working on windows.

I have git installed, using OpenSSH. Our server is deployed on private Gitlab
instance.

Jenkins service is logging in as the "jenkins" user, and this user
has its SSH key registered with Gitlab.

I can manually clone our repo using Git bash.

However, when I try to to get the Jenkins job to build, I get this message:


Started by user anonymous
Building in workspace C:\bin\Jenkins\workspace\master
Cloning the remote Git repository
Cloning repository git@JDMIDEVREPO:RisPacs/rispacs.git
 > git.exe init C:\bin\Jenkins\workspace\master # timeout=10
ERROR: Error cloning remote repo 'origin'
ERROR: Error cloning remote repo 'origin'
Finished: FAILURE


Any ideas?

Thanks!

Aaron

[Aaron Boxer]

Problem solved. git.exe was not in the path.

[Richard Bywater]

On a slightly different note, is there anywhere that one is supposed to see the underlying exceptions being thrown when "Error cloning from repo" happens? Looking that the code it was changed to not print the stack track out to the console and it appears to throw the original exception. However when I've tried taking a look for it, I've not been able to find it in the log or anything which makes it kind of hard to tell what problem there actually is.

Am I just not looking hard enough or does the exception, in fact, get lost?

Richard.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3e752dd8-5c73-4a83-b51b-567319a75b32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mark Waite]

The exception is being lost.  That was a mistake I made in Dec 2014.  Kohsuke fixed my mistake in a recent change.

If you're willing to use a pre-release version of the git plugin 2.3.6, you can see the results of the fix (and help with the testing of the git plugin 2.3.6 pre-release).  It will show the stack trace of the failure and usually provides enough information to diagnose the root cause.

Instructions related to the pre-release are in several bug reports, including:

https://issues.jenkins-ci.org/browse/JENKINS-26582?focusedCommentId=229640&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-229640

Mark Waite

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMui945KidpLZf_%3DoNgKMw2n8uaNY1NZH4sv3f53P_DDuzJt6w%40mail.gmail.com.

[Richard Bywater]

Ah excellent. Thanks Mark. Will see if I get a chance to try out the pre-release, else I'll just wait for the main release.

Richard.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFR158a3RmbUfFqtRf5Tidkt_2s8_797jqNRY0D%3Dk5o9A%40mail.gmail.com.