Tag · 7 posts
A CustomRun connects Tekton to disposable macOS VMs, but choosing that integration means owning results, retries and cleanup after Tekton stops waiting, with runner integrations offering another…
A fresh, pre-booted macOS VM cuts startup from 26s to 4.7s, including a similar saving through Tekton, at the cost of one VM slot and about 10 GiB of combined VM process RSS.
A macOS build can run twice after an agent restart, and Tekton can time out before its VM is deleted. Recovery needs durable results, one retry owner and independent cleanup.
A host journal tracks macOS build outcomes separately from VM deletion, with seven pipeline runs covering success, failure, cancellation and environment rejection before cloning.
Source and artifacts move between Tekton and a macOS VM through an OCI registry, with digest checks that caught an empty archive copied from a successful compilation.
A Tekton CustomRun delegates builds to a macOS VM, with the controller tracking build results and waiting for confirmed VM deletion on normal completion.