← Back to issue list

Support build plans

View original Github issue

Metadata

Project
craft-application
Number
#60
Type
issue
State
closed
Author
tigarmo
Labels
—
Created
Updated
Closed

Current evaluation

Build-plan support was merged in canonical/craft-application PR #70 via commit 082e6211, enabling multi-artefact builds and provider instances.

Resolution: closed resolved

Reason: PR #70 added an application-defined build-plan resolver and explicitly closed issue #60. It was merged into main as commit 082e6211.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### What needs to get done Every existing application has some version of support for multiple builds based on a "build matrix". This matrix needs craft-application support because it ends up informing the entire rest of the process. For example: - The build base might depend of the current build configuration; - The instances created by craft-providers need the current build configuration (specially in their names); - The parts lifecycle need the current build config to inform the target/build-for variables and such. ### Why it needs to get done For feature-parity with the existing applications.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Build-plan support was merged in canonical/craft-application PR #70 via commit 082e6211, enabling multi-artefact builds and provider instances.
stealth/space-bunny-alpha — closed resolved Build-plan support landed via PR #70, commit 082e6211, enabling multi-artefact builds and multiple provider instances.
stealth/space-bunny-alpha — closed superseded Build-plan support was split into #67, then delivered by PR #70 in commit 082e6211.
qwen/qwen3.6-35b-a3b — — Superseded by #67. The request to implement build plan support for multi-build matrices in craft-application was tracked separately to handle configuration for bases, providers, and lifecycle variables.
qwen/qwen3.6-35b-a3b — — Superseded by #67. The request for build matrix support in craft-application was closed after the maintainer created a dedicated ticket to handle multiple build configurations and ensure feature parity.

Update history

No update history recorded yet.

Related work

Related issues

Issue Project State Summary Similarity
#70 feat(application): enable build plans craft-application merged PR #70 by cmatsuoka merged to main as commit 082e6211, adding the application-defined build plan resolver to enable multi-artefact builds and creating multiple provider instances; closes issue #60.
76%
#83 Support "platforms" for the build plans craft-application closed Platform support for build plans was merged in craft-application#86 (commit e494797a), adding platform-name selection/filtering and closing #83.
72%