(replies inline) On Fri, 05 Jan 2018, Alicia Doblas wrote:
> Hi, > > a couple of months ago we had the same problem. After improving the > discover filter of the branch/tag/PR calls, there weren't too much to > do...so we decided to "by-pass" the api of github by using different users. > Looks like the api limit applies to a single user, so the "solution" for us > was to split our jobs into different groups, each of them using a different > user for the api call. > > By changing this configuration we can manage 5000 req/hour x N groups. This is very very much against the GitHub.com terms of service, which states that one legal entity can have one free machine account. https://help.github.com/articles/github-terms-of-service/#b-account-terms - R. Tyler Croy ------------------------------------------------------ Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: rty...@jabber.org % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F ------------------------------------------------------ -- 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/20180106042952.4wlg7enl4dbnnw5i%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
