Sender: jenkinsci-users@googlegroups.com
On-Behalf-Of: ty...@monkeypox.org
Subject: Re: github quota limit when scanning with the addition of tags
Message-Id: <20180106042952.4wlg7enl4dbnn...@blackberry.coupleofllamas.com>
Recipient: andrew.h...@nab.com.au

The information contained in this email and its attachments may be confidential.
If you have received this email in error, please notify the sender by return 
email,
delete this email and destroy any copy.

Any advice contained in this email has been prepared without taking into
account your objectives, financial situation or needs. Before acting on any
advice in this email, National Australia Bank Limited (NAB) recommends that
you consider whether it is appropriate for your circumstances.
If this email contains reference to any financial products, NAB recommends
you consider the Product Disclosure Statement (PDS) or other disclosure
document available from NAB, before making any decisions regarding any
products.

If this email contains any promotional content that you do not wish to receive,
please reply to the original sender and write "Don't email promotional
material" in the subject.

-- 
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/9633fa14-c91f-4969-b6ab-de03e20cebac%40journal.report.generator.
For more options, visit https://groups.google.com/d/optout.
--- Begin Message ---
(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.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to