remote build: support attaching a build to a user-provided project
Metadata
Current evaluation
Remote builds gained support for user-provided projects, including permission and visibility checks for private builds. Fixed by merged PR canonical/craft-application#293 (8d50bcc8).
Resolution: closed resolved
Reason: PR #293 implemented user-provided projects for remote builds and was merged as commit 8d50bcc8. The maintainer explicitly closed #274 with a comment identifying that PR as the fix.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
The remote build service should be able to take a user-provided project name and use that for the remote build. Checks to make include:
1. That the user is allowed to create git repositories on this project
2. That the user is allowed to create recipes on this project
3. Whether this project is public or private (the build service should also expose this in a public API)
### Why it needs to get done
This is how we'll support private remote-build. The application will be able to accept a project name and build on a private project.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Remote builds gained support for user-provided projects, including permission and visibility checks for private builds. Fixed by merged PR canonical/craft-application#293 (8d50bcc8). | |
| stealth/space-bunny-alpha | — | closed resolved | Remote builds now accept user-provided projects with permission and visibility checks, enabling private builds; fixed by merged PR #293 (8d50bcc8). | |
| stealth/space-bunny-alpha | — | closed resolved | Remote build service now accepts a user-provided project with permission/private checks. Fixed by PR canonical/craft-application#293, merged as commit 8d50bcc8; mr-cal closed the issue citing that PR. | |
| stealth/space-bunny-alpha | — | closed resolved | Remote-build support for user-provided projects landed: PR canonical/craft-application#293 ('feat(remote-build): allow a user-provided project') merged as commit 8d50bcc8 and the issue was closed by mr-cal citing that PR. | |
| stealth/space-bunny-alpha | — | closed resolved | Remote builds now accept user-provided projects, with permission and visibility checks enabling private builds. Merged in canonical/craft-application#293. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed via pull request #293. The remote build service now accepts user-provided project names, enabling private builds with enforced permission and visibility checks. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed via PR #293. Remote build now accepts user-provided project names, enabling private builds with permission and visibility checks. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-application#293
(confidence 100%)
Merged PR implementing project permission and visibility handling for private remote builds.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #293 feat(remote-build): allow a user-provided project | craft-application | merged | Added support for user-provided projects in remote builds, resolving #274; PR #293 merged as commit 8d50bcc8. | |
| #4678 Accept and validate a user-provided project name for remote build | snapcraft | closed | Remote builds gained user-provided Launchpad project support, including private projects; fixed by merged canonical/craft-application#293. | |
| #5223 remote-build: refactor onto craft-application's command | snapcraft | closed | Remote-build was refactored onto craft-application's RemoteBuild in merged PR #5239 (commit f31d99498), bringing the requested upstream improvements. | |
| #4664 feat(craft-application): support remote build | snapcraft | merged | PR #4664 by syu-w merged (commit 57d184af7), adding remote build support to craft-application in Snapcraft, including --platform and --build-for handling. Shipped in the 8.0.0 release notes as the new core24 remote-builder. |