[JIRA] (JENKINS-33273) Optimize Jenkinsfile loading and branch detection

[leo.gil...@navaati.net (JIRA)]

Title: Message Title

Léo Gillot-Lamure commented on JENKINS-33273   Re: Optimize Jenkinsfile loading and branch detection Hi. We are badly affected by this problem (our git repo is 2GB) and it is still present for us even though we're on an up to date Jenkins. Here is a transcript of the first build for a PR: Branch event 21:46:11 Connecting to https://api.github.com using navaati/****** (navaati github superpower token) Checking out git https://github.com/H3IO/HyperCube.git https://github.com/H3IO/HyperCube.git to read Jenkinsfile Cloning the remote Git repository Cloning repository https://github.com/H3IO/HyperCube.git > git init /var/lib/jenkins/workspace/H3IO_HyperCube_PR-2456-QRWOPV3KS7P4NT653VHEA3YTIWGDI2HVFN6AWXB4RVJQQDYPR3UA@script # timeout=10 Fetching upstream changes from https://github.com/H3IO/HyperCube.git > git --version # timeout=10 using GIT_ASKPASS to set credentials navaati github superpower token > git fetch --tags --progress https://github.com/H3IO/HyperCube.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/H3IO/HyperCube.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/H3IO/HyperCube.git # timeout=10 Fetching upstream changes from https://github.com/H3IO/HyperCube.git using GIT_ASKPASS to set credentials navaati github superpower token > git fetch --tags --progress https://github.com/H3IO/HyperCube.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin1.url https://github.com/H3IO/HyperCube.git # timeout=10 Fetching upstream changes from https://github.com/H3IO/HyperCube.git using GIT_ASKPASS to set credentials navaati github superpower token > git fetch --tags --progress https://github.com/H3IO/HyperCube.git +refs/pull/*/head:refs/remotes/origin/pr/* Merging master commit eb08b54b49658077f34f3a5e71010ae9ccbbf879 into PR head commit a674225cb3cbd2dc4a126996a50d73262d5132f4 > git config core.sparsecheckout # timeout=10 > git checkout -f a674225cb3cbd2dc4a126996a50d73262d5132f4 > git merge eb08b54b49658077f34f3a5e71010ae9ccbbf879 # timeout=10 > git rev-parse HEAD^{commit} # timeout=10 Merge succeeded, producing a674225cb3cbd2dc4a126996a50d73262d5132f4 Checking out Revision a674225cb3cbd2dc4a126996a50d73262d5132f4 (PR-2456) > git config core.sparsecheckout # timeout=10 > git checkout -f a674225cb3cbd2dc4a126996a50d73262d5132f4 As you can see a full fetch is still done, in a new directory for each PR. Do I need to do something in particular for this fix to take effect ? Regards, Léo Gillot-Lamure. Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.