First GIT integration test fails

[Duncan Bates]

Dear sir's I'm new to seting up of Jenkins and have issues integrating with my GIt/SSH server.

Running Jenkins on a Windows 7 machine, while my GIT repository is on a Ubuntu Linux (10.0.0.131)

I've tried to understand the explained issues with integration, but seams fetch hangs as bellow

Started by user anonymous

Building in workspace C:\Program Files (x86)\Jenkins\jobs\a\workspace

 > git.exe rev-parse --is-inside-work-tree # timeout=10

Fetching changes from the remote Git repository

 > git.exe config remote.origin.url dba...@10.0.0.131:/home/git/repos/medsave # timeout=10

Fetching upstream changes from dba...@10.0.0.131:/home/git/repos/medsave

 > git.exe --version # timeout=10

using GIT_SSH to set credentials 

 > git.exe -c core.askpass=true fetch --tags --progress dba...@10.0.0.131:/home/git/repos/medsave +refs/heads/*:refs/remotes/origin/*

Build was aborted

Aborted by anonymous

Finished: ABORTED

From my commandline I can pull using;

C:\Temp>mkdir test

C:\Temp>cd test

C:\Temp\test>git init

Initialized empty Git repository in C:/Temp/test/.git/

C:\Temp\test>git pull dba...@10.0.0.131:/home/git/repos/medsave

dba...@10.0.0.131's password:

remote: Counting objects: 330, done.

remote: Compressing objects: 100% (276/276), done.

Rremote: Total 330 (delta 182), reused 0 (delta 0)eceiving objects:  99% (327/33

Receiving objects: 100% (330/330), 548.73 KiB | 186.00 K

iB/s, done.

Resolving deltas: 100% (182/182), done.

From 10.0.0.131:/home/git/repos/medsave

 * branch            HEAD       -> FETCH_HEAD

C:\Temp\test>

The jenkins service is running as Local System Account but I've also tried running it under the same account as my command prompt above, to avoid known_hosts.

I can't find a good way to provide the ssh password through Jenkins, Any quick tips to help me keep running Jenkins as is and grab git data through the dbates user account.

Regards,

Duncan

[Mark Waite]

I've not been able to use an ssh authenticated git URL with a Windows Jenkins agent running as a service.  Refer to https://issues.jenkins-ci.org/browse/JENKINS-20356 for the details of that bug.

I have been able to consistently use ssh keys with the Jenkins agent running from a Windows desktop, though not if the ssh private key requires a passphrase.  If you have a passphrase assigned to your ssh key, it may be worth creating a different (no passphrase) key for your Jenkins use.  Refer to https://issues.jenkins-ci.org/browse/JENKINS-20879 for the details of that bug.

Mark Waite

--
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/47fd6c84-0424-4782-8f05-54bf2b79b3be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite