Skip to content

ci(release): repoint macOS/Windows/checksums to self-hosted runners (finish #439) - #689

Merged
frstrtr merged 1 commit into
masterfrom
ci-steward/release-runner-repoint
Jul 13, 2026
Merged

ci(release): repoint macOS/Windows/checksums to self-hosted runners (finish #439)#689
frstrtr merged 1 commit into
masterfrom
ci-steward/release-runner-repoint

Conversation

@frstrtr

@frstrtr frstrtr commented Jul 13, 2026

Copy link
Copy Markdown
Owner

Finishes the #439 self-hosted migration for release.yml, which lagged build.yml (PR #617) because release.yml only fires on tags — the v0.2.1 tag exposed the gap.

Mirrors the exact fork-fallback guard build.yml already proved (head.repo == repository ? self-hosted : github-hosted):

job was now (self-hosted, fork-fallback)
macos arm64 (per-arch) macos-14 c2pool-mac-arm (Alonso-227) / macos-14
macos-universal (lipo merge) macos-14 c2pool-mac-arm / macos-14
windows windows-2022 [self-hosted,Windows,X64,c2pool-build] (VM217) / windows-2022
checksums / draft ubuntu-24.04 [self-hosted,Linux,X64,c2pool-build] / ubuntu-24.04

macos x86_64 (c2pool-mac-intel) and linux were already self-hosted. Pure config — no new infra; all runners live and used by build.yml daily.

Kept independent of the BCH __int128 fix (separate concern, unbundled per convention). integrator review + operator tap; no self-merge.

Finish the #439 self-hosted migration for release.yml, which lagged
build.yml (PR #617) because it only fires on tags — the v0.2.1 tag
exposed the gap. Mirror the exact fork-fallback guard build.yml proved:
head.repo == repository ? self-hosted : github-hosted.

- macos arm64 + macos-universal (lipo merge) -> c2pool-mac-arm (Alonso-227), else macos-14
- windows -> [self-hosted,Windows,X64,c2pool-build] (VM217), else windows-2022
- checksums/draft -> [self-hosted,Linux,X64,c2pool-build], else ubuntu-24.04

macos x86_64 (c2pool-mac-intel) and linux were already self-hosted.
Pure config; no new infra (runners live, build.yml uses them daily).
@frstrtr
frstrtr merged commit c79e4be into master Jul 13, 2026
31 of 32 checks passed
frstrtr added a commit that referenced this pull request Jul 14, 2026
VM217 (c2pool-windows-217) answers the windows-2022 label but has no
Git-bash on the runner-service PATH, so the Resolve-version / presence /
Install-Conan shell:bash steps died with "bash: command not found"
(release dispatch run 29298632408). Mirror build.yml Windows lane:
ExecutionPolicy-Bypass PowerShell defaults, PowerShell rewrites of the
three bash steps, and the py-launcher conan install with GITHUB_PATH
export. setup-python now gated off self-hosted. Completes #689 so the
repointed Windows runner is non-hollow.
frstrtr added a commit that referenced this pull request Jul 14, 2026
VM217 (c2pool-windows-217) answers the windows-2022 label but has no
Git-bash on the runner-service PATH, so the Resolve-version / presence /
Install-Conan shell:bash steps died with "bash: command not found"
(release dispatch run 29298632408). Mirror build.yml Windows lane:
ExecutionPolicy-Bypass PowerShell defaults, PowerShell rewrites of the
three bash steps, and the py-launcher conan install with GITHUB_PATH
export. setup-python now gated off self-hosted. Completes #689 so the
repointed Windows runner is non-hollow.
frstrtr added a commit that referenced this pull request Jul 14, 2026
…e conan) (#696)

* release.yml: port Windows lane to VM217 (bash->pwsh + py-resolve conan)

VM217 (c2pool-windows-217) answers the windows-2022 label but has no
Git-bash on the runner-service PATH, so the Resolve-version / presence /
Install-Conan shell:bash steps died with "bash: command not found"
(release dispatch run 29298632408). Mirror build.yml Windows lane:
ExecutionPolicy-Bypass PowerShell defaults, PowerShell rewrites of the
three bash steps, and the py-launcher conan install with GITHUB_PATH
export. setup-python now gated off self-hosted. Completes #689 so the
repointed Windows runner is non-hollow.

* release.yml: ASCII-ize Windows-lane warning (PS5.1 ANSI em-dash parse break)

VM217 has no pwsh, so the Windows job falls back to Windows PowerShell
5.1, which reads the GitHub-generated temp .ps1 as ANSI. The em-dash in
the Check-source-presence Write-Host string mis-decoded and broke string
parsing (missing terminator -> cascading } error), failing all 5 Windows
package cells at Check source presence. Swap the em-dash for ASCII --.

---------

Co-authored-by: frstrtr <frstrtr@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant