workflow: cache the spinel build (~6min/run today)
Open
Beginner friendly
Nobody has claimed this yet.
transport
- Dominant language
- Ruby
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
the live #5 run took ~6 minutes, almost entirely spent in make deps && make
building spinel from source on the runner. every request rebuilds it.
options
- actions/cache keyed on SPINEL_REF → cache
/tmp/spinel(the built
binaries). first run builds, rest restore in seconds. - prebuilt artifact: build spinel once in a separate workflow, publish the
binaries as a release asset / container, pull them here. - a prebuilt action: wrap "install spinel @ ref" as a composite action.
simplest first step: actions/cache on /tmp/spinel keyed by SPINEL_REF.
depends on the pin (already in place, SPINEL_REF=f7602f4).
Contributor guide
No contributing guide indexed for this repository
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 GitHub Actions workflow that runs the live #5 request and inspect the existing make deps && make step and SPINEL_REF pin. Add caching for /tmp/spinel keyed by SPINEL_REF, then verify that the first run builds spinel and a repeated run restores the binaries without rebuilding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100