Remote build: Uploaded repository should have the same information type as the project
Metadata
Current evaluation
Fixed by merged PR #615 (commit b394bdd6), making remote-build repositories and recipes inherit the project's Launchpad privacy.
Resolution: closed resolved
Reason: PR #615 was merged as commit b394bdd6 and changed repository creation to use the project's information type by default, applying the same privacy to recipes.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
When ensuring a repository exists for remote build, make its `information_type` be the same as the `information_type` for the project it's building in:
https://github.com/canonical/craft-application/blob/b398a0f20c8693ef1dfcb216d901da049c02d15a/craft_application/services/remotebuild.py#L275-L277
### To Reproduce
Run `snapcraft remote-build --project=<some-private-project>`
### part yaml
```shell
n/a
```
### Relevant log output
```shell
n/a
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #615 (commit b394bdd6), making remote-build repositories and recipes inherit the project's Launchpad privacy. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #615 (commit b394bdd6), aligning remote-build repository information_type with project privacy and applying the same privacy to Launchpad recipes. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a linked fix or merge. The request to align repository information_type with the project during remote build was abandoned on GitHub after internal tracking via Jira CRAFT-3984. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a repository fix. The request was tracked internally via Jira ticket CRAFT-3984. No pull request was merged. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a direct fix. Tracking moved to Jira ticket CRAFT-3984. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-application#615
(confidence 100%)
Merged fix for preserving project privacy in remote-build repositories and recipes.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #615 fix(launchpad): use the project's privacy for repos and recipes | craft-application | merged | Merged PR #615 in commit b394bdd6, fixing remote-builder uploads so Launchpad repositories and recipes inherit the project's privacy instead of becoming public. | |
| #5238 fix(remotebuild): use the project's privacy for repos and recipes | snapcraft | merged | Merged #5238 incorporated craft-application#615, preserving project privacy for remotely created Launchpad repositories and recipes; the fix shipped in Snapcraft 8.6.2. | |
| #5221 remote build: use the project's privacy for repos and recipes | snapcraft | closed | Remote builds now preserve project privacy for repositories and recipes; fixed by merged PR #5238 and released in Snapcraft 8.6.2. |