Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-72574

Git plugin Version 5.2.1 - ERROR: Error cloning remote repo 'origin'

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Blocker Blocker
    • git-plugin
    • Jenkins

      since the upgrade from 5.2.0 to 5.2.1 all builds fail with
      ERROR: Error cloning remote repo 'origin'
      hudson.plugins.git.GitException: Could not init xxx\xxx

          [JENKINS-72574] Git plugin Version 5.2.1 - ERROR: Error cloning remote repo 'origin'

          Mark Waite added a comment -

          ruijterj that message will usually be followed by other messages that explain why command line git could not initialize the local repository. Failure to initialize a local repository is usually due to a problem with the local file system. It could be an ownership problem. It could be a permission problem. It could be a file system that is now mounted read-only. It could be a network file system that is offline.

          That failure message looks like it will need a question and answer series to diagnose the failure. We use the Jenkins issue tracker for bugs and enhancements. We don't use it as a support forum.

          We use https://community.jenkins.io and the Jenkins user mailing list and the Jenkins chat system for question and answer. There are more people reading those other locations than read the Jenkins issue tracker.

          I'm closing this issue as "Not a defect". If the messages that you did not include in the report are not enough to tell you how to solve the problem, please start a conversation in one of the other locations. I'm confident that this is not an issue that is specific to git plugin 5.2.1. Git plugin 5.2.1 is being used in over 70,000 installations. It was released 2 months ago and is running many, many jobs on machines like ci.jenkins.io.

          Mark Waite added a comment - ruijterj that message will usually be followed by other messages that explain why command line git could not initialize the local repository. Failure to initialize a local repository is usually due to a problem with the local file system. It could be an ownership problem. It could be a permission problem. It could be a file system that is now mounted read-only. It could be a network file system that is offline. That failure message looks like it will need a question and answer series to diagnose the failure. We use the Jenkins issue tracker for bugs and enhancements. We don't use it as a support forum. We use https://community.jenkins.io and the Jenkins user mailing list and the Jenkins chat system for question and answer. There are more people reading those other locations than read the Jenkins issue tracker. I'm closing this issue as "Not a defect". If the messages that you did not include in the report are not enough to tell you how to solve the problem, please start a conversation in one of the other locations. I'm confident that this is not an issue that is specific to git plugin 5.2.1. Git plugin 5.2.1 is being used in over 70,000 installations. It was released 2 months ago and is running many, many jobs on machines like ci.jenkins.io.

          Judith added a comment -

          markewaite the solution was to specify the location of the git binary on the node.  No recent updates in the Jenkins config where it was removed. The only change I found was the plugin update. Guess it might have been an update on the node itself. 

          Thanks

          Judith added a comment - markewaite the solution was to specify the location of the git binary on the node.  No recent updates in the Jenkins config where it was removed. The only change I found was the plugin update. Guess it might have been an update on the node itself.  Thanks

            Unassigned Unassigned
            ruijterj Judith
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: