remote build: provide a way to set application snap channel
Metadata
Current evaluation
Enhancement to add an environment variable or option so remote builds can specify which snap channel (e.g. edge) to use for the application snap in Launchpad build recipes. Triaged by maintainer; not yet implemented.
Suggested action: keep open
Reason: The issue is labelled Status: Triaged and Type: Enhancement, and the maintainer (lengau) added a concrete implementation note on 2024-05-13 that remote-build tests should run on the edge channel. The recipe model already has auto_build_channels and channels parameters in craft_application/launchpad/models/recipe.py, so the plumbing partially exists but no user-facing env var/option is wired up. Related open issues snapcraft#6384 and charmcraft#1706 confirm this is still an active, unimplemented need across the craft ecosystem.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
30.0
Staleness:
45
Complexity:
40
Confidence:
70
Support Request:
10
|
keep open | Enhancement to add an environment variable or option so remote builds can specify which snap channel (e.g. edge) to use for the application snap in Launchpad build recipes. Triaged by maintainer; not yet implemented. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
65
Complexity:
15
Confidence:
90
Support Request:
0
|
keep open | Enhancement requesting an environment variable to set the snap channel for remote builds. Triaged and acknowledged by a maintainer, but inactive for over five months with no implementation progress. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
65
Complexity:
20
Confidence:
85
Support Request:
0
|
keep open | Enhancement request to add an environment variable for configuring the snap channel during remote builds, currently triaged and awaiting implementation. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
40
Complexity:
20
Confidence:
85
Support Request:
10
|
keep open | Enhancement to specify the snap channel for remote builds via an environment variable. Triaged and linked to internal Jira ticket CRAFT-2910. Awaiting implementation. Last updated 139 days ago. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft#6384
(confidence 85%)
Same feature request scoped to snapcraft: set snapcraft's channel in the build recipe via env var. Open and triaged.
-
Related To:
charmcraft#1706
(confidence 85%)
Same feature request scoped to charmcraft: allow user to specify charmcraft channel for remote builds. Open since 2023.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #6384 remote-build: set snapcraft's channel in the build recipe | snapcraft | open | Enhancement to set Snapcraft's channel in remote build recipes and expose an environment variable for channel selection. Triaged, from maintainer, 23 days old. | |
| #1706 Remote build: allow the user to specify a charmcraft channel and default to the charmcraft snap channel | charmcraft | open | Feature request to let users select the charmcraft snap channel for remote builds (CLI option) and default to the installed snap's tracking channel. Open since 2023, last activity July 2024; no channel option exists in remote-build yet. | |
| #2933 remote-build: introduce --launchpad-snapcraft-channel option | snapcraft | closed | Closed without merging. Reviewers requested changing the default channel to stable and replacing the CLI flag with an environment variable for developer use. The author agreed to implement the environment variable approach in a new PR. | |
| #2061517 `remote-build` lacks support for selecting Snapcraft channel | snapcraft (launchpad) | open | Feature request to expose Launchpad's snapcraft channel selection API in remote-build, defaulting to the local channel. Untriaged, no maintainer engagement in 871 days. |