Skip to content
Xcode build cache

Reuse Xcode compilation cache on a fresh Mac.

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

How BoringCache fits your build.

Native compilation cache

Use the cache Xcode already reads and writes.

Fresh CI machines

Restore reusable compiled work before the build.

Matching paths

Keep physical source and DerivedData paths aligned.

Make compatibility part of the setup.

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.

See cache activity across your Mac builds.

Track compilation-cache reads, transfers, and stored data in your workspace.

Explore the workspace →
OBS Studio · Workspace insights
Cache hits

BoringCache · GitHub macOS runner · 3 vCPU

100.0% of 217,417 lookups over 28 builds

Served from the runner
Under 1 ms per read
Read from cache
30.8 GB

Xcode benchmark

All Xcode results →

Build times grouped by runner, with cold and warm builds shown separately.

OBS Studio

Xcode

Benchmark →

Video recording and live streaming application in C and C++.

Average restore, build and save · lower is better

GitHub macOS runner

3 vCPU · 7 GB · macOS 26 Apple M1

BoringCache
5 min 22 s 28 builds
GHA Cache
4 min 53 s 28 builds

Apple M1 (Virtual)

Cold and warm builds

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.

One cold and warm build per cache
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)
Cache hits

BoringCache · GitHub macOS runner · 3 vCPU

100.0% of 217,417 lookups over 28 builds

Served from the runner
Under 1 ms per read
Read from cache
30.8 GB

Keep shared-cache publication in trusted jobs.

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

  • Trusted builds Publish shared cache for the next build Read + publish
  • Pull requests Restore cache without replacing it Read only
  • Local development Use a scoped credential for the workspace Scoped access

Common questions

Does this replace Xcode's build system?
No. xcodebuild still plans and runs the build. BoringCache manages the compilation cache it reads and writes.
Does it work on ephemeral macOS CI runners?
Yes, when builds use matching paths. Xcode includes physical source and DerivedData paths in cache identity, so runners need matching paths or the same staging path to share compiled work.
Can a local Mac reuse cache from any CI provider?
Not automatically. The workspace can be the same, but builds with different physical source or DerivedData paths cannot share compiled results.
Read the Xcode setup guide →

Can I help with your build?

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.

Get help with your build

Set up Xcode caching

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