<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Build-Cache on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/build-cache/</link>
    <description>Recent content in Build-Cache on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/build-cache/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Remote Build Cache: BuildBuddy vs bazel-remote vs NativeLink (2026)</title>
      <link>https://www.pistack.xyz/posts/2026-05-03-self-hosted-remote-build-cache-buildbuddy-bazel-remote-nativelink-guide/</link>
      <pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-03-self-hosted-remote-build-cache-buildbuddy-bazel-remote-nativelink-guide/</guid>
      <description>&lt;p&gt;If you use Bazel or any build system that supports remote caching, you know the difference between local builds and remote-cached builds can mean the difference between a 30-second feedback loop and a 15-minute wait. Remote build caches store compiled artifacts, test results, and intermediate outputs on a shared server so that every developer and CI runner benefits from each other&amp;rsquo;s work.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
