Interest in establishing a "Build Helper" role
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
@nodejs/build As we all know we have a lot of burden in the build working group with never enough volunteers to shoulder it all.
I propose we look into creating a sort of "Build Helper" style role that can help expand our reach and help solve problems faster. I was thinking something along of the lines of offering a subset of the node/collaborators to be come "Build Helpers".
Initially, i'm thinking a "Build Helper" would have access to a subset of our test machines, allowing them to deal with simple problems (restarting the Jenkins agent, file permissions, clearing up workspace, etc.). By limiting the "Build Helper" role to a subset of node/collaborators, I think we can still ensure that everyone with access fulfils the trust requirement. The aim would be that the "Build Helper" role only allows permissions to solve the simple problems/perform certain actions on the machine.
I think this could maybe be achieved through jenkins jobs that only the "build helpers" can access to run like "force workspace clean" or similar (similar to the force windows updates jobs)
I'm opening this issue to just brainstorm what ideas other members have, I think possibly asking the collaborators what common problems they face, and whether they would be willing to fix it themselves if its a small issue.
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
Start with the proposed Jenkins jobs and the existing “force windows updates” jobs, then review the node/collaborators access model. Done would require an agreed Build Helper role, a defined permission scope for subset test machines, and a concrete list of supported recovery actions.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100