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

git plugin not cloning properly since monday(30 Jan 2023)

XMLWordPrintable

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

      git plugin not cloning properly since monday(30 Jan 2023)

       

      It's working fine if we are trying with last week jenkins image. But with the latest jenkins image, git clone is giving us the below error. When comparing the jenkins images, we don't see any changes in git plugin version or any other major image changes to be dealt with. All permissions to Bitbucket seems fine & if we clone via sh command git, it working fine. Problem is only if we try using the git plugin for cloning as shown below

      git credentialsId: '', url: 'ssh://git@bitbucket..net:7999/test-prototype/aws--*-seeder.git'

       
      ERROR: Error cloning remote repo 'origin'
      hudson.plugins.git.GitException: Command "git fetch --tags --force --progress – ssh://git@bitbucket..net:7999/cloudpb-prototype/aws-pb-testkins-seeder.git +refs/heads/:refs/remotes/origin/*" returned status code 128:
      stdout:
      stderr: fatal: detected dubious ownership in repository at '/var/jenkins_home/workspace/AWS/Platform/Jobs_Seeder/seeder@script/c8bd8428ea64a1e1a5a4c84e7d3a6c16da4e6efbf6dac0abd7f818e2f7c263bd'
      To add an exception for this directory, call:

      git config --global --add safe.directory /var/jenkins_home/workspace/AWS/Platform/Jobs_Seeder/seeder@script/c8bd8428ea64a1e1a5a4c84e7d3a6c16da4e6efbf6dac0abd7f818e2f7c263bd

            Unassigned Unassigned
            venkatd4u Venkatesh
            Votes:
            4 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: