← Back to issue list

remote-build: add support for `--build-for`

View original Github issue

Metadata

Project
charmcraft
Number
#2467
Type
issue
State
open
Author
sed-i
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to add --build-for flag to charmcraft remote-build for building a subset of architectures, mirroring snapcraft. No maintainer response or labels in 319 days; remote-build still lacks the flag in current code.

Suggested action: needs triage

Reason: The issue has no labels, no comments, and no maintainer interaction in 319 days. The remote-build command in charmcraft/application/commands/remote.py still only accepts --recover, --launchpad-accept-public-upload, and --launchpad-timeout — no --build-for. The underlying craft-application framework does support build_for in its lifecycle commands (craft_application/commands/lifecycle.py), so the feature is feasible but requires wiring through the remote build service. This is a legitimate feature request that needs maintainer assessment.

Impact: 45 Quick Win: 27.0 Staleness: 75 Complexity: 40 Confidence: 70 Support Request: 10

Issue body

### What needs to get done Like snapcraft, charmcraft should support the `--build-for` arg for remote build. ``` > charmcraft remote-build --build-for=s390x --launchpad-accept-public-upload Usage: charmcraft [options] command [args]... Try 'charmcraft remote-build -h' for help. Error: unrecognized arguments: --build-for=s390x ``` ### Why it needs to get done For testing a subset of charms, it would be handy if we didn't need to wait for all of them to be built remotely. The amd64 and arm64 remotes are often busy, and github has amd64 and arm64 runners. Building remotely can take an hour, vs. locally ~5 min.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 45
Quick Win: 27.0
Staleness: 75
Complexity: 40
Confidence: 70
Support Request: 10
needs triage Feature request to add --build-for flag to charmcraft remote-build for building a subset of architectures, mirroring snapcraft. No maintainer response or labels in 319 days; remote-build still lacks the flag in current code.
qwen/qwen3.6-35b-a3b
Staleness: 75
Complexity: 40
Confidence: 85
Support Request: 10
needs triage Feature request to add --build-for argument to charmcraft remote-build for targeting specific architectures. Unlabelled, no maintainer response, inactive for ~9 months.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 40
Confidence: 85
Support Request: 10
needs triage Feature request to add --build-for argument to charmcraft remote-build for targeting specific architectures. Currently unlabelled and inactive for 264 days with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 80
Complexity: 45
Confidence: 80
Support Request: 10
needs triage Feature request to add --build-for argument to charmcraft remote-build for multi-architecture builds. Unlabelled, no maintainer response, open for ~8.5 months.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 45
Confidence: 65
Support Request: 10
needs triage Implement --build-for flag for charmcraft remote-build to target specific architectures. Open 242 days with no comments. Needs triage and assignment to move forward.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#5435 remote build: deprecate `--build-for` snapcraft open Deprecate --build-for in snapcraft remote-build to align with Craft Application and other craft tools. Triaged by maintainer who confirmed it can ship in a minor release, but blocked by Launchpad's new build farm migration for --platform support. Code confirms --build-for is still active without deprecation warning.
70%