This is the limitation of 5000 requests per hour. Ideally we would look into caching the github responses so that duplicate requests could be eliminated... but my preliminary analysis shows that would basically save about 50% of the requests.
The recommendation for "*Scan Organization Triggers* -> *Periodically if not otherwise run*" is *at least 8 hours* more likely somewhere between 24h and 7 days *depending on how long you are willing to wait* for a failure to deliver an event from GitHub. There are only two good reasons to scan periodically: 1. To recover from missed events (keep in mind that follow-up commits will typically recover anyway, so the only case here is a commit before bedtime not being built by morning because that event was not delivered by GitHub) 2. To run the orphaned item strategies (which is probably fine at once per week for most people) The only other reason to scan periodically is a bad one, namely * You cannot set up push notification from GitHub On 3 January 2018 at 14:19, <j.knu...@travelaudience.com> wrote: > Now that we've added *Discover tags*[1 > <https://issues.jenkins-ci.org/browse/JENKINS-34395>] and a *Build > everything*[2 > <https://github.com/jenkinsci/github-branch-source-plugin/pull/158#issuecomment-332842623>] > strategy, we're running into Github quota limits quite frequently. > > 18:58:09 GitHub API Usage: Current quota has 1110 remaining (5 over budget). > Next quota of 5000 in 13 min. Sleeping for 29 sec. > > > We've had to extend the *Scan Organization Triggers* -> *Periodically if > not otherwise run *setting to be 8 hours, to help limit the amount of > scans, but that hasn't completely solved this issue, nor is it the goal we > want to achieve. > > > There's an open bug about the time setting and github quota limits > (*JENKINS-47154*[3] <https://issues.jenkins-ci.org/browse/JENKINS-47154>), > but it's not relevant in this case. > > So I'm wondering if it's a bug in the github-branch-source-plugin? or in the > Build everything extension? or is there simply an easy way to request Jenkins > to have a higher API quota from GitHub? > > > > REF: > > 1. https://issues.jenkins-ci.org/browse/JENKINS-34395 > > 2. > https://github.com/jenkinsci/github-branch-source-plugin/pull/158#issuecomment-332842623 > > 3. https://issues.jenkins-ci.org/browse/JENKINS-47154 > > -- > 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/4079f366-003e-4ac4-8aea-462ef4ed2090%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/4079f366-003e-4ac4-8aea-462ef4ed2090%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BnPnMx9u0kKcNGyYBNW4wt%3DZUjOc%3D3_7gQiepcoLmSB4DCb7Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
