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

TF401019: The Git repository with name or identifier REPO_NAME does not exist or you do not have permissions for the operation you are attempting.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Not A Defect
    • Component/s: git-client-plugin
    • Labels:
    • Environment:
      Jenkins v.2.249.1.2
      Jenkins OS - RHEL 7
      Agent/Slave OS - Windows 10
      Agent/Slave Git Client version: Git 2.30.1

      Jenkins Plugin versions:
      git-client-plugin v3.6.0
      git plugin v4.5.2
    • Similar Issues:

      Description

      We are getting the following error after upgrading to the latest version of git scm to version 2.30.1.

      Caused by: hudson.plugins.git.GitException: Command "<C:\Program Files\Git\bin\git.exe fetch --tags --force --progress – REPO_URL +refs/heads/:refs/remotes/origin/>" returned status code 128:
      stdout:
      stderr: remote: TF401019: The Git repository with name or identifier REPO_NAME does not exist or you do not have permissions for the operation you are attempting.
      fatal: repository 'REPO_URL' not found

      The thing that I was able to find is that the plugin works with git scm version v2.26.2.  But due to security reasons, I have to install 2.30.1

      Please let me know if you need more information

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          If the only thing you changed was to upgrade from command line git 2.26.2 to command line git 2.30.1, then the issue is not likely to be in the Jenkins git client plugin or in the Jenkins git plugin. You'll need to work with the command line git team to identify what changed between the working command line git 2.26.2 and the broken command line git 2.30.1.

          I'm using command line git 2.30.0.2 on all my Windows agents and it works very well. I'm able to clone repositories provided by GitHub, Gitea, GitLab, Bitbucket, Microsoft Visual Studio Online, Assembla, and Beanstalk. I don't see anything mentioned in the transition from 2.30.0.2 to 2.30.1 that would hint of a likely problem due to authentication.

          Show
          markewaite Mark Waite added a comment - If the only thing you changed was to upgrade from command line git 2.26.2 to command line git 2.30.1, then the issue is not likely to be in the Jenkins git client plugin or in the Jenkins git plugin. You'll need to work with the command line git team to identify what changed between the working command line git 2.26.2 and the broken command line git 2.30.1. I'm using command line git 2.30.0.2 on all my Windows agents and it works very well. I'm able to clone repositories provided by GitHub, Gitea, GitLab, Bitbucket, Microsoft Visual Studio Online, Assembla, and Beanstalk. I don't see anything mentioned in the transition from 2.30.0.2 to 2.30.1 that would hint of a likely problem due to authentication.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            monil536 Monil Patel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: