Facing GitHub API quota issue in multi-branch pipelines. about cortx-re HOT 14 CLOSED

@mukul-seagate11 Can we consider this as priority I see lot of Jenkins jobs queued because of this issue

from cortx-re.

Also our repos are public now. I think we can remove credentials in the jobs where it only clones the repo.

from cortx-re.

@mukul-seagate11 Can you please raise ticket with GitHub enterprise support for this.

CC: @priyankdal @gowthamchinna @swatiseagate

from cortx-re.

We are using cortx-admin cred for all Jenkins related github interaction please increase the API limit for this user

from cortx-re.

We are using cortx-admin cred for all Jenkins related github interaction please increase the API limit for this user

@gowthamchinna If issue is due to user limit can we distribute jobs in my and your's credentials. We can use this as temporary adjustment till quota is not increased.

from cortx-re.

distribute jobs in my and your's credentials. We can use this as tempo

Okay @shailesh-vaidya for PR VM deployment job I am using my credentials.

from cortx-re.

This issue/pull request has been automatically marked as stale because it has not had recent activity. Tagging @shailesh-vaidya

from cortx-re.

From: GitHub [email protected]
Sent: Sunday, September 27, 2020 11:38 PM
To: Mukul Malhotra [email protected]
Subject: [GitHub Support] Re: Facing GitHub API quota issue in multi-branch pipelines

Stephen Mather(GitHub Support)Sep 27, 2020, 6:07 PM UTC

Hello Mukul,

The best way to avoid hitting our API rate limit in this scenario would be to switch from polling to https://docs.github.com/en/free-pro-team@latest/developers/webhooks-and-events/about-webhooks in order to trigger your Jenkins jobs on commit. If using webhooks is not an option for you, you could take advantage of our recent https://github.blog/changelog/2020-07-27-increase-to-api-limits-in-github-enterprise-subscriptions. When associated with an enterprise account, both GitHub Apps and OAuth Apps have an hourly limit of 15,000 API calls. Finally, you could consider splitting API calls between separate user accounts in order to avoid hitting rate limits for a single account. Let me know if you have any further questions.

Kindly
Stephen

from cortx-re.

From above update

• We can not use web-hooks as GitHub -> Jenkins connectivity for push is not configured. As Jenkins is not available outside.
• We tried using two separate users and seems issue frequency is reduced. @gowthamchinna can confirm.
• I feel we should increase rate limit as using two separate account is just temporary solution. We need create and maintain two accounts if we opt for using two accounts,

from cortx-re.

• We tried using two separate users and seems issue frequency is reduced. @gowthamchinna can confirm.
  Yes the issue frequency is reduced now.
• I feel we should increate rate limit as using two separate account is just temporary solution. We need create and maintain two accounts if we opt for using two accounts,
  Please consider user name jenkins-* or ci-* instead of cortx-admin

from cortx-re.

This issue/pull request has been automatically marked as stale because it has not had recent activity. Tagging @shailesh-vaidya

from cortx-re.

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @shailesh-vaidya for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

from cortx-re.

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @shailesh-vaidya for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

from cortx-re.

We are not facing issue now. We will re-open if issue occurs again.

from cortx-re.