If you’ve been following our community calls and plans on the forum, you’ll have heard a lot of talk about building out a new infrastructure for delivering cache (and soon registry) artifacts.
This started with the launch of the Xcode cache, which has been running on regionally distributed infrastructure from its inception, and is now continuing with us making it the default for serving the module cache used by tuist cache and tuist generate, starting with Tuist CLI 4.28.0.
What this means for you
Both cache uploads and downloads will become faster and more reliable. We have been testing this new infrastructure ourselves and with a select few customers where it has resolved a whole bunch of file size and rate limits. The distributed nature of these new nodes will be especially impactful if you’re not from Central Europe, where our server has so far been the middleman of all cache-related requests.
On the surface, nothing should change. The CLI, analytics and dashboard all stay the same. You can also check out the new Cache endpoint display in the dashboard, showing you which region you were connected to.
This change does require a fresh tuist cache run for warming the cache, as the new storage infrastructure means that old artifacts are not carrying over.
For the foreseeable future, you can fall back to the old infrastructure by setting TUIST_LEGACY_MODULE_CACHE="1" in your environment. Please note that this option will be removed in the future, so we do not suggest relying on it past a short migration period of re-warming the cache.
If you see any issues after upgrading, please let us know.