Use platform for build environment names
Metadata
Current evaluation
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.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned. The proposed build environment naming convention change to include the platform was closed without resolution or an associated pull request. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5015 Use craft-platforms for build plans | snapcraft | closed | Closed and synced to Jira as CRAFT-3322. No repository changes or merges were applied. The task remains deferred pending resolution of craft-platforms issue #5. | |
| #693 craft-platforms errors aren't caught | craft-application | closed | Closed without a code fix; tracking moved to Jira CRAFT-4371. | |
| #1535 Implement platforms for charmcraft | charmcraft | closed | Closed without implementation. No pull requests were merged or code changes applied. The request appears abandoned or migrated to internal Jira tracking (CRAFT-2514) without a GitHub resolution. | |
| #4993 Use craft-platforms utilities | snapcraft | closed | Closed and abandoned. The issue requested replacing local architecture utilities with craft-platforms to reduce duplication. No pull request was submitted, and the task was left unresolved after an internal Jira ticket was created. |