oxidecomputer / oxidecomputer/omicron
Want Omicron buildomat job to track incremental build time
Open
Nobody has claimed this yet.
development
Metrics
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
From 1/18 dev sync meeting:
- For developers, we care significantly about "rebuild time after modifying one file"
- We'd like to track this over time to mitigate regressions
- Highest priority targets would probably be nexus, possibly sled agent
- We could add a (non-blocking) buildomat job, to effectively (after a full build) "touch one file, do a re-build, emit how long that took"
To complete this issue, we should have some way (via emitted artifact, or stored "timing" information somewhere) that gives this info for one or two high-priority crates within Omicron.
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 by locating the repository's existing Buildomat jobs and the build commands for nexus and sled agent. Define a non-blocking job that performs a full build, touches one file, rebuilds, and emits timing data as an artifact or stored record; done means timings are available over time for one or two priority crates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100