Sri Sankaran
Sri Sankaran

Reputation: 8310

Unable to get Jenkins and Git to play nice

Jenkins version: 1.429
Git plugin version: 1.1.12

I am unable to get the Git plugin to clone a Git repository. It fails with the error

Command "git clone --progress -o vipor V:\VIPOR c:\Program Files\jenkins\workspace" returned status code 128: Cloning into
c:\Program Files\jenkins\workspace...
fatal: 'V:\VIPOR' does not appear to be a git repository
fatal: The remote end hung up unexpectedly

The Git repo being cloned is on the local network. I have already tried the following

The last one I tried because I am successfully able to clone the repository in question by executing the very command being issued Git plugin, on the Jenkins server and with the same Git executable.

What am I missing?

Upvotes: 7

Views: 5215

Answers (2)

Roy Truelove
Roy Truelove

Reputation: 22446

Shot in the dark: Have you tried double slashes? eg

V:\\VIPOR

We were on a similar path as yourself (jenkins and git on a windows box) and quickly found that we needed to move to linux. We got the impression that many of the plugins were not tested throughly (or at all) on windows.

Upvotes: 0

Sagar
Sagar

Reputation: 9503

I believe the problem is this:

For a network path (such as V:) to be accessible/active, a user needs to be logged in. The Jenkins service does not actually log-in to a system, even if you run the service as you, and therefore network paths are usually not available by drive letter.

You might want to try the actual path to the repository, such as:

\\server\path\to\gitrepo

and see if that works.

Upvotes: 8

Related Questions