18:58:09 GitHub API Usage: Current quota has 1110 remaining (5 over budget). Next quota of 5000 in 13 min. Sleeping for 29 sec.
We've had to extend the Scan Organization Triggers -> Periodically if not otherwise run setting to be 8 hours, to help limit the amount of scans, but that hasn't completely solved this issue, nor is it the goal we want to achieve.
There's an open bug about the time setting and github quota limits (JENKINS-47154[3]), but it's not relevant in this case.
So I'm wondering if it's a bug in the github-branch-source-plugin? or in the Build everything extension? or is there simply an easy way to request Jenkins to have a higher API quota from GitHub?
REF:
1. https://issues.jenkins-ci.org/browse/JENKINS-34395
2. https://github.com/jenkinsci/github-branch-source-plugin/pull/158#issuecomment-332842623
3. https://issues.jenkins-ci.org/browse/JENKINS-47154
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4079f366-003e-4ac4-8aea-462ef4ed2090%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
This is the limitation of 5000 requests per hour.Ideally we would look into caching the github responses so that duplicate requests could be eliminated... but my preliminary analysis shows that would basically save about 50% of the requests.The recommendation for "Scan Organization Triggers -> Periodically if not otherwise run" is at least 8 hours more likely somewhere between 24h and 7 days depending on how long you are willing to wait for a failure to deliver an event from GitHub.There are only two good reasons to scan periodically:1. To recover from missed events (keep in mind that follow-up commits will typically recover anyway, so the only case here is a commit before bedtime not being built by morning because that event was not delivered by GitHub)2. To run the orphaned item strategies (which is probably fine at once per week for most people)The only other reason to scan periodically is a bad one, namely* You cannot set up push notification from GitHubOn 3 January 2018 at 14:19, <j.kn...@travelaudience.com> wrote:Now that we've added Discover tags[1] and a Build everything[2] strategy, we're running into Github quota limits quite frequently.18:58:09 GitHub API Usage: Current quota has 1110 remaining (5 over budget). Next quota of 5000 in 13 min. Sleeping for 29 sec.
We've had to extend the Scan Organization Triggers -> Periodically if not otherwise run setting to be 8 hours, to help limit the amount of scans, but that hasn't completely solved this issue, nor is it the goal we want to achieve.
There's an open bug about the time setting and github quota limits (JENKINS-47154[3]), but it's not relevant in this case.So I'm wondering if it's a bug in the github-branch-source-plugin? or in the Build everything extension? or is there simply an easy way to request Jenkins to have a higher API quota from GitHub?
There are only two good reasons to scan periodically:
1. To recover from missed events (keep in mind that follow-up commits will typically recover anyway, so the only case here is a commit before bedtime not being built by morning because that event was not delivered by GitHub)
2. To run the orphaned item strategies (which is probably fine at once per week for most people)
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
Checking tag v0.28.1
‘Jenkinsfile’ not found
Does not meet criteria
19:01:38 GitHub API Usage: Current quota has 901 remaining (4 under budget). Next quota of 5000 in 10 min
Checking tag v0.28.2
‘Jenkinsfile’ not found
Does not meet criteria
19:01:38 GitHub API Usage: Current quota has 897 remaining (0 under budget). Next quota of 5000 in 10 min
Checking tag v0.28.3
‘Jenkinsfile’ not found
Does not meet criteria
19:01:38 GitHub API Usage: Current quota has 894 remaining (3 over budget). Next quota of 5000 in 10 min. Sleeping for 27 sec.
19:02:06 GitHub API Usage: Current quota has 894 remaining (26 under budget). Next quota of 5000 in 9 min 53 sec
@StephenYou mention that caching the responses would "save about 50% of the requests." That seems like a significant savings to me.I'm also wondering, I'm seeing a lot of things like this in the scan log:
Checking tag v0.28.1
‘Jenkinsfile’ not found
Does not meet criteria
19:01:38 GitHub API Usage: Current quota has 901 remaining (4 under budget). Next quota of 5000 in 10 min
Checking tag v0.28.2
‘Jenkinsfile’ not found
Does not meet criteria
19:01:38 GitHub API Usage: Current quota has 897 remaining (0 under budget). Next quota of 5000 in 10 min
Checking tag v0.28.3
‘Jenkinsfile’ not found
Does not meet criteria
19:01:38 GitHub API Usage: Current quota has 894 remaining (3 over budget). Next quota of 5000 in 10 min. Sleeping for 27 sec.
19:02:06 GitHub API Usage: Current quota has 894 remaining (26 under budget). Next quota of 5000 in 9 min 53 secThat seems to me like each tag invokes an api request? And with 500+ tags, that seems like a lot of unneeded calls (most especially when Jenkins doesn't even track/build the tag).
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/628123fe-ab0f-4139-b307-15b4c4470b66%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
Checking tag v1.1.0
‘Jenkinsfile’ found
Met criteria
No changes detected: v1.1.0 (still at d11d5c94130db1b43dea147091c2cfc2d260b2c1)
19:05:09 GitHub API Usage: Current quota has 677 remaining (0 under budget). Next quota of 5000 in 6 min 50 sec
Checking tag v1.1.1
‘Jenkinsfile’ found
Met criteria
No changes detected: v1.1.1 (still at 20b7a9ccd47f9e10165268ccc252bc4b793a61fc)
19:05:09 GitHub API Usage: Current quota has 675 remaining (2 over budget). Next quota of 5000 in 6 min 50 sec. Sleeping for 26 sec.
19:05:36 GitHub API Usage: Current quota has 675 remaining (26 under budget). Next quota of 5000 in 6 min 23 sec
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3bdd60ea-91b2-4e82-9b24-b4e4583f1d08%40googlegroups.com.
Ok, than I think I misunderstand what the scan is doing.During the scan, Jenkins creates a list in memory of all branches, tags, PRs. It does it from a single api call? Or from an api call for each type?
And then while iterating over that list, for each entity Jenkins makes an api call to get the Jenkinsfile (or to find out it doesn't exist)?
If that's the case, it doesn't sound like there is much to be done in the current setup.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0acbea7c-c882-437d-abfe-859a7763996b%40googlegroups.com.