Native compilation cache
Use the cache Xcode already reads and writes.
Share Xcode's native compilation cache across compatible macOS builds. Reuse requires compatible Xcode versions and matching physical source and DerivedData paths.
.boringcache.toml
workspace = "my-org/app" [adapters.xcode] tag = "xcode-cache" command = ["xcodebuild", "-workspace", "App.xcworkspace", "-scheme", "App", "build"]
boringcache xcode
permissions: contents: read id-token: write steps: - uses: boringcache/one@1781572d7b3ec5aef652f8ba479b981439b2776b # v1.48.2 with: mode: xcode trust-policy: auto - run: xcodebuild -workspace App.xcworkspace -scheme App -derivedDataPath "$BORINGCACHE_XCODE_DERIVED_DATA_PATH" build
steps: - label: Build command: > boringcache ci run --oidc-provider buildkite -- boringcache xcode
build: timeout: 1h id_tokens: BORINGCACHE_OIDC_TOKEN: aud: urn:boringcache:workload script: - boringcache ci run --oidc-provider gitlab -- boringcache xcode
Use the cache Xcode already reads and writes.
Restore reusable compiled work before the build.
Keep physical source and DerivedData paths aligned.
A shared workspace alone is not enough for Xcode. Match the required paths across machines, or use a consistent staging path, so compiled results have compatible identities.
Track compilation-cache reads, transfers, and stored data in your workspace.
Explore the workspace →BoringCache · GitHub macOS runner · 3 vCPU
100.0% of 217,417 lookups over 28 builds
Build times grouped by runner, with cold and warm builds shown separately.
Xcode
Benchmark →Video recording and live streaming application in C and C++.
Average restore, build and save · lower is better
3 vCPU · 7 GB · macOS 26 Apple M1
Apple M1 (Virtual)
Each table is one workflow run with one build per cache. A row marked Different CPU ran on another CPU model than BoringCache at the same level, so part of its time difference can come from the hardware.
| Cache | Cold | Warm | CPU |
|---|---|---|---|
| BoringCache Compilation cache | 11 min 17 s | 5 min 7 s | Apple M1 (Virtual) |
| GHA Cache Local cache directory restored and saved by actions/cache | 10 min 53 s | 4 min 21 s | Apple M1 (Virtual) |
BoringCache · GitHub macOS runner · 3 vCPU
100.0% of 217,417 lookups over 28 builds
Give consumers restore access and publishers a separate permission. Connect supported CI through OIDC or use scoped credentials.
Connect your CI →Separate readers and publishers
Send me a repo or a workflow and I'll take a look. I've spent more than a year on slow Docker, Cargo and Bazel builds in CI.
Install the CLI. Run onboarding to connect your repository and configure your cache.
30-day trial. No credit card required.
curl -sSL https://install.boringcache.com/install.sh | sh
boringcache onboard
boringcache xcode
We use cookies to understand how people use BoringCache. Privacy policy