Accept and validate a user-provided project name for remote build
Metadata
Current evaluation
Remote builds gained user-provided Launchpad project support, including private projects; fixed by merged canonical/craft-application#293.
Resolution: closed resolved
Reason: Merged PR canonical/craft-application#293, titled "feat(remote-build): allow a user-provided project", added selection and validation support for user-provided projects, including private-project remote builds.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
This requires https://github.com/canonical/craft-application/issues/274
Remote build should accept a user-provided project name. The project name will be selected as follows:
1. `--launchpad-project=<name>` in the command line
2. Fallback to `CRAFT_REMOTE_BUILD_PROJECT` environment variable
3. Get a project name from snap settings
4. Fall back to default
If any project name other than the default is provided through mechanisms 1-3, remote build should fail if the project does not exist or the user does not have correct permissions on it. Users wanting to use a non-default project must manage that project outside of snapcraft.
### Why it needs to get done
This enables private remote build by use of private projects.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Remote builds gained user-provided Launchpad project support, including private projects; fixed by merged canonical/craft-application#293. | |
| stealth/space-bunny-alpha | — | closed resolved | Added user-provided Launchpad projects for remote builds, including private-project support; fixed and closed by merged PR canonical/craft-application#293. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. An internal Jira ticket was created, but no pull requests were merged or code changes applied. The feature request was deferred or abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The request to accept and validate user-provided project names for remote builds was synced to Jira (CRAFT-2625) but shows no linked pull request or development activity, indicating it was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution, likely abandoned after syncing to internal Jira tracking. No implementation or merge occurred. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The feature request was abandoned or deferred due to the unmet upstream dependency and lack of follow-up activity or pull requests. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-application#293
(confidence 100%)
The merged PR implements user-provided Launchpad projects for remote builds and is recorded as fixing this issue.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #274 remote build: support attaching a build to a user-provided project | craft-application | closed | 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). | |
| #2648 remote-build: include project name in build-id | snapcraft | merged | Merged #2648, adding the project name to remote-build IDs (for example, snapcraft-figlet-<ID>) so builds are identifiable in the Launchpad portal. | |
| #634 feat: upstream --project flag for remote-build | craft-application | merged | Merged upstream --project support for remote-build, allowing builds to target a user-defined Launchpad project; landed in commit c5e963e7. |