ci(core22-7): don't use a spread runner for publishing the rock
Metadata
Current evaluation
Merged PR #83 restricted core22-7 rock publishing to amd64 runners, preventing scheduling on resource-constrained Spread runners; all CI checks passed.
Resolution: closed resolved
Reason: The approved one-line workflow change was merged in PR #83. Adding the amd64 runner label isolates publishing from Spread-runner resource contention.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Resource contention could cause us to try to publish on the spread runner. This has us use the `amd64` runner label so we don't do so.
I tricked the fourth run of [this job](https://github.com/canonical/snapcraft-rocks/actions/runs/15621518381/job/44009148202) by loading up the spread runner :-)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #83 restricted core22-7 rock publishing to amd64 runners, preventing scheduling on resource-constrained Spread runners; all CI checks passed. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #83, assigning core22-7 rock publishing to an amd64 runner to avoid spread-runner resource contention; all CI checks passed. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged a one-line CI configuration change to use the amd64 runner label for rock publishing, resolving resource contention issues on spread runners. Approved by one reviewer with all CI checks passing. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a CI fix that switches the rock publishing job to the amd64 runner label. This prevents resource contention from accidentally triggering publishes on the spread runner. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #81 ci(core22-8): don't use a spread runner for publishing the rock | snapcraft-rocks | merged | Merged #81 constrained core22-8 rock publishing to amd64 runners, preventing resource contention from routing publication to a Spread runner. | |
| #82 ci(core24-8): don't use a spread runner for publishing the rock | snapcraft-rocks | merged | Merged PR #82 targeted core24-8 publishing to the amd64 runner label, avoiding accidental use of resource-contended Spread runners. | |
| #78 feat(core22-7): publish as a multi-arch rock | snapcraft-rocks | merged | Merged #78 into core22-7, adding amd64/arm64 multi-arch rock publishing for SNAPCRAFT-1156. Review was approved and all CI checks passed. | |
| #79 feat(core22-8): publish as a multi-arch rock | snapcraft-rocks | merged | Merged #79, adding amd64/arm64 rock publishing for core22-8 under SNAPCRAFT-1156; it required #75, brought #72's approach to the core22 branch, and completed #35. | |
| #116 ci: always discard spread workers in build-rock tests (core22-7) | snapcraft-rocks | open | Adds an always-run 'Discard spread workers' cleanup step to the spread-tests job in .github/workflows/build-rock.yaml (core22-7) so GCP VMs aren't leaked on cancellation (SNAPCRAFT-1368). +8/-0, spread-tests green, build-rock amd64/arm64 failing. | |
| #115 ci: always discard spread workers in build-rock tests (core22-8) | snapcraft-rocks | merged | PR #115 merged (+8/-0): adds an always-run 'Discard spread workers' step to the spread-tests job in .github/workflows/build-rock.yaml for core22-8, so cancelled/crashed jobs no longer leak spread GCP VMs (SNAPCRAFT-1368). | |
| #72 feat(ci): publish as a multi-arch rock | snapcraft-rocks | merged | Merged PR #72 added amd64/arm64 multi-arch rock publishing for core24-8, cherry-picking the test fix from #73 as part of #35. |