macOS hosted agents
macOS instances for Buildkite hosted agents are only offered with Apple silicon architecture. Please contact support if you have specific needs for Intel machines.
To accommodate different workloads, instances are capable of running up to 4 hours. If you require longer running agents, please contact support at support@buildkite.com.
Sizes
Buildkite offers a selection of macOS instance types (each based on a different size combination of virtual CPU power and memory capacity, known as an instance shape), allowing you to tailor your hosted agents' resources to the demands of your jobs.
| Instance shape | Size | vCPU | Memory | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Instance shape | Instance shape |
MACOS_ARM64_M4_6X28
|
Size | Size | Medium | vCPU | vCPU | 6 | Memory | Memory | 28 GB |
| Instance shape | Instance shape |
MACOS_ARM64_M4_12X56
|
Size | Size | Large | vCPU | vCPU | 12 | Memory | Memory | 56 GB |
Note: Shapes MACOS_M2_4X7, MACOS_M2_6X14, MACOS_M2_12X28, MACOS_M4_12X56 have been deprecated and will be removed on the 1st of July, 2025.
macOS instance software support
All standard macOS Sequoia and Sonoma version instances have their own respective Xcode and runtime software versions available by default (listed below). For both of these macOS versions, the Homebrew packages and their versions (listed further down) are also available. If you have specific requirements for software that is not listed here, please contact support.
Updated Xcode versions will be available one week after Apple offers them for download. This includes Beta, Release Candidate (RC), and official release versions.
macOS Sequoia
- 15.4.1
Xcode
- 16.3
- 16.2
- 16.1
- 16.0
- 15.4
Runtimes
iOS
- 18.4 RC
- 18.2 RC
- 18.1
- 18.0
- 17.5
- 16.4
- 15.5
tvOS
- 18.4 RC
- 18.2 RC
- 18.1
- 18.0
- 17.5
- 16.4
visionOS
- 2.4 RC
- 2.2 RC
- 2.1
- 2.0
- 1.2
- 1.1
- 1.0
watchOS
- 11.4 RC
- 11.2 RC
- 11.1
- 11.0
- 10.5
- 9.4
macOS Sonoma
- 14.6.1
Xcode
- 16.3-RC2
- 16.3
- 16.2
- 16.1
- 16.0
- 15.4
- 15.3
- 15.2
- 15.1
- 14.3.1
Runtimes
iOS
- 18.4 RC
- 18.2 RC
- 18.1
- 18.0
- 17.5
- 17.4
- 17.2
- 16.4
- 16.2
- 15.5
tvOS
- 18.4 RC
- 18.2 RC
- 18.1
- 18.0
- 17.5
- 17.4
- 17.2
- 16.4
visionOS
- 2.4 RC
- 2.2 RC
- 2.1
- 2.0
- 1.2
- 1.1
- 1.0
watchOS
- 11.4 RC
- 11.2 RC
- 11.1
- 11.0
- 10.5
- 10.4
- 10.2
- 9.4
Homebrew packages
| Package | Version |
|---|---|
| ant | 1.10.15_1 |
| applesimutils | 0.9.12 |
| aria2 | 1.37.0 |
| awscli | 2.25.49 |
| azcopy | 10.29.1 |
| azure-cli | 2.75.0 |
| bazelisk | 1.26.0 |
| bicep | 0.36.177 |
| carthage | 0.40.0 |
| cmake | 4.0.3 |
| cocoapods | 1.16.2_1 |
| codeql | 2.21.4 |
| curl | 8.14.1 |
| deno | 2.4.1 |
| docker | 28.3.0 |
| fastlane | 2.228.0 |
| gcc@13 | 13.4.0 |
| gh | 2.74.2 |
| git | 2.50.1 |
| git-lfs | 3.7.0 |
| gmp | 6.3.0 |
| gnu-tar | 1.35 |
| gnupg | 2.4.8 |
| go | 1.24.5 |
| gradle | 8.14.3 |
| httpd | 2.4.63 |
| jq | 1.8.1 |
| kotlin | 2.2.0 |
| libpq | 17.5 |
| llvm@15 | 15.0.7 |
| maven | 3.9.10 |
| mint | 0.18.0 |
| nginx | 1.29.0 |
| node | 24.3.0 |
| openssl@3 | 3.5.1 |
| p7zip | 17.06 |
| packer | 1.13.1 |
| perl | 5.40.2 |
| php | 8.4.10 |
| pkgconf | 2.5.1 |
| postgresql@14 | 14.18 |
| r | 4.5.1 |
| rbenv | 1.3.2 |
| rbenv-bundler | 1.0.1 |
| ruby | 3.4.4 |
| rust | 1.88.0 |
| rustup | 1.28.2 |
| selenium-server | 4.34.0 |
| swiftformat | 0.56.4 |
| swiftlint | 0.59.1 |
| tmux | 3.5a |
| unxip | 3.2 |
| wget | 1.25.0 |
| xcbeautify | 2.29.0 |
| xcodes | 1.6.2 |
| yq | 4.45.4 |
| zstd | 1.5.7 |
Git mirror cache
The Git mirror cache is a specialized type of cache volume designed to accelerate Git operations by caching the Git repository between builds. This is useful for large repositories that are slow to clone.
These volumes are attached on a best-effort basis depending on their locality, expiration and current usage, and therefore, should not be relied upon as durable data storage. By default, a Git mirror cache is created for each repository.
Enabling Git mirror cache
To enable Git mirror cache for your hosted agents:
- Select Agents in the global navigation to access the Clusters page.
- Select the cluster in which to enable the Git mirror cache feature.
- Select Cache Storage, then select the Settings tab.
- Select Enable Git mirror, then select Save cache settings to enable Git mirrors for the selected hosted cluster.
Once enabled, the Git mirror cache will be used for all hosted jobs using Git repositories in that cluster. A separate cache volume will be created for each repository.
Deleting Git mirror cache
Deleting a cache volume may affect the build time for the associated pipelines until the new cache is established.
To delete a git mirror cache:
- Select Agents in the global navigation to access the Clusters page.
- Select the cluster whose Git mirror cache is to be deleted.
- Select Cache Storage, then select the Volumes tab to view a list of all exiting cache volumes.
- Select Delete for the Git mirror cache volume you wish to remove.
- Confirm the deletion by selecting Delete Cache Volume.