Can’t dry-run a build to check snapcraft.yaml
Metadata
Current evaluation
Requests a build-free snapcraft.yaml validation mode; the reporter narrowed the initial goal to schema validation, but no dedicated dry-run command or resolving change is evident.
Suggested action: keep open
Reason: Evan explicitly narrowed the request to “just validating the schema to start,” making this a valid, scoped feature, although the report is based on hearsay and lacks a reproducer. The current tree contains snapcraft.yaml parsing and schema files, but the discovered `snapcraft lint` command requires an existing `.snap`; no implementation or resolving commit is evidenced.
Evaluated by: mr-cal-bot
Impact:
38
Quick Win:
13
Complexity:
48
Confidence:
78
Actionability:
68
Issue body
Apologies for the incomplete bug report: this is based purely on what I’ve been told.
Evan says that currently, it is not possible to do a “dry run” build that does everything involving the snapcraft.yaml but does not perform the actual build.
It might save time to fix bug 1666160 at the same time as this bug.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
13
Complexity:
48
Confidence:
78
Actionability:
68
|
keep open | Requests a build-free snapcraft.yaml validation mode; the reporter narrowed the initial goal to schema validation, but no dedicated dry-run command or resolving change is evident. | |
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
12
Complexity:
42
Confidence:
88
Actionability:
55
|
keep open | Requests a build dry run that validates snapcraft.yaml without building; scope was narrowed to schema validation, but no implementation or resolution is evident. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
3
Complexity:
50
Confidence:
50
Actionability:
20
|
needs triage | Feature request to add a "dry run" mode for snapcraft builds to validate snapcraft.yaml without performing the actual build. Issue is vague, incomplete, and has no maintainer assessment after 3502 days. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
19
Staleness:
100
Complexity:
25
Confidence:
65
Support Request:
15
|
close stale | Feature request (9.5 years old, no maintainer activity) for a dry-run build that validates snapcraft.yaml without performing the build. The core capability now exists via the snapcraft validate command, so the request is largely obsolete. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Feature request for a dry-run mode to validate snapcraft.yaml without performing the actual build. Untriaged, inactive for over 9 years, lacks details. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
60
Confidence:
75
Support Request:
10
|
close stale | Feature request to add a dry-run mode for snapcraft builds to validate snapcraft.yaml without executing the actual build. Untriaged, inactive for over 9 years, with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Request to implement a dry-run mode for snapcraft builds to validate snapcraft.yaml without executing the full build. Untriaged, inactive for over 9 years, lacks details. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1666160
(confidence 90%)
The issue body explicitly suggests fixing bug 1666160 at the same time.
Related issues
No related issues found above the similarity threshold.