remote-build: migrate build-id generation
Metadata
Current evaluation
Build-ID generation was migrated in snapcraft#4385 (commit 5fc76d839), using the snap name and a hash of the project directory.
Resolution: closed resolved
Reason: The requested migration was implemented by PR #4385, committed as 5fc76d839, which added build-ID generation to the remote-build command.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Migrate code to generate the build-id:
- get the project name from the snapcraft.yaml
- generate the hash for the build-id in [`snapcraft_legacy/project/_project.py`](https://github.com/snapcore/snapcraft/blob/8758571f08fcdb896a25dce98d8bd6ee65a7f5f2/snapcraft_legacy/project/_project.py#L86).
This needs to be migrated to `snapcraft/commands/remote.py`.
### Why it needs to get done
The build-id format is `snapcraft-<snap-name>-<project-hash>`. The project hash is based on the entire contents of the project directory. This allows for parallel builds of the same project (see details [here](https://github.com/snapcore/snapcraft/pull/3554)).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Build-ID generation was migrated in snapcraft#4385 (commit 5fc76d839), using the snap name and a hash of the project directory. | |
| stealth/space-bunny-alpha | — | closed stale | Build-id generation migration closed without explanation or a linked PR or commit; PR #3554 provides the cited parallel-build design. | |
| stealth/space-bunny-alpha | — | closed resolved | Build-ID generation was migrated to the new remote-build command in PR #4385 (commit 5fc76d839). | |
| stealth/space-bunny-alpha | — | closed resolved | Remote-build build IDs were updated to use the project name; fixed in commit 592787d8f. | |
| qwen/qwen3.6-35b-a3b | — | — | Remote build-id generation migration was closed without comments or a linked pull request, indicating the task was abandoned or superseded by subsequent code refactoring. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a linked resolution or merge. The build-id generation migration task was abandoned, as no pull request or resolution was recorded. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation or discussion. The requested migration of build-id generation from legacy project code to remote commands was not completed and appears abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation or linked pull request. The build-id migration task was abandoned or superseded by later refactoring. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
snapcraft#4385
(confidence 98%)
Its title and path history directly match the requested remote-build build-ID migration.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #3014 meta: migrate get_build_base to Snap | snapcraft | merged | Merged in snapcraft#3014 via commit 09be6bb53, moving get_build_base from Projectinfo to Snap and simplifying tests to use Snap metadata instead of self.project.info. |