
Should you run macOS jobs from Tekton?
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…
Hi, I'm Bhawani
Platform engineer · Creator of dockstat · CI/CD & Kubernetes

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.