I thought that I had seen that failure when I enabled "fast remote polling" and had not yet cloned the git repository.
My quick web search did not show that as a bug, so I may be wrong, but it won't hurt to try disabling fast remote polling (it is in the Advanced section of the git plugin settings for your job). I tried to duplicate the problem myself and was unable to duplicate it, so I'm probably not using exactly the steps you are using. Mark Waite >________________________________ > From: Jeff <predato...@gmail.com> >To: jenkinsci-users@googlegroups.com >Sent: Thursday, January 3, 2013 1:35 PM >Subject: Git question... > > >I have some Git projects (internal gitolite repository) that I'm configuring >and when I put the git repo URL in, it shows this error below field: > > >Failed to connect to repository : Error performing command: ls-remote -h gitolite@mygitrepo:/myproject.git HEAD > > > >If I login as the user that Jenkins is running as (tomcat7 on Ubuntu 12.10) >and type the same command, I don't get an error, but I also don't see any >output of any kind. > > >If I leave off the "HEAD" option, I get a response like: > > >6156c0bd163a1b9e3a878e889be53c5b80f48c36 refs/heads/master > > >Am I doing something wrong? If I just save the job, it seems to clone and >build just fine but I haven't tried any Maven releases yet so I don't know if >that works. > > >I can't see in any logs what the specific error might be. Thoughts? > >-- > >Jeff Vincent >predato...@gmail.com >See my LinkedIn profile at: >http://www.linkedin.com/in/rjeffreyvincent >I ♥ DropBox !! > >
