← Back to issue list

[PROTOTYPE] refactor: use craft-platforms

View original Github issue

Metadata

Project
craft-application
Number
#403
Type
pull request
State
closed
Author
mr-cal
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action:

No scores available.

Issue body

- [x] Have you followed the guidelines for contributing? - [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [x] Have you successfully run `tox`? ----- This prototype ensures that the `craft-platforms` build planner is a drop-in replacement for the default build planner. This is a prototype because it has some hacks, linting errors, and lacks support for `build-for: [all]`. Downstream prototype: https://github.com/canonical/rockcraft/pull/662 Upstream build planner: https://github.com/canonical/craft-platforms/pull/25 (CRAFT-3154)

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b 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.
qwen3.6-35b-a3b-mtp-q6 Closed as a prototype. The craft-platforms build planner refactor was abandoned and superseded by tracking issue #391, which will handle landing the changes.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#662 [PROTOTYPE] refactor: use craft-platforms rockcraft closed Closed as a prototype pending upstream completion of craft-application#391. The branch remains available for future use once those changes are released.
88%
#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.
78%
#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.
76%
#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.
74%
#986 [PROTOTYPE] build(deps): use craft-parts branch rockcraft closed Abandoned as a prototype PR to test CI with a craft-parts branch. Explicitly marked DO NOT MERGE and closed without integration. No changes were merged.
74%
#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.
73%
#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.
73%
#1894 refactor: use craft-platforms for build plans charmcraft merged Merged a refactor replacing custom build plan logic with craft-platforms for platforms charms. Approved by two reviewers, the change modifies two files with a net reduction of eight lines, streamlining platform handling.
71%
#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.
71%
#5015 Use craft-platforms for build plans snapcraft closed 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.
70%