Use a more repeatable identity for remote builds
Metadata
Current evaluation
Closed without resolution. Superseded by internal Jira ticket CRAFT-2556. No public fix or implementation was merged.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Instead of naming remote builds based on file contents, name it something that will remain the same for the lifespan of a project.
For example, hash the hostname, the project directory inode, and the build base (thus changing the name only when the user changes the build base).
### Why it needs to get done
Currently we can't resume a remote build without knowing its ID.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Superseded by internal Jira ticket CRAFT-2556. No public fix or implementation was merged. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation after extended inactivity. The request for repeatable remote build identities was abandoned, with tracking transferred to internal Jira ticket CRAFT-2556. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and superseded by internal Jira ticket CRAFT-2556. No public fix or merge was implemented. The proposal to replace file-based build names with a deterministic hash remains unresolved. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4842 remote build: document nuances of current and legacy remote builders | snapcraft | closed | Closed without implementation. The scope was split into three sub-tasks, but no changes were made. The issue was superseded by internal Jira ticket CRAFT-3000 and abandoned after over two years. |