Update `gn` for V8 15.4
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 542
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
via @miladfarca for the V8 CI for Linux on ppc64le and s390x we'll need to update gn on the machines to include https://gn.googlesource.com/gn/+/c7ffaf80713afbe5a4f4d95a605c0a98084374de as V8 has started to require it starting from https://chromium-review.googlesource.com/c/v8/v8/+/8299913.
This will involve rolling the sha in https://github.com/nodejs/build/blob/7f9c831a38334b7fdebbbcbb819930ec3ae48226/ansible/roles/gn/vars/main.yml#L8 forwards and then redeploying the updated playbook across the Linux ppc64le and s390x machines used to run the V8 CI.
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 ansible/roles/gn/vars/main.yml at the referenced SHA and inspect the playbook used to deploy the GN update. Confirm the target Linux ppc64le and s390x machines used by V8 CI, then redeploy the updated playbook. Done means those machines use the referenced GN revision and V8 CI can require it successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- build-system, ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100