You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking that currently we are only tracking the machines under ci.nodejs.org, but this is limited to the test machines. Should we extended it to the release machines?
I can create a PR for it, but I will need help to generate a valid token and also to add it in the repository secrets.
Hmm actually that's a good point. Do we remember which Jenkins user we're using? If it's one of the build automation GH users it won't have access to the release Cl.
Hmm actually that's a good point. Do we remember which Jenkins user we're using? If it's one of the build automation GH users it won't have access to the release Cl.
Currently, I think it is using a personal token from my account on ci.nodejs.org, as it is the one that I used when building the project before it was transferred to Node.js.
hmm. FWIW @UlisesGascon I sent an email to the other members of @nodejs/build-infra today suggesting we upgrade your level of access. Although maybe we ought to be setting up the automation with one of our Build WG-owned automation accounts.
Although maybe we ought to be setting up the automation with one of our Build WG-owned automation accounts.
Yes, 100 we should replace the current token for a one generated by a Build WG-owned automation accounts and keep the token in the secrets repo as well.
Activity
richardlau commentedon Jul 7, 2023
+1. FWIW our orka macOS release machines are currently all offline #3416
UlisesGascon commentedon Jul 7, 2023
I can create a PR for it, but I will need help to generate a valid token and also to add it in the repository secrets.
richardlau commentedon Jul 7, 2023
Hmm actually that's a good point. Do we remember which Jenkins user we're using? If it's one of the build automation GH users it won't have access to the release Cl.
[-]Should we extend jenkins-alerts to relese machines?[/-][+]Should we extend jenkins-alerts to release machines?[/+]UlisesGascon commentedon Jul 7, 2023
Currently, I think it is using a personal token from my account on
ci.nodejs.org
, as it is the one that I used when building the project before it was transferred to Node.js.richardlau commentedon Jul 7, 2023
hmm. FWIW @UlisesGascon I sent an email to the other members of @nodejs/build-infra today suggesting we upgrade your level of access. Although maybe we ought to be setting up the automation with one of our Build WG-owned automation accounts.
UlisesGascon commentedon Jul 7, 2023
Thanks! :)
Yes, 100 we should replace the current token for a one generated by a Build WG-owned automation accounts and keep the token in the secrets repo as well.
I created a PR nodejs/jenkins-alerts#262 for the changes.
UlisesGascon commentedon Jul 12, 2023
@richardlau should I use @nodejs-ci account to generate the tokens?
richardlau commentedon Jul 12, 2023
@UlisesGascon I can't remember if that account has access to Jenkins (either one). I think it's used by our Jenkins jobs to check code out of GitHub.
richardlau commentedon Jul 12, 2023
@UlisesGascon @node-forward-build might be a better account to use, depending on whether we can create API tokens with less access than the user has.
5 remaining items