Target a queue named after a profile
Create a cluster agent token in Buildkite, connect it in Tuist, create self-hosted queues keyed after Tuist profiles, and target one from a step:
No Buildkite agent to install and no API token needed: logs ship with a job-scoped credential. See the Buildkite guide.
steps:
- label: "Test"
command: tuist test
agents:
- queue: macos
+ queue: tuist-macos
How it differs from your current agents
- No fleet to operate. Tuist provides the machines; pick a profile by CPU, memory, and Xcode or Ubuntu version.
- A build cache shared beyond CI. Runners share the Tuist cache with developer machines and coding agents.
- Directories that survive between jobs. Cache volumes keep build caches between jobs.