← Back to issue list

Clean Launchpad repositories when remote-build errors are raised

View original Github issue

Metadata

Project
snapcraft
Number
#4481
Type
issue
State
closed
Author
dilyn-corner
Labels
—
Created
Updated
Closed

Current evaluation

Launchpad cleanup for remote-build errors was implemented in commit 663dcdfab; the author confirmed the request was completed.

Resolution: closed resolved

Reason: Commit 663dcdfab implemented cleanup after remote-build errors. The author later confirmed the request had been completed before the issue was closed.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### What needs to get done Currently, if a `remote-build` fails due to some error, the repository will be left on Launchpad. A specific error where this happens is when an HTTP 500 error occurs (see #4478 for a reproducible case). A specific error where this *does not* happen is when the snap fails to build for some reason (a legitimate *build failure*). In these instances, the repository **is** deleted in Launchpad. I would suggest that either * the behavior is switched (when a non-build issue is encountered, delete the repository; when a build issue is encountered, leave the repository), OR * that the behavior is mirrored -- the repository is deleted from Launchpad in all instances where a failure occurs. ### Why it needs to get done It is probably unlikely to be useful to have an ever-growing collection of repositories on Launchpad accounts, especially repositories which users probably don't actually care about *except* insofar as it allows them to get a snap package back from Launchpad.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Launchpad cleanup for remote-build errors was implemented in commit 663dcdfab; the author confirmed the request was completed.
stealth/space-bunny-alpha — closed resolved Launchpad cleanup for remote-build errors was implemented in commit 663dcdfab; the author confirmed the request had been addressed.
qwen/qwen3.6-35b-a3b — — Fixed. Launchpad repositories are now automatically deleted when remote-build errors occur, preventing accumulation of unused repositories. The author confirmed the implementation.
qwen/qwen3.6-35b-a3b — — Implemented cleanup of Launchpad repositories following remote-build errors. The author confirmed the fix, which now automatically deletes repositories on all failure types, preventing unnecessary account clutter.
qwen/qwen3.6-35b-a3b — — Cleanup of Launchpad repositories after remote-build errors was implemented. The author confirmed the request was fulfilled, and the system now deletes repositories on all failure types. Resolved as fixed and closed.
qwen3.6-35b-a3b-mtp-q6 — — Requested cleanup of Launchpad repositories following remote-build errors has been implemented. The author confirmed the fix is in place, ensuring repositories are deleted on all failure types.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/snapcraft@663dcdfab (confidence 98%)

    Repository metadata identifies this commit as implementing the requested Launchpad cleanup.

Related issues

Issue Project State Summary Similarity
#224 fix(remotebuild): create the launchpad instance correctly craft-application merged Merged PR #224 as commit 87bc56a7, fixing remotebuild to create the Launchpad instance correctly.
77%
#1205 remote build: stale git repositories on launchpad craft-application open New, unlabelled report documents several remote-build paths orphaning about 20,000 Launchpad git repositories and proposes a best-effort, bounded cleanup sweep; no maintainer response yet.
74%
#1206 Issue 1205 remote clean build stale repos craft-application open Adds best-effort cleanup of stale Launchpad git repositories during remote builds; under review, CI title check failing and tests pending.
74%
#2642 remote-build: detect early build errors snapcraft merged Merged PR #2642 by cjp256: remote-build now detects early Launchpad build errors (e.g. missing snapcraft.yaml) instead of misreporting a busy builder; landed as commit 73fd95e86.
73%
#249 remote build: provide a way to clean up all of a user's remote builds craft-application open Triaged enhancement remains open: add a command to remove stopped, app-prefixed builds left in the user's Launchpad remote-build project after crashes.
73%
#2825 remote-build: remove need to specify user snapcraft merged Merged #2825, removing the remote-build user requirement and adding automatic Launchpad login; it also fixed public-upload handling and cleaned up LaunchpadClient.
73%
#3021 remote-build: remove artifact sanity check snapcraft merged Merged PR #3021 (commit e4a878561) removed remote-build's artifact arch sanity check, so Launchpad results with arch 'multi' from build-on are downloaded instead of rejected. Fixes LP bug #1870730.
72%
#2633 remote-build: increase number of launchpad start_build request attempts snapcraft closed Closed unmerged: more start_build retries were abandoned after the author traced repeated failures to an uncaught Launchpad backend error that the change would not address.
70%
#4460 fix: push tags for remote-build snapcraft merged Merged PR #4460 in commit 21f6ad788, fixing remote-build to push Git tags to Launchpad for version discovery.
70%
#384 fix(remotebuild): push git tags to launchpad craft-application merged Merged #384 as commit dd5bccd3, enabling remote builds to push Git tags to Launchpad so applications can derive versions from those tags.
70%