remote-build: support `build_path` for snaps
Metadata
Current evaluation
Accepted and closed. The build_path enhancement for snaps is scoped to the remote-build subcommand for now, with plans to expand to other lifecycle commands later.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Launchpad added a `build_path` field to the [Snap recipe API](https://api.launchpad.net/devel.html#snap) in April 2026, similar to rock and charm recipes.
Craft-application should wire up this field, such that Snapcraft can provide a build path.
### Why it needs to get done
To unblock https://github.com/canonical/snapcraft/issues/6287 and allow users to do:
```bash
snapcraft remote-build --build-path path/to/snapcraft.yaml
```
Note:
It looks like the behavior for this is to cd to that directory and build. So this can support a monorepo with multiple, independent snap projects but not a monorepo containing shared code across multiple snap files.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Accepted and closed. The build_path enhancement for snaps is scoped to the remote-build subcommand for now, with plans to expand to other lifecycle commands later. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
15
Complexity:
45
Confidence:
90
Support Request:
0
|
keep open | Enhancement to support `build_path` for snaps in remote-build, unblocking snapcraft issue #6287. Currently under discussion regarding scope (remote-build only vs. all lifecycle commands). | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
5
Complexity:
40
Confidence:
95
Support Request:
5
|
keep open | Enhancement to wire up Launchpads new build_path field for snap recipes, enabling snapcraft to specify a build directory for remote builds. Currently under active discussion among maintainers regarding implementation scope. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
5
Complexity:
25
Confidence:
90
Support Request:
10
|
keep open | Enhancement to wire up Launchpad's new build_path field for Snap recipes in craft-application, enabling snapcraft remote-build to accept a custom build path. Currently triaged and awaiting implementation. |
Update history
| Date | Change |
|---|---|
| closed |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #6287 remote-build: support build paths | snapcraft | open | Enhancement to add --project-dir support for remote-build command, allowing users to specify build paths when multiple snapcraft.yaml files exist. Issue is triaged and assigned to a contributor after upstream dependency was resolved. | |
| #1128 feat(remotebuild): add build-path to snap recipes | craft-application | merged | Merged. Adds build-path to snap recipes and RemoteBuildService, resolving #1106 and unblocking snapcraft #6287. Exposed as --project-dir in the remote-build command. Approved by two reviewers and passed CI. | |
| #1968303 remote-build: support for snap relative sources | snapcraft (launchpad) | open | Remote build fails when a part uses a snapcraft extension path ($SNAPCRAFT_EXTENSIONS_DIR/ros2) as its source, because the remote builder cannot determine the source type. Open since ~2021 with no labels, comments, or maintainer response. | |
| #6372 feat(remote-build): add --project-dir argument to support build paths | snapcraft | open | Adds --project-dir argument to snapcraft remote-build for monorepo support. Under active review with maintainer suggesting alternative approaches using build-path or upstream monorepo feature. |