Use craft-platforms for build plans
Metadata
Current evaluation
Closed and synced to Jira as CRAFT-3322. No repository changes or merges were applied. The task remains deferred pending resolution of craft-platforms issue #5.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Once https://github.com/canonical/craft-platforms/issues/5 is completed, snapcraft should use craft-platforms to create a build plan
### Why it needs to get done
* To deduplicate similar build planning logic
* To ensure consistent build plans between snapcraft and potential consumers of craft-platforms, like Launchpad
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed and synced to Jira as CRAFT-3322. No repository changes or merges were applied. The task remains deferred pending resolution of craft-platforms issue #5. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The request to use craft-platforms for build plans was deferred pending a prerequisite issue. No code changes or merges were executed, indicating the task was abandoned or superseded. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The integration of craft-platforms for build plans was abandoned or superseded. Tracking was moved to internal Jira ticket CRAFT-3322. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The task was likely superseded or abandoned pending resolution of the upstream craft-platforms dependency. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The task depends on an upstream craft-platforms update and was synced to Jira (CRAFT-3322) but never resolved or merged. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #600 Use platform for build environment names | craft-application | closed | Closed without implementation. Automated Jira syncs indicate tracking moved internally to CRAFT-3859 and CRAFT-3858. No public fix, merge, or resolution was documented, suggesting the request was abandoned or handled offline. | |
| #1876 Use craft-platforms for build plans | charmcraft | closed | Closed without resolution. The proposal to use craft-platforms for build plans to deduplicate logic and ensure consistency was not implemented or superseded. | |
| #698 Use craft-platforms for build plans | rockcraft | closed | Closed and superseded by prototype PR #662, which implements craft-platforms for build plans to deduplicate logic and ensure consistency across projects. No explicit resolution or merge details are documented. | |
| #391 Use craft-platforms for build plans | craft-application | closed | Build planner logic and filterer were upstreamed to craft-platforms via PR #25. Downstream integration is being prototyped in craft-application. The issue is closed as resolved. | |
| #501 feat: use craft-platforms build planning | craft-application | closed | Closed without merging. The author closed the pull request following a team discussion, noting that the build planning feature will be handled separately. | |
| #4993 Use craft-platforms utilities | snapcraft | closed | Closed and abandoned. The issue requested replacing local architecture utilities with craft-platforms to reduce duplication. No pull request was submitted, and the task was left unresolved after an internal Jira ticket was created. | |
| #403 [PROTOTYPE] refactor: use craft-platforms | craft-application | closed | Closed as a prototype. The author abandoned the pull request, noting that the craft-platforms build planner integration is tracked and implemented via issue #391. | |
| #639 Move the build planner logic into craft-platforms | rockcraft | open | Refactor to move build planner logic into craft-platforms, requested by jugmac00. Work completed: craft-application#391 closed as resolved, rockcraft PR #715 and commit 5f898b32 implemented the change. No BuildPlanner class remains in codebase. |