Check for invalid recipes in remote-builds
Metadata
Current evaluation
Remote builds gained an early error for --build-for with shorthand platforms in merged PR #5351 (0c224fc7d); PR #5687 later removed the restriction.
Resolution: closed resolved
Reason: PR #5351 merged as commit 0c224fc7d and added a clearer early validation error for shorthand platforms with --build-for. The maintainer confirmed the fix in #5270, while PR #5687 later removed the restriction after Launchpad's underlying limitations ended.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Until https://bugs.launchpad.net/launchpad/+bug/2077005 and https://bugs.launchpad.net/launchpad/+bug/2098811 is resolved or Launchpad uses craft-platforms, Snapcraft should check a remote build is requested with:
* the `--build-for` argument AND
* a shorthand platform notation
If so, Snapcraft should error or warn the user.
### Why it needs to get done
To improve the UX - remote builds fail with unhelpful errors.
Source: https://forum.snapcraft.io/t/call-for-testing-snapcraft-8-7-0/45762/7?u=mr_cal
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Remote builds gained an early error for --build-for with shorthand platforms in merged PR #5351 (0c224fc7d); PR #5687 later removed the restriction. | |
| stealth/space-bunny-alpha | — | closed resolved | Closed by mr-cal as fixed in PR #5351 (commit 0c224fc7d), which added an early error when --build-for is used with shorthand platforms in remote builds. Tracked as CRAFT-4186. | |
| stealth/space-bunny-alpha | — | closed resolved | Snapcraft added an early error for `remote-build` when `--build-for` is combined with shorthand platform notation, avoiding opaque Launchpad failures. Fixed by merged PR #5351 (commit 0c224fc7d); tracked as CRAFT-4186. | |
| stealth/space-bunny-alpha | — | closed resolved | Remote builds now reject shorthand platform notation with --build-for before submission, providing a clearer error. Fixed by merged PR #5351. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed in PR #5351. Added validation to error when remote builds lack the required --build-for argument or shorthand platform notation, preventing unhelpful remote build failures. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed in #5351. Snapcraft now validates remote build requests by requiring the --build-for argument and shorthand platform notation, preventing unhelpful errors and improving user experience. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Fixed in PR #5351. Snapcraft now validates remote build requests by requiring both the --build-for argument and shorthand platform notation, preventing unhelpful errors and improving user experience. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
snapcraft#5351
(confidence 100%)
Merged fix for #5270, committed as 0c224fc7d.
-
Related To:
snapcraft#5687
(confidence 98%)
Later enabled --build-for with shorthand platforms after the Launchpad restriction was removed.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5351 fix(remote): error early for invalid platform usage | snapcraft | merged | PR #5351 merged as commit 0c224fc7d, adding an early, friendlier error when --build-for is used with shorthand project platforms instead of failing at Launchpad. Fixes #5270 (CRAFT-4186); restriction later lifted by #5687. |