Use platform for build environment names
Metadata
Current evaluation
Fixed in commit 5ae7f878: build instance names now use the platform name instead of build-on/build-for, preventing platform environment collisions.
Resolution: closed resolved
Reason: Commit 5ae7f878 implemented the requested naming scheme, and the provider now generates names using build_info.platform.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Change the instance naming convention from:
```
<app>-<project>-on-<build-on>-for-<build-for>-<project-dir-inode>
```
to:
```
<app>-<project>-<platform>-<project-dir-inode>
```
### Why it needs to get done
To avoid the same instance getting used for different builds.
### Example
Currently, these use the same build environment:
```
platforms:
noble:
build-on: amd64
build-for: amd64
noble-debug:
build-on: amd64
build-for: amd64
```
This is also a problem for multi-base recipes (https://github.com/canonical/charmcraft/issues/2058).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed in commit 5ae7f878: build instance names now use the platform name instead of build-on/build-for, preventing platform environment collisions. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in commit 5ae7f878 by using the platform name in build-instance names, preventing incompatible build environments from being reused. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in commit 5ae7f878: build-environment instance names now use the platform name, preventing reuse across platforms with identical build architectures. | |
| stealth/space-bunny-alpha | — | closed stale | Platform-based instance naming was requested to prevent build-environment reuse. Closure left no implementation evidence or maintainer explanation beyond automated CRAFT-3859 and CRAFT-3858 ticket-sync comments. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. Automated Jira syncs indicate tracking moved internally to CRAFT-3859 and CRAFT-3858. No public fix, merge, or resolution was documented, suggesting the request was abandoned or handled offline. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The naming convention update proposal was routed to internal Jira tracking via automated bot comments, but received no discussion or implementation on GitHub. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a public resolution. The naming convention change to use platform identifiers was moved to internal Jira tracking (CRAFT-3858/3859) and remains unimplemented. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #601 feat: use platform name in build instance name | craft-application | merged | Merged in canonical/craft-application#601 as 5ae7f878: build instance names now use the platform, preventing environment reuse across platforms and fixing #600. |