Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Not A Defect
-
Component/s: git-client-plugin
-
Labels:None
-
Environment:Jenkins ver. 2.195
Git client plugin ver. 3.2.1
Git plugin ver. 4.2.2
-
Similar Issues:
Description
Folks,
Please help me with advice on how to fix this issue in our environments. It is happening all the time.
When we attempt checkout using the jenkins plugin, we are seeing this error:
[2020-08-17T21:25:43.615Z] Cloning repository http://irepo.eur.ad.sag/scm/tsm/um-test.git
[2020-08-17T21:25:43.650Z] > git init /home/vmtest/workspace/10.7_git_release_pipeline_test_java_units # timeout=10
[2020-08-17T21:25:43.839Z] Fetching upstream changes from http://irepo.eur.ad.sag/scm/tsm/um-test.git
[2020-08-17T21:25:43.839Z] > git --version # timeout=10
[2020-08-17T21:25:43.843Z] > git fetch --no-tags --force --progress --depth=1 – http://irepo.eur.ad.sag/scm/tsm/um-test.git +refs/heads/:refs/remotes/origin/ # timeout=20
[2020-08-17T21:45:43.934Z] ERROR: Error cloning remote repo 'origin'
[2020-08-17T21:45:43.934Z] hudson.plugins.git.GitException: Command "git fetch --no-tags --force --progress --depth=1 – http://irepo.eur.ad.sag/scm/tsm/um-test.git +refs/heads/:refs/remotes/origin/" returned status code 128:
[2020-08-17T21:45:43.934Z] stdout:
[2020-08-17T21:45:43.934Z] stderr: remote: Enumerating objects: 15448, done.
[2020-08-17T21:45:43.934Z] remote: Counting objects: 0% (1/15448)
remote: Counting objects: 1% (155/15448)
remote: Counting objects: 2% (309/15448)
remote: Counting objects: 3% (464/15448)
And then it resumes work, but fails in the end with:
Receiving objects: 69% (10704/15448), 208.76 MiB | 168.00 KiB/sReceiving objects: 69% (10704/15448), 208.76 MiB | 168.00 KiB/sReceiving objects: 69% (10704/15448), 208.92 MiB | 172.00 KiB/s*Receiving objects: 69% (10704/15448), 208.99 MiB | 169.00 KiB/serror: --shallow-file died of signal 15[2020-08-17T23:05:45.622Z] fatal: index-pack failed*[2020-08-17T23:05:45.622Z] [2020-08-17T23:05:45.623Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430)[2020-08-17T23:05:45.623Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044)[2020-08-17T23:05:45.623Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:81)
Attaching the full console ouput from a linux test node in linux_console_output.txt
Attaching the full console output from a windows node in windows_console_output.txt
The errors both on windows and linux appear to be the same to me.
When I manually perform the same commands on the same Jenkins nodes, it all works just fine and quick.
Looking for suggestions how to workaround/resolve this issue
(SIDE NOTE)
I made some attempts to collect more logs by adding GIT_TRACE_PACKET=1, GIT_TRACE=1, GIT_CURL_VERBOSE=1 in the checkout step (as advised here: https://confluence.atlassian.com/bitbucketserverkb/git-clone-fails-fatal-the-remote-end-hung-up-unexpectedly-fatal-early-eof-fatal-index-pack-failed-779171803.html)I made some attempts to collect more logs by adding GIT_TRACE_PACKET=1, GIT_TRACE=1, GIT_CURL_VERBOSE=1 in the checkout step (as advised here: https://confluence.atlassian.com/bitbucketserverkb/git-clone-fails-fatal-the-remote-end-hung-up-unexpectedly-fatal-early-eof-fatal-index-pack-failed-779171803.html)
But this did not help – no additional information was collected (I wrapped my checkout step in withEnv block and also tried plain sh/bat commands). Since this did not work, I assumed the plugin requires some different logging configuration and enabled the loggers on Jenkins level under Manage Jenkins -> System Log -> Log Recorders. Added these:
hudson.plugins.git
hudson.plugins.git.GitChangeSet
hudson.plugins.git.GitSCM
hudson.plugins.git.GitStatus
hudson.plugins.git.GitTool
hudson.plugins.git.util
hudson.plugins.git.util.BuildData
hudson.plugins.git.util.GitUtils
org.jenkinsci.plugins.gitclient.Git
Unfortunately, these do not collect any info as well. Probably not the right configuration.