Hi, We often see long delays during multibranch pipeline builds.
The job shows Branch indexing > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to g...@github.com:foo/bar.git > git config remote.origin.url g...@github.com:foo/bar.git # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 using GIT_SSH to set credentials > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* Seen branch in repository origin/branch-1 Seen branch in repository origin/branch-2 ... Seen branch in repository origin/branch-559 Seen 559 remote branches There is then a long delay before it shows Obtained proj/Jenkinsfile from 61b5c00e80eaf221bb354e07ccfb3f56cb657484 Looking at the processes on the Jenkins master machine, it seems that there are just a couple of git processes (at 100% CPU) trying to checkout the different branches and get the appropriate Jenkinsfile. Does anyone know why takes so long (the master has more than enough resources)? Or how I can improve this? I'm using Jenkins ver. 2.89.4 Thanks, David -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5e68765d-b6b9-472d-9de5-b0a80e161873%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
