[JIRA] (JENKINS-58111) Github webhooks triggers a multibranch scan of all refs

[connor.po...@gmail.com (JIRA)]

Title: Message Title

connor poole created an issue   Jenkins / JENKINS-58111 Github webhooks triggers a multibranch scan of all refs Issue Type: Bug Assignee: Unassigned Components: github-api-plugin, github-branch-source-plugin, scm-api-plugin Created: 2019-06-20 04:50 Environment: jenkins 2.176.1 latest versions of all plugins in LTS Priority: Minor Reporter: connor poole Jenkins handles a monorepo well enough when using git scm with ssh clone. If we have the following repo structure: // code placeholder api-one/ Jenkinsfile api-two/ Jenkinsfile ... api-n/ Jenkinsfile We create one multibranch pipeline per Jenkinsfile in order to have many independent pipelines (CI + CD) for our projects. These projects all share common code through jenkins shared libraries and everything works ok.  However, if we want to use the github branch source and want to enable webhooks from github we immediately run into rate limit issues. We have a large repository - thousands of pushes a day. Every time a webhook is fired from github and hits jenkins all N multibranch pipelines begin scanning ALL remote refs for the repository. In our repository there are 10s of thousands of tags. A single scan on a single multibranch pipeline eliminates our entire github rate limit budget.  I am not entirely sure why jenkins must rescan the entire repo. It seems at the very least the webhook from github contains all information about the ref to be built and the individual jobs could simply take the webhook at face value and build/delete/etc without requiring a full repository scan.    Is this possible? Why does Jenkins currently scan the entire repo?   Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.200154.1561006243000.4157.1561006260096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.