remote-build always recovers, even when --recover is not specified

Metadata

Project: snapcraft (launchpad)
Number: #1913599
Type: issue
State: open
Author: ~nymea
Labels: —
Created: 2021-01-28 02:24 PM UTC
Updated: 2021-02-25 01:26 PM UTC
Closed: —

Current evaluation

Snapcraft remote-build recovers a previous build even without --recover, breaking automated builds. Open ~5.5 years with zero comments, no labels, and no maintainer engagement; the remote-build command has since been removed from snapcraft.

Suggested action: close stale

Reason: The issue has had zero comments, no labels, and no maintainer response for ~5.5 years (last activity 2013 days ago), and the remote-build command it targets was deprecated in snapcraft 7.x and removed in 8.0, so the reported behavior can no longer occur. Confidence is moderate because repo inspection tools were unavailable (no pinned SHA), so the removal of remote-build rests on background knowledge rather than verified code.

Impact: 30 Quick Win: 19.5 Staleness: 92 Complexity: 35 Confidence: 55 Support Request: 10

Issue body

To reproduce, start a remote-build, and make the client fail somehow. Wait for the remote build to finish or fail (doesn't matter). Then start another remote-build with a different revision of the source code *without* specifying --recover. => snapcraft will recover the previous build and report the status instead of actually building the new source. Given that snapcraft clean doesn't seem to clean remote builds, this makes it close to impossible to use snapcraft remote-build in some sort of automated build environment as one never knows what the build artifact is actually based on.

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 07:00 AM UTC	qwen/qwen3.8-27b	Impact: 30 Quick Win: 19.5 Staleness: 92 Complexity: 35 Confidence: 55 Support Request: 10	close stale	Snapcraft remote-build recovers a previous build even without --recover, breaking automated builds. Open ~5.5 years with zero comments, no labels, and no maintainer engagement; the remote-build command has since been removed from snapcraft.
2026-07-23 11:42 AM UTC	qwen/qwen3.6-35b-a3b	Staleness: 95 Complexity: 35 Confidence: 85 Support Request: 5	close stale	Remote-build recovers previous builds without --recover flag, breaking automated workflows. Issue is 5+ years old, has no comments or labels, and shows no maintainer engagement.
2026-07-22 01:26 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 95 Complexity: 40 Confidence: 75 Support Request: 5	needs triage	snapcraft remote-build recovers previous state without --recover flag, causing automated builds to use stale source. Unlabelled, zero comments, no maintainer interaction in over 5 years.
2026-07-09 03:48 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 95 Complexity: 40 Confidence: 85 Support Request: 10	close stale	snapcraft remote-build automatically recovers previous build state without --recover, breaking automated builds. Unlabelled, zero comments, inactive for over 5 years.
2026-06-20 09:21 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 95 Complexity: 30 Confidence: 60 Support Request: 10	close stale	snapcraft remote-build incorrectly recovers previous builds without --recover, breaking automated workflows. Issue is open, unassigned, untriaged, and has no comments.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.