← Back to issue list

Provide a unified way to get the current build's BuildInfo

View original Github issue

Metadata

Project
craft-application
Number
#297
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to add a unified accessor for the current build's BuildInfo, validating the plan has exactly one entry. Implemented via AppService._build_info in PR #911, which raises EmptyBuildPlanError or MultipleBuildsError as requested.

Suggested action: close stale

Reason: The requested functionality is already implemented: AppService._build_info (craft_application/services/base.py) returns the single BuildInfo and raises EmptyBuildPlanError/MultipleBuildsError for empty or multi-entry plans, matching the issue's requirements. This was added in commit 89382915 (PR #911, 'feat(AppService): add convenience properties for frequently-accessed items'), so the issue is no longer applicable.

Impact: 35 Quick Win: 24.5 Staleness: 85 Complexity: 30 Confidence: 80 Support Request: 0

Issue body

### What needs to get done This should also validate that the provided build plan contains exactly one BuildInfo object. See: [discussion here](https://github.com/canonical/rockcraft/pull/521#discussion_r1550351690) ### Why it needs to get done Multi-build build plans are generally used for determining which providers to run. Once we're actually doing the build, we only need a single BuildInfo object.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 24.5
Staleness: 85
Complexity: 30
Confidence: 80
Support Request: 0
close stale Feature request to add a unified accessor for the current build's BuildInfo, validating the plan has exactly one entry. Implemented via AppService._build_info in PR #911, which raises EmptyBuildPlanError or MultipleBuildsError as requested.
qwen/qwen3.6-35b-a3b
Staleness: 90
Complexity: 40
Confidence: 75
Support Request: 10
close stale Feature request to unify BuildInfo retrieval and validate single-object build plans. Unlabelled, inactive for over a year with only an automated Jira sync comment, awaiting maintainer assessment or closure.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 45
Confidence: 85
Support Request: 10
needs triage Feature request to unify access to the current build's BuildInfo object and validate build plans. Unlabelled, no maintainer response, inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 30
Confidence: 75
Support Request: 5
close stale Implement a unified method to retrieve the current build's BuildInfo, ensuring the build plan contains exactly one instance. Inactive for over a year with an internal Jira ticket created. Awaiting implementation or triage.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: craft-application#911 (confidence 85%)

    PR #911 added the _build_info convenience property to AppService, which validates the build plan contains exactly one BuildInfo object as requested in this issue.

Related issues

No related issues found above the similarity threshold.