A. Ullrich commented on Bug JENKINS-14447

We have the same problem with one of our slaves running CentOS 6.3 64 bit and jenkins version 1.481. Interestingly enough though the first two jobs I moved to this slave did not show this problem. My stack trace has slightly different line numbers:

git version 1.7.1
ERROR: Error cloning remote repo 'origin' : Could not clone ssh://git@myserver/my-repo.git
hudson.plugins.git.GitException: Could not clone ssh://git@myserver/my-repo.git
	at hudson.plugins.git.GitAPI.clone(GitAPI.java:271)
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1102)
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2200)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: hudson.plugins.git.GitException: Command "git clone --progress -o origin ssh://git@myserver/my-repo.git /home/builder/jenkins-build/workspace/my-repo" returned status code 128:
stdout: 
stderr: fatal: Could not get current working directory: No such file or directory

	at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:863)
	at hudson.plugins.git.GitAPI.access$000(GitAPI.java:40)
	at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:267)
	at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:246)
	at hudson.FilePath.act(FilePath.java:842)
	at hudson.FilePath.act(FilePath.java:824)
	at hudson.plugins.git.GitAPI.clone(GitAPI.java:246)
	... 12 more

Anything anybody wants me to do in order to figure out the cause of this?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to