← Back to issue list

remote-build should be asynchronous by default

View original Github issue

Metadata

Project
craft-application
Number
#1105
Type
issue
State
open
Author
steinbro
Labels
—
Created
Updated
Closed
—

Current evaluation

Maintainer proposal to make remote-build non-blocking: exit after submitting the job, print a status URL and follow-up command, with an opt-in --detach/--bg flag. Discussed and converging, not implemented.

Suggested action: keep open

Reason: Author is a maintainer and the thread has substantive discussion with jnsgruk agreeing the change is reasonable if opt-in ('this should be explicit with --bg or --detach'), but no implementation is referenced and the flag name remains unsettled across three proposals (steinbro's --wait, mr-cal's --detach, jnsgruk's --bg/--detach), so it is triaged and valid but not turnkey. Code inspection was blocked (no pinned SHA available for craft-application), so I could not verify whether any flag already exists — the only signal was a single '--wait' hit in the repo, which I could not read; that ambiguity plus the unresolved default-vs-opt-in semantics drives the moderate actionability and sub-70 confidence.

Evaluated by: mr-cal-bot

Impact: 40 Quick Win: 12 Complexity: 45 Confidence: 68 Actionability: 55

Issue body

### What needs to get done Given the queue length and speed for some architectures, remote-build should exit immediately after uploading and submitting the job. The user should be presented with a URL to open to check the build status, and the followup command to execute to fetch the result. A new argument like `--wait` could be used if the user wants the current behavior. ### Why it needs to get done A blocking command is reasonable for actions that are expected to take seconds or minutes, not hours or days.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 40
Quick Win: 12
Complexity: 45
Confidence: 68
Actionability: 55
keep open Maintainer proposal to make remote-build non-blocking: exit after submitting the job, print a status URL and follow-up command, with an opt-in --detach/--bg flag. Discussed and converging, not implemented.
stealth/space-bunny-alpha
Impact: 45
Quick Win: 10
Complexity: 55
Confidence: 65
Actionability: 50
keep open Wants remote-build to stop blocking on queued cross-arch builds; maintainers converging on opt-in --detach/--bg plus clearer --resume messaging. Valid, still open and mid-UX-design.
stealth/space-bunny-alpha
Impact: 47
Quick Win: 15
Complexity: 49
Confidence: 91
Actionability: 64
keep open remote-build remains blocking for queued cross-architecture builds; maintainers are weighing opt-in --detach/--bg behavior or clearer --resume guidance for hours-long riscv64 builds.
qwen3.6-35b-a3b-mtp-q6
Impact: 55
Quick Win: 19
Staleness: 45
Complexity: 65
Confidence: 75
Support Request: 0
needs triage Feature request to add --detach/--bg flag for asynchronous remote-build. Discussed among maintainers but not yet implemented.
qwen/qwen3.6-35b-a3b
Staleness: 15
Complexity: 45
Confidence: 85
Support Request: 10
keep open Feature request to make remote-build asynchronous by default for interactive UX. Maintainers propose an opt-in flag instead. Actively discussed but lacks labels or assignee.
qwen3.6-35b-a3b-mtp-q6
Staleness: 10
Complexity: 65
Confidence: 85
Support Request: 5
needs triage Feature request to make remote-build asynchronous by default, with a URL for status checking and a followup command. Currently under discussion among maintainers regarding implementation details (default vs. opt-in flag).

Update history

No update history recorded yet.

Related work

  • Related To: craft-application#1101 (confidence 55%)

    Also an open maintainer-filed issue about remote-build's blocking status indicator harming interactive use, and jnsgruk's resilience/retry concerns in this thread concern the same command flow.

Related issues

No related issues found above the similarity threshold.