Use legacy remote builder for core20 snaps
Metadata
Current evaluation
Superseded and closed pending dependency #4885. The legacy remote builder fallback for core20 snaps was deferred, with tracking moved to internal ticket CRAFT-3071.
Suggested action: —
No scores available.
Issue body
### What needs to get done
If the base is `core20`, then use the legacy remote builder.
### Why it needs to get done
Core20 snaps cannot be built with the new remote builder because it fails to parse the `architectures` keyword with `run-on`. This requires #4885 to be completed first. In the meantime, snapcraft will use the remote builder.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Superseded and closed pending dependency #4885. The legacy remote builder fallback for core20 snaps was deferred, with tracking moved to internal ticket CRAFT-3071. | |
| qwen/qwen3.6-35b-a3b | — | — | Legacy remote builder support for core20 snaps was closed without implementation. The change was abandoned pending referenced issue #4885, with no fix or further activity provided since closure. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. Deferred pending issue #4885. An internal Jira ticket (CRAFT-3071) tracks using the legacy remote builder for core20 snaps, as the new builder fails to parse the architectures keyword. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The fix depends on #4885, leaving the issue superseded or abandoned pending upstream resolution. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as superseded after PR #4885 resolved the architecture parsing failure. The legacy remote builder fallback for core20 snaps was implemented, with tracking moved to internal Jira ticket CRAFT-3071. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4895 fix(remotebuild): require core20 snaps to use the legacy remote builder | snapcraft | merged | Merged. Requires core20 snaps to use the legacy remote builder since the new builder cannot parse core20 snapcraft.yaml files. Resolves #4886. Approved and passed CI. | |
| #4144 remote build: legacy builder cannot parse core22 snapcraft.yaml syntax | snapcraft | closed | Won't fix. The legacy remote builder lacks core22 syntax support and was descoped in favor of the new remote builder. The legacy builder will be removed in Snapcraft 9, making this enhancement unnecessary. | |
| #5427 Add a deprecation notice for building core22 snaps with the legacy remote builder | snapcraft | closed | Closed without implementation. The requested deprecation warning for the legacy remote builder with core22 snaps was not added, and the issue appears abandoned. | |
| #5676 remote build: remove legacy remote builder | snapcraft | closed | Superseded by a merged pull request that removed the legacy remote builder and related configuration, completing the deprecation cleanup for Snapcraft 9. | |
| #4365 remote-build: legacy builder complains about the wrong part name | snapcraft | closed | Marked won't fix. The legacy remote builder causing misleading validation errors for core22 snaps will be removed in Snapcraft 9, rendering the issue obsolete. No code changes were implemented. | |
| #4710 Remove core22 remote-builder in favour of craft-application remote-builder | snapcraft | closed | Closed without a linked resolution or merge. The migration of the core22 remote-builder to craft-application appears abandoned or completed via an unlinked pull request, as no resolution details are documented. | |
| #4498 fix(remote): fallback to legacy snapcraft if under shallow git clone | snapcraft | merged | Merged a fix falling back to legacy remote builds for shallow git clones, which cannot be pushed by design. Supports only core20 and core22 bases. Approved by two reviewers, passed CI, and modified 8 files. |