Unable to set up Git pull in Jenkins

We currently have Subversion builds in Jenkins, and are trying to add Git builds as well, using Windows filesystem access.

So far:

  • Jenkins GIT Plugin is installed.
  • Jenkins and the repositories are on the same machine, so we don’t need ssh setup.
  • Started a new Jenkins Project, and clicked on Git under Source Code Management.

We’re hitting a snag on the Repsitory URL:

Repository URL: file:////my_server/Repositories/My_Repo
Failed to connect to repository : Error performing command: git ls-remote -h file:////my_server/Repositories/My_Repo HEAD

To troubleshoot, I created a separate project which just runs Windows commands, and confirmed that:

  1. Jenkins has permission to see the repository
  2. The Jenkins path can find git.exe
  3. I can get output from Jenkins running git ls-remote file:////my_server/Repositories/My_Repo
  4. Which means my URI format is correct

Does anyone know how to fix the error with the Jenkins Git plugin not being able to connect to the repository, when Jenkins itself can?

Thank you.

  • Is there an example of JUnit Attachments Jenkins Plugin working?
  • Jenkins (Windows) very slow Git fetch
  • Jenkins plug-in developing - Maven issue: Unknown packaging: hpi
  • Running Groovy command from Jenkins using Groovy script plugin
  • Jenkins Groovy Script finding null testResultAction for a successful run
  • Jenkins Post Build Step only if there is a change in GIT/SVN
  • What is “workspace polling” in the context of Jenkins?
  • Using Jenkins Version Environment Variable in the MSBuild step
  • 2 Solutions collect form web for “Unable to set up Git pull in Jenkins”

    It turns out my file URI was correct, and even though my path variables were correct and included Git, Jenkins was unable to find it using the Windows path.

    I resolve the problem by going to:

    1. Manage Jenkins
    2. Configure System
    3. Git
    4. Path to Git executable

    And entering C:\Program Files (x86)\Git\bin\git.exe

    Hope this helps someone in the future!

    Well that would be because that’s not a valid Git URI. You need to link to the C:\ or whatever drive letter path, not to a file:// url. Also, two slashes, not three.

    Git Baby is a git and github fan, let's start git clone.