-
Notifications
You must be signed in to change notification settings - Fork 119
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
need to generate a Jenkins API new token #201
Comments
I don't have privileges do see those tokens anymore, so I can't help update them. FYI all the secrets the bot gets provided as environment variables are defined in the secrets repo. |
Is that a @nodejs/build-infra issue then? |
The ones who has read/write access to the github-bot secrets are a subset of the build WG, I'd ping @joyeecheung @maclover7 @rvagg. For ref these secrets are defined in |
BTW: that group might need a refresh - nodejs/build#1575 |
I can take a look at this in the next day or so |
OK, figured it out. Login credentials for nodejs-github-bot are in secrets/build/github-bot/github_bot_account.md. So I've logged in to Jenkins as that and made a new API token there. It's now in secrets/build/github-bot/deployment_secrets.md and also on the gh-bot server and I've restarted its services. Documented some of this in the user description @ https://ci.nodejs.org/user/nodejs-github-bot/ What's the best way to test this or do I just watch for the next PR to see if it's worked? |
Works: nodejs/node#24538 |
New version of Jenkins revoked all API tokens.
https://ci.nodejs.org/user/nodejs-github-bot/configure
The text was updated successfully, but these errors were encountered: