macOS and Windows runners issue #71
open andymccall opened this · 0 comments
andymccall
From the competitor comparison (2026-10-19): GitHub, GitLab and TeamCity offer macOS and Windows runners; OxygenFlow runs only on Linux (microVM tier with KVM, syscall tier).
Goal: jobs that must build or test on macOS or Windows, with as much of Flow's isolation and receipts as each platform allows.
macOS: Apple hardware only (licensing). Isolation via Virtualization.framework VMs (macOS guests, ephemeral clones per job, as tart/Anka do), a new tier vz; or a weaker process tier (sandbox-exec) for trusted repositories.
Windows: Hyper-V VMs or Windows Sandbox per job (tier hyperv), or WSL2 for Linux-like jobs.
Same runner protocol, claims with arch/os, keyless receipts; placement by os (spec §11) so a job says runs-on "macos".
Images per platform (a macOS base with Xcode CLT; Windows with MSVC build tools), pinned and checked like rootfs images.
Hardware: a Mac mini and a Windows box would be needed (Andy's call).
Today's cross-builds (cargo-zigbuild, MinGW) stay for releases; this is for native builds and tests.
From the competitor comparison (2026-10-19): GitHub, GitLab and TeamCity offer macOS and Windows runners; OxygenFlow runs only on Linux (microVM tier with KVM, syscall tier).
Goal: jobs that must build or test on macOS or Windows, with as much of Flow's isolation and receipts as each platform allows.
vz; or a weakerprocesstier (sandbox-exec) for trusted repositories.hyperv), or WSL2 for Linux-like jobs.arch/os, keyless receipts; placement byos(spec §11) so a job saysruns-on "macos".Today's cross-builds (cargo-zigbuild, MinGW) stay for releases; this is for native builds and tests.