Remove core22 remote-builder in favour of craft-application remote-builder
Metadata
Current evaluation
Closed without a linked resolution or merge. The migration of the core22 remote-builder to craft-application appears abandoned or completed via an unlinked pull request, as no resolution details are documented.
Suggested action: —
No scores available.
Issue body
### What needs to get done
1. Ensure the `Dispatcher` exectues new remote-build command regardless of the base (I think this can be done [here](https://github.com/canonical/snapcraft/blob/c3e328853adc5e42ee06110473b6e6e8cc9af66b/snapcraft/application.py#L169)))
2. Migrate `_run_new_or_fallback_remote_build()` from `snapcraft.commands.core22.remote` to `snapcraft.commands.remote`.
- This function contains [this business logic](https://private-user-images.githubusercontent.com/1146853/288046913-c0a1fb19-0561-4810-ba53-73aad8910056.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTIwODk5NjgsIm5iZiI6MTcxMjA4OTY2OCwicGF0aCI6Ii8xMTQ2ODUzLzI4ODA0NjkxMy1jMGExZmIxOS0wNTYxLTQ4MTAtYmE1My03M2FhZDg5MTAwNTYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDQwMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA0MDJUMjAyNzQ4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NjkyNDRkZDQzZDY0YzIzMGMzNGEwNjM2NmQ0NDBhMjVlMjE5YWIwMzhhZGQ5MTViNWUyZTE2OWRiMjViOGEyMSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.T0zToicicdnrE6ST76tRqdS0_amg03Mug_TrU0q7q6w)
3. Remove `snapcraft/commands/core22/remote.py` and `snapcraft.remote/`
### Why it needs to get done
1. Deduplication of code
2. So the new craft-application remote-builder can be used for core20, core22, and core24 snaps.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without a linked resolution or merge. The migration of the core22 remote-builder to craft-application appears abandoned or completed via an unlinked pull request, as no resolution details are documented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The core22 remote-builder was removed and its logic migrated to craft-application, enabling unified remote builds across core20, core22, and core24 bases while eliminating code duplication. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The core22 remote-builder migration to craft-application was resolved internally via CRAFT-2659. No pull request was merged to implement the deduplication or file removal. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and superseded by JIRA ticket CRAFT-2659. The core22 remote-builder migration to craft-application was deferred, with deduplication efforts tracked externally. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without a direct resolution. Internal ticket CRAFT-2659 was created to track the core22 remote-builder migration. No merge or fix was implemented, indicating the task was abandoned or superseded by internal processes. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #300 Remote-build: use craft-application for core22 | craft-application | closed | Migration to craft-application for core22 remote builds was closed without a specified resolution or implementation. No merge or fix was documented. | |
| #4724 feat(remote)!: use craft-application remote build for core22 | snapcraft | merged | Replaced deprecated remote build code with craft-application for core22. Core20 support enabled via environment variable. The --build-on flag was removed. Fixes #4710. Merged after approval and passing CI checks. | |
| #4886 Use legacy remote builder for core20 snaps | snapcraft | closed | Superseded and closed pending dependency #4885. The legacy remote builder fallback for core20 snaps was deferred, with tracking moved to internal ticket CRAFT-3071. | |
| #4842 remote build: document nuances of current and legacy remote builders | snapcraft | closed | Closed without implementation. The scope was split into three sub-tasks, but no changes were made. The issue was superseded by internal Jira ticket CRAFT-3000 and abandoned after over two years. | |
| #4653 feat(craft-application): support remote build | snapcraft | closed | Remote build support for craft-application was closed without merging. The request received no reviews or CI checks and remained inactive for over 800 days, effectively abandoning the feature. |