-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Description:
Today depending on how big an instance is we can easily hit a rate limit imposed by GitHub and this could block the ability to perform DVCS full-Sync in Jira
Suggested Solution:
The suggestion here is to deliver jira.devstatus.applink.ratelimit to GitHub integration so we can give a small delay between calls we do against GitHub, generating then the possibility to perform a full-sync even on instances with a large number of repos/branches/commits, etc.
As an additional suggestion, would be good to focus on this approach, or at least give the option in HOW we want to configure this parameter in Jira, since it can cause a general degradation, it could impact other functions like how the development panel is loaded would be good to mainly point it to sync transaction if possible.
- links to
- mentioned in
-
Page Failed to load
[JSWSERVER-25904] Support jira.devstatus.applink.ratelimit also on GitHub
| UIS | Original: 1 | New: 0 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 994541 ] |
| UIS | Original: 0 | New: 1 |
| Labels | New: ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979978 ] |
| UIS | Original: 1 | New: 0 |
| UIS | New: 1 |
| Description |
Original:
h2. Description:
Today depending on how big an instance is we can easily hit a [rate limit|https://docs.github.com/en/enterprise-cloud@latest/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#checking-the-status-of-your-rate-limit] imposed by GitHub and this could block the ability to perform DVCS full-Sync in Jira h2. Suggested Solution: (flag) The suggestion here is to deliver *_jira.devstatus.applink.ratelimit_* to GitHub integration so we can give a small delay between calls we do against GitHub, generating then the possibility to perform a full-sync even on instances with a large number of repos/branches/commits, etc. (!) _As an additional suggestion, would be good to focus on this approach, or at least give the option in HOW we want to configure this parameter in Jira, since it can cause a general degradation, it could impact other functions like how the development panel is loaded_ |
New:
h2. Description:
Today depending on how big an instance is we can easily hit a [rate limit|https://docs.github.com/en/enterprise-cloud@latest/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#checking-the-status-of-your-rate-limit] imposed by GitHub and this could block the ability to perform DVCS full-Sync in Jira h2. Suggested Solution: (flag) The suggestion here is to deliver *_jira.devstatus.applink.ratelimit_* to GitHub integration so we can give a small delay between calls we do against GitHub, generating then the possibility to perform a full-sync even on instances with a large number of repos/branches/commits, etc. (!) _As an additional suggestion, would be good to focus on this approach, or at least give the option in HOW we want to configure this parameter in Jira, since it can cause a general degradation, it could impact other functions like how the development panel is loaded would be good to mainly point it to sync transaction if possible._ |