-
Notifications
You must be signed in to change notification settings - Fork 402
Description
I have generated classic token in GH: github-api-access with admin:org_hook scope and used in GitHub Server section in Jenkins -> Manage Jenkins -> System. Test connection shows me:
Credentials verified for user user_name, rate limit: 4998
Probably that's not enough because I reached my limit after a few days. If I click on Re-register hooks for all jobs I see Called re-register hooks for 17007 items.
For example for Github App token I have: Success, Remaining rate limit: 14998
I'm looking, why after upgrade jenkins and plugins a hook from GH does not invoke a Jenkins build.
Previously I used jenkins 2.504.3 and plugin 1.43.0 - outdated, the problem was incorrect project configuration. The only question that remains is the limit.
Originally reported by
dracorp, imported from: Github API access rate limit - switch to Github App token
- assignee:
lanwen
- status: Open
- priority: Minor
- component(s): github-plugin
- resolution: Unresolved
- votes: 0
- watchers: 2
- imported: 2025-12-08
Raw content of original issue
I have generated classic token in GH: github-api-access with admin:org_hook scope and used in GitHub Server section in Jenkins -> Manage Jenkins -> System. Test connection shows me:
Credentials verified for user user_name, rate limit: 4998
Probably that's not enough because I reached my limit after a few days. If I click on Re-register hooks for all jobs I see Called re-register hooks for 17007 items.
For example for Github App token I have: Success, Remaining rate limit: 14998
I'm looking, why after upgrade jenkins and plugins a hook from GH does not invoke a Jenkins build.Previously I used jenkins 2.504.3 and plugin 1.43.0- outdated, the problem was incorrect project configuration. The only question that remains is the limit.
environment
jenkins: 2.528.1<br/>
github-plugin: 1.45.0