[JIRA] (JENKINS-51542) Git checkout is slower than the command line execution
Title: Message Title Marcelo Oliveira edited a comment on JENKINS-51542 Re: Git checkout is slower than the command line execution FYI, I was also having this problem and it boiled down to shallow depth = 1 clone, not sure if it's the same but it may help others.3m30s with depth =1{noformat}00:00:02.788 > /usr/bin/git fetch --tags --progress --depth=1 -- g...@git.xyz.com:repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:03:26.147 > /usr/bin/git config remote.origin.url g...@git.xyz.com:repo.git # timeout=60{noformat}40s normal fetch {noformat}00:00:02.472 > /usr/bin/git fetch --tags --progress -- g...@git.xyz.com:apps/repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:00:42.424 > /usr/bin/git config remote.origin.url g...@git.xyz.com:apps/repo.git # timeout=60 {noformat}*Node:*git version 2.23.0git-lfs/2.10.0 (GitHub; darwin amd64; go 1.13.6)*Jenkins:*git-client 3.1.1git-plugin: 4.1.1.*Git server:*GitLab Enterprise Edition 12.7.2-ee Maybe the server spends more time figuring out the shallow copy than just send the pack files? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190925.1527240014000.5767.1582589280928%40Atlassian.JIRA.
[JIRA] (JENKINS-51542) Git checkout is slower than the command line execution
Title: Message Title Marcelo Oliveira edited a comment on JENKINS-51542 Re: Git checkout is slower than the command line execution FYI, I was also having this problem and it boiled down to shallow depth = 1 clone, not sure if it's the same but it may help others. 3m30s ~3m24s with depth =1{noformat}00:00:02.788 > /usr/bin/git fetch --tags --progress --depth=1 -- g...@git.xyz.com:repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:03:26.147 > /usr/bin/git config remote.origin.url g...@git.xyz.com:repo.git # timeout=60{noformat} ~ 40s normal fetch{noformat}00:00:02.472 > /usr/bin/git fetch --tags --progress -- g...@git.xyz.com:apps/repo.git +refs/heads/*:refs/remotes/origin/* # timeout=15000:00:42.424 > /usr/bin/git config remote.origin.url g...@git.xyz.com:apps/repo.git # timeout=60 {noformat}*Node:*git version 2.23.0git-lfs/2.10.0 (GitHub; darwin amd64; go 1.13.6)*Jenkins:*git-client 3.1.1git-plugin: 4.1.1.*Git server:*GitLab Enterprise Edition 12.7.2-eeMaybe the server spends more time figuring out the shallow copy than just send the pack files? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190925.1527240014000.5769.1582589280974%40Atlassian.JIRA.
[JIRA] (JENKINS-51542) Git checkout is slower than the command line execution
Title: Message Title Marcelo Oliveira commented on JENKINS-51542 Re: Git checkout is slower than the command line execution FYI, I was also having this problem and it boiled down to shallow depth = 1 clone, not sure if it's the same but it may help others. 3m30s with depth =1 00:00:02.788 > /usr/bin/git fetch --tags --progress --depth=1 -- g...@git.xyz.com:repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:03:26.147 > /usr/bin/git config remote.origin.url g...@git.xyz.com:repo.git # timeout=60 40s normal fetch 00:00:02.472 > /usr/bin/git fetch --tags --progress -- g...@git.xyz.com:apps/repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:00:42.424 > /usr/bin/git config remote.origin.url g...@git.xyz.com:apps/repo.git # timeout=60 Node: git version 2.23.0 git-lfs/2.10.0 (GitHub; darwin amd64; go 1.13.6) Jenkins: git-client 3.1.1 git-plugin: 4.1.1. Git server: GitLab Enterprise Edition 12.7.2-ee Maybe the server spends more time figuring out the shallow copy than just send the pack files? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)