remote build: document nuances of current and legacy remote builders
Metadata
Current evaluation
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.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Update the [Architectures object](https://github.com/canonical/snapcraft/blob/67de4083f7b56afd899c3d43c4fe0acaa7bd4c95/snapcraft/models/project.py#L481) and [this converter](https://github.com/canonical/snapcraft/blob/67de4083f7b56afd899c3d43c4fe0acaa7bd4c95/snapcraft/models/project.py#L538) to handle `run-on` for `core20` bases
After a team discussion on 2024-Jun-21 and a discussion with @lengau on 2024-Jun-26, the complexity of this task has increased and we've divided it into 3 separate problems:
1. Document the behavior and nuances of the legacy and new remote builders.
2. Do not parse the `architectures` or `platform` keywords if `--build-for` or `--platform` is provided
3. Create `Architecture` and `Project` models per-base and union type the models.
### Why it needs to get done
`core20` snaps cannot use the new remote-builder because `architectures: run-on:` is not in the Project model.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The scope was split into three tasks, but no pull requests were merged or code implemented. An internal Jira ticket was created, and the issue appears abandoned or superseded. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and superseded. Scope expansion split the task into three separate tracking items. Work was deferred to internal Jira ticket CRAFT-3000. No code changes or merges were implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and deferred to internal tracking ticket CRAFT-3000. The scope was split into three tasks, prioritizing documentation. No code changes or pull requests were merged. Implementation remains pending. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. Scope was split into three sub-tasks and tracked internally via Jira ticket CRAFT-3000. No code changes or documentation were merged, indicating the issue was deferred pending further planning. |
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. | |
| #766 Prototype the `remote-build` command/support | rockcraft | closed | Closed without implementation. The request to prototype the rockcraft remote-build command was migrated to internal Jira tracking (CRAFT-3748) and abandoned on GitHub. No code changes or pull requests were submitted. | |
| #4324 remote-build: new command logic | snapcraft | closed | The remote-build command logic update was closed without implementation. No linked pull request or resolution details exist, indicating the feature was abandoned. | |
| #4710 Remove core22 remote-builder in favour of craft-application remote-builder | snapcraft | closed | 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. | |
| #246 Use a more repeatable identity for remote builds | craft-application | closed | Closed without resolution. Superseded by internal Jira ticket CRAFT-2556. No public fix or implementation was merged. |