Skip to content

chore(build): Update snap packaging to use prebuilt binaries #1610

Closed as not planned

Description

@zyga

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

Activity

  1. added
    area:buildRelated to CI/CD and builds
    and removed
    state:triage-neededOpened without agent diagnostics and needs triage
    on May 28, 2026
  2. changed the title [-]Update snap packaging to use prebuilt binaries[/-] [+]chore(build): Update snap packaging to use prebuilt binaries[/+] on Jun 2, 2026
  3. github-actions commented on Jun 17, 2026

    @github-actions

    This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.

  4. eviehoward commented on Aug 20, 2026

    @eviehoward
    Contributor

    Hi @zyga 🙂! from reviewing parent issue CI/CD & Testing Improvements, this is marked as Todo, but IIUC this issue was resolved by #1651... can this be marked as closed&done? (same for issue #1611)

  5. github-actions commented on Sep 12, 2026

    @github-actions

    This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:buildRelated to CI/CD and buildsstate:staleInactive item at risk of automatic closure.

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions