Works now, thanks to Mark pointing out the memory error.

Jenkins needs some more RAM to use external software like GIT.

Op donderdag 22 november 2012 15:50:12 UTC+1 schreef Casper het volgende:
>
> It returns nothing, but when I omit the HEAD at the end, it returns all 
> the head just fine:
>
> jenkins@damocles:/home/casper/git/4xS$ /usr/bin/git ls-remote -h 
> file:///home/casper/git/4xS/.git HEAD
> jenkins@damocles:/home/casper/git/4xS$ /usr/bin/git ls-remote -h 
> file:///home/casper/git/4xS/.git     
> 87ba7166704d85a92ef0c81768ff74d189444d6e refs/heads/develop
> 035a02f708b60353491e30fda31fd819f2cbec06 refs/heads/master
> jenkins@damocles:/home/casper/git/4xS$ 
>
>
> Op donderdag 22 november 2012 14:05:50 UTC+1 schreef Mark Waite het 
> volgende:
>>
>> That seems to indicate that the Jenkins user can't read the 
>> /home/casper/git/4xS/.git directory.
>>
>> Since you've confirmed that the Jenkins user can run the git command, 
>> could you also confirm that the Jenkins user can successfully run the 
>> command:
>>
>>  /usr/bin/git ls-remote -h file:///home/casper/git/4xS/.git HEAD
>>
>>   ------------------------------
>> *From:* Casper <daca...@gmail.com>
>> *To:* jenkins...@googlegroups.com 
>> *Sent:* Thursday, November 22, 2012 1:59 AM
>> *Subject:* Jenkins + GIT ls-remote error
>>  
>> Hey everyone,
>>
>> I've been trying to install Jenkins with the GIT plugin, but somehow the 
>> GIT plugin doesn't seem to work for me.
>>
>> I'm running Debian 5, with Jenkins as a service through apt-get. Jenkins 
>> itself works just fine. I installed the GIT plugin through Jenkins, but it 
>> does not seem to be able to use GIT properly.
>>
>> Whenever I insert a GIT repository in a Jenkins project, regardless 
>> whether it's local or remote through the ssh protocol, it always gives me 
>> this error:
>> Failed to connect to repository : Error performing command: /usr/bin/git 
>> ls-remote -h file:///home/casper/git/4xS/.git HEAD
>>
>> i have the latest version of GIT installed, and tested through sudo su 
>> jenkins whether GIT was accessible as Jenkins, which it is. As you can see 
>> I defined the absolute path to my GIT binary in the config as well, it 
>> still won't work.
>>
>> Any suggestions?
>>
>> Thanks in advance,
>>
>> Casper
>>
>>
>>   

Reply via email to