← Back to issue list

Remote build: allow the user to specify a charmcraft channel and default to the charmcraft snap channel

View original Github issue

Metadata

Project
charmcraft
Number
#1706
Type
issue
State
open
Author
lengau
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action: keep open

Reason: The remote-build command in charmcraft/application/commands/remote.py still only exposes --recover, --launchpad-accept-public-upload, and --launchpad-timeout — no channel option — so the request is unimplemented. A maintainer (jugmac00) actively followed it in June 2024, noting the Launchpad team will only announce Charmcraft 3 remote-build support once this works, and it was synced to internal ticket CRAFT-3132, so it remains a tracked, relevant gap rather than stale.

Impact: 50 Quick Win: 22.5 Staleness: 65 Complexity: 55 Confidence: 75 Support Request: 10

Issue body

### What needs to get done Currently Charmcraft has no way to select its own snap channel for remote builds. 1. Allow the user to choose the charmcraft channel by command line 2. If none is specified and charmcraft is installed via snap, use the snap's tracking channel. ### Why it needs to get done Users doing remote builds want to be able to select charmcraft 2 or 3 cc @jugmac00

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 50
Quick Win: 22.5
Staleness: 65
Complexity: 55
Confidence: 75
Support Request: 10
keep 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.
qwen/qwen3.6-35b-a3b
Staleness: 78
Complexity: 35
Confidence: 82
Support Request: 5
keep open Feature request to allow specifying a charmcraft channel for remote builds, defaulting to the snap channel. Open, unlabelled, last active over a year ago, tied to external Charmcraft 3 support announcement.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 50
Confidence: 80
Support Request: 10
needs triage Allows specifying a charmcraft snap channel for remote builds, defaulting to the installed snap channel. Open for ~2 years with no labels, assignee, or implementation progress.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 20
Confidence: 70
Support Request: 10
needs triage Feature request to allow specifying a charmcraft channel for remote builds, defaulting to the snap channel. Currently open, awaiting upstream/external team dependency for Charmcraft 3 support.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 40
Confidence: 85
Support Request: 10
needs triage Allow specifying a charmcraft channel via CLI for remote builds, defaulting to the snap channel. Open and pending implementation. Awaiting Launchpad team to enable Charmcraft 3 remote build support. Last updated 304 days ago.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft#6384 (confidence 80%)

    Same feature for snapcraft's remote-build (set snapcraft's channel in the build recipe), still open and awaiting implementation — a parallel request in the sibling project.

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.
77%
#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.
75%
#344 remote build: provide a way to set application snap channel craft-application 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.
74%
#3600 remote build: use channel defaults (CRAFT-568) snapcraft merged Merged changes remove hardcoded channel forcing for snapcraft and core18 in remote builds, aligning with snapcraft's core20 transition. Approved and merged with a minimal diff. Launchpad now auto-selects the correct build-base.
71%