[JIRA] (JENKINS-61439) Independent git operations share singular JVM lock

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title

Mark Waite commented on JENKINS-61439   Re: Independent git operations share singular JVM lock I'm not sure what you mean by "remote name". Can you explain further? I would assume that the lock is being acquired on the URL of the remote repository. A single remote repository URL has a single cache directory on the Jenkins master. That cache is locked for the duration of an update to retrieve the Jenkinsfile for each branch. If your repository has grown significantly or if the git cache on the Jenkins master has not recently been garbage collected, you might try performing a git gc on the specific cache directory on the master, just as an exploration to see if that would improve performance. We could consider multiple copies of the cache on the Jenkins master with some way of choosing one of the pool of caches. That seems more complicated and has different challenges in trying to decide how deep to make the pool of caches and how to avoid disc space bloat in the pool of caches. Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205117.1583948832000.5798.1583955060148%40Atlassian.JIRA.