ci(bazel): evaluate shared Java prebuild
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Description
Evaluate a merge-queue Java prebuild that warms the remote cache before service test fan-out. It should reduce duplicate NV Boot compilation without increasing wall time.
Definition of Done
- Compare current and prebuild runs for an NV Boot change.
- Record wall time, Bazel actions or cache-hit rate, and runner minutes.
- Adopt it only if it reduces wall time and duplicate work. Otherwise retain the current fan-out.
Resources (optional)
.github/workflows/bazel.yml
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 .github/workflows/bazel.yml and compare the current fan-out with a merge-queue Java prebuild for an NV Boot change. Record wall time, Bazel actions or cache-hit rate, and runner minutes for both runs. Done means adopting the prebuild only if it reduces wall time and duplicate work; otherwise retain the current fan-out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100