Access for @shipujin to kick off https://ci.nodejs.org/job/node-test-commit-loongarch64
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
@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 - https://github.com/nodejs/build/issues/3540#issuecomment-1916603497
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the referenced build issue comment and the Jenkins job node-test-commit-loongarch64 at ci.nodejs.org. Confirm that @shipujin already has physical-machine access and determine the Jenkins permission needed for starting this single job. Done means he can initiate that CI job without broader access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100