[JIRA] (JENKINS-47154) GitHub Rate Limits are compared using the Jenkins master time not the http response's Date

[msh...@mshade.org (JIRA)]

Title: Message Title

Mike Shade edited a comment on JENKINS-47154   Re: GitHub Rate Limits are compared using the Jenkins master time not the http response's Date > {quote} I have yet to see an actual project where a larger burst results in better behaviour. {quote}   Consider a project (or org) whose API key usage is shared across multiple tools (as the GH TOS require). What we're finding is that sometimes when another tool consumes a burst of requests, Jenkins is rate limiting itself to the overall detriment. We may never drop below, say, 3k available API requests, yet are unable to spend them on queued jobs in Jenkins. It's maddening to hit this and not have a TOS-compliant workaround available within the plugin. Any chance of reconsidering a simple toggle to disable the rate limit function? Forking and separately maintaining the plugin for this purpose seems excessive.   Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.185558.1506502537000.4871.1572381841058%40Atlassian.JIRA.