chore(build): Update snap packaging to use prebuilt binaries
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8.7k
- Forks
- 1.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 253
Description
Problem Statement
We want to use identical binaries across all the packaging systems, reusing same hashes, etc. We can update snapcraft.yaml to use prebuilt binaries built by earlier stages of the pipeline.
Proposed Design
We can update the snapcraft.yaml to use the dump plugin to assemble the file system of the snap from binaries that exist in the target/ directory. The CI pipeline can then reuse binaries built by earlier jobs and transfer them, as artifacts, into the job that calls snapcraft pack
Alternatives Considered
Making identical builds (reproducible builds) is possible but would not avoid cost of building on every merge.
Agent Investigation
No response
Checklist
- I've reviewed existing issues and the architecture docs
- This is a design proposal, not a "please build this" request
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 snapcraft.yaml and inspect how the current snap is assembled, then trace the CI pipeline stages that produce target/ and the job that runs snapcraft pack. Update the packaging flow so those earlier-built binaries are transferred as artifacts and used to assemble the snap; done means the snap uses the prebuilt binaries and preserves their hashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100