-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSS prow uses GitHub app for authenticating #1171
Comments
The migration can be done one org/repo at a time, there are two steps:
The org/repo with managed webhooks are the targets for migration:
Note:
|
This is part of GoogleCloudPlatform#1171, I have requested installation of all repos under GoogleCloudPlatform that are currently using prow, and so far it seems like they are all approved. Trying this out on testgrid repo, will migrate others all at once if this proves to be working
This is part of GoogleCloudPlatform#1171, I have requested installation of all repos under GoogleCloudPlatform that are currently using prow, and so far it seems like they are all approved. Trying this out on testgrid repo, will migrate others all at once if this proves to be working
So far all orgs/repos have been migrated over to use GitHub app, crier, hook, and tide work well with Github now. Remaining work:
|
Sub just migrated with the fix #1313 , and it seems working fine so far |
Will mark this issue as fixed, since deck migration is not super critical at this point. Will revisit when it becomes necessary /close |
@chaodaiG: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
OSS prow currently uses bot personal access token(PAT) for authentication with GitHub APIs, which has a global rate limit of 5000 per hour. This is not very well scalable with many tenants. Switching over to GitHub app will get a rate limit per installation, which would greatly increase the rate limit exhaustion problem we have seen lately
The text was updated successfully, but these errors were encountered: