-
Bug
-
Resolution: Not A Defect
-
Critical
-
ace-editor 1.1
analysis-core 1.96
analysis-model-api 7.0.2
ant 1.10
antexec 1.11
antisamy-markup-formatter 1.6
apache-httpcomponents-client-4-api 4.5.10-2.0
bouncycastle-api 2.17
branch-api 2.5.4
cloudbees-folder 6.9
cobertura 1.15
code-coverage-api 1.1.1
command-launcher 1.3
config-file-provider 3.6.2
credentials 2.3.0
display-url-api 2.3.2
external-monitor-job 1.7
forensics-api 0.6.1
git 4.0.0
git-client 3.0.0
greenballs 1.15
jackson2-api 2.10.0
javadoc 1.5
jdk-tool 1.3
jquery 1.12.4-1
jquery-detached 1.2.1
jsch 0.1.55.1
junit 1.28
junit-attachments 1.6
ldap 1.21
mailer 1.29
managed-scripts 1.4
matrix-auth 2.5
matrix-project 1.14
maven-plugin 3.4
pam-auth 1.6
scm-api 2.6.3
script-security 1.67
ssh-credentials 1.18
ssh-slaves 1.31.0
structs 1.20
token-macro 2.10
trilead-api 1.0.5
warnings 5.0.1
warnings-ng 7.2.0
windows-slaves 1.5
workflow-api 2.37
workflow-cps 2.76
workflow-job 2.36
workflow-scm-step 2.9
workflow-step-api 2.20
workflow-support 3.3ace-editor 1.1 analysis-core 1.96 analysis-model-api 7.0.2 ant 1.10 antexec 1.11 antisamy-markup-formatter 1.6 apache-httpcomponents-client-4-api 4.5.10-2.0 bouncycastle-api 2.17 branch-api 2.5.4 cloudbees-folder 6.9 cobertura 1.15 code-coverage-api 1.1.1 command-launcher 1.3 config-file-provider 3.6.2 credentials 2.3.0 display-url-api 2.3.2 external-monitor-job 1.7 forensics-api 0.6.1 git 4.0.0 git-client 3.0.0 greenballs 1.15 jackson2-api 2.10.0 javadoc 1.5 jdk-tool 1.3 jquery 1.12.4-1 jquery-detached 1.2.1 jsch 0.1.55.1 junit 1.28 junit-attachments 1.6 ldap 1.21 mailer 1.29 managed-scripts 1.4 matrix-auth 2.5 matrix-project 1.14 maven-plugin 3.4 pam-auth 1.6 scm-api 2.6.3 script-security 1.67 ssh-credentials 1.18 ssh-slaves 1.31.0 structs 1.20 token-macro 2.10 trilead-api 1.0.5 warnings 5.0.1 warnings-ng 7.2.0 windows-slaves 1.5 workflow-api 2.37 workflow-cps 2.76 workflow-job 2.36 workflow-scm-step 2.9 workflow-step-api 2.20 workflow-support 3.3
Jenkins fails sometimes with the error: Could not read from remote repository.
Jenkins runs on a local Win10 machine with access rights to our local server. On the server there is the GIT repository stored. The WIN10 user account jenkins runs the jenkins-service with has access rights to the server. Communication to the server is stable.
This happend after a update from jenkins 2.176.3 to 2.190.2 (and update of all plugins).
The error occurs very often, if more than one build-processor is used (parallel builds). If only one build-processor is used, the error occurs less, but it still occurs.
The following console output is generated:
Build wurde zeitgesteuert ausgelöst.
Running as SYSTEM
Baue auf Master in Arbeitsbereich C:\jenkins\workspace\xxxxx
No credentials specified
> git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git.exe config remote.origin.url //xxxx/xxxxx/xxxx/xxxx/xxxx/xxxx.git # timeout=10
Cleaning workspace
> git.exe rev-parse --verify HEAD # timeout=10
Resetting working tree
> git.exe reset --hard # timeout=10
> git.exe clean -fdx # timeout=10
> git.exe submodule foreach --recursive git reset --hard # timeout=10
> git.exe submodule foreach --recursive git clean -fdx # timeout=10
Fetching upstream changes from //xxxx/xxxx/xxxx/xxxx/xxxx/xxxx.git
> git.exe --version # timeout=10
> git.exe fetch --tags --force --progress – //xxxx/xxxx/xxxx/xxxx/xxxx/xxxx.git +refs/heads/:refs/remotes/origin/ # timeout=10
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from //xxxx/xxxx/xxxx/xxxx/xxxx/xxxx.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:899)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1114)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1145)
at hudson.scm.SCM.checkout(SCM.java:504)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1815)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Caused by: hudson.plugins.git.GitException: Command "git.exe fetch --tags --force --progress – //xxxx/xxxx/xxxx/xxxx/xxxx/xxxx.git +refs/heads/:refs/remotes/origin/" returned status code 128:
stdout:
stderr: fatal: '//xxxx/xxxx/xxxx/xxxx/xxxx/xxxx.git' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2372)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1985)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:80)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:563)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:897)
... 11 more
ERROR: Error fetching remote repo 'origin'
[WARNINGS] Skipping publisher since build result is FAILURE
Archiviere Artefakte
Sending e-mails to: xxxxr@xxxx.com xxxx@xxxx.com
Finished: FAILURE
The message from command line git is:
If you're accessing the remote git repository through https or ssh, that might indicate that the remote git repository is temporarily inaccessible or that remote server has some issue with its file system. In my case, I can generate that message when I use a a valid ssh private key credential to clone a repository which does not exist on a remote server which I host myself. My example looks like this:
However, when I attempt to use a valid ssh private key to clone a non-existent repository from github.com, I don't see that exact message. I see:
Based on that, I would guess that you're cloning a repository from a server that you're hosting. That internal server is temporarily unable to detect the repository, especially during times of high load (concurrent clones). You could test that theory by running multiple git clone commands on different machines at the same time.
If you're accessing the remote git repository through file system access (for example through an NFS mount or a CIFS mount), that message might indicate that command line git was unable to read the directory it needed. It might also mean that it was unable to find a specific file or to acquire a lock on a specific file. If you're accessing a git repository through a remote file access protocol, you should reconsider that choice and use the remote protocols that are included with command line git (http/https and ssh).