We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@shipujin has been working to get loongarch64 runs going in the CI.
Not being able to kickoff CI runs is slowing that down. For example see - #3540 (comment)
He already has access to the physical machine so I think giving him the privs in Jenkins to start that one job is ok as well.
@nodejs/build, unless there are objections I'll give him access this Friday. If I get enough +1s before then I'll do it earlier.
The text was updated successfully, but these errors were encountered:
Yep definitely +1 from me especially since it's for running stuff on a machine they already have direct access to (and provided to us!) :-)
Sorry, something went wrong.
+1
I've updated the job to add @shipujin
@shipujin you should now be able to start the CI job.
I've updated the job to add @shipujin @shipujin you should now be able to start the CI job.
Thank you very much. I'll go test the build and fix the current network timeout issue
Best regards
No branches or pull requests
@shipujin has been working to get loongarch64 runs going in the CI.
Not being able to kickoff CI runs is slowing that down. For example see - #3540 (comment)
He already has access to the physical machine so I think giving him the privs in Jenkins to start that one job is ok as well.
@nodejs/build, unless there are objections I'll give him access this Friday. If I get enough +1s before then I'll do it earlier.
The text was updated successfully, but these errors were encountered: