Access for @shipujin to kick off https://ci.nodejs.org/job/node-test-commit-loongarch64

[mhdawson]

@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.

[sxa]

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!) :-)

[UlisesGascon]

+1

[mhdawson]

I've updated the job to add @shipujin

@shipujin you should now be able to start the CI job.

[shipujin]

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