-
Bug
-
Resolution: Duplicate
-
Critical
-
Jenkins 1.509.2 on Linux master or slave and on Windows Server 2008 R2 slave
My 2.5 GB git repository cloned to this computer (from another local area network computer using git protocol) in about 6.5 minutes using the Git plugin 2.0 beta with the Git command line provider. The same git repository cloning from the same server to the same Jenkins machine using the jgit provider (instead of the Git CLI) still has not finished after 14 minutes. There are indications on other jobs that the first time clone of that large repository may never complete.
- duplicates
-
JENKINS-19043 jgit hangs on "Updating references" with large repositories
-
- Closed
-
[JENKINS-18960] Clone of 2.5 GB git repository is dramatically slower with jgit than command line git
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Environment | Original: Debian x86 "testing" with Oracle JDK 7 | New: Jenkins 1.509.2 slave on Windows Server 2008 R2 wih JDK 1.7.0_25 |
Environment | Original: Jenkins 1.509.2 slave on Windows Server 2008 R2 wih JDK 1.7.0_25 | New: Jenkins 1.509.2 on Linux master or slave and on Windows Server 2008 R2 slave |
Labels | Original: git2 | New: git2 performance |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Assignee | Original: Nicolas De Loof [ ndeloof ] | New: Jesse Glick [ jglick ] |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Issue is with upstream jgit implementation, outside the control of Jenkins