https://bxm.net/tags/github-actions/ Recent content in Github Actions on BXM.net Hugo en-us Thu, 22 Oct 2026 00:00:00 +0000 https://bxm.net/memo-in-github-actions-skipped-a-rust-release-build-and-caught-runners-with-different-compilers/ Thu, 22 Oct 2026 00:00:00 +0000 https://bxm.net/memo-in-github-actions-skipped-a-rust-release-build-and-caught-runners-with-different-compilers/ <p>Most CI jobs build the same thing again and again. A docs fix or a typo in a README triggers the whole pipeline, and the release build runs as if the code had changed. This case study puts BXM Memo in front of one such step, a release build of the <code>bxm-canon</code> binary, and keeps Memo&rsquo;s cache between jobs with <code>actions/cache</code>.</p> <p>The workflow is in the <a href="https://github.com/softdevstudio/bxm">repository</a> as <code>.github/workflows/case-study-memo.yml</code>. Five jobs run one after another, each on a fresh GitHub-hosted runner. <code>plain</code> builds without Memo for the baseline. <code>cold</code> builds through Memo with an empty cache, <code>warm</code> changes nothing, <code>docs</code> edits the README, and <code>source</code> edits a Rust source file. The inputs are <code>canon/src/**</code>, <code>Cargo.toml</code> and <code>Cargo.lock</code>, and the salt is <code>rustc --version</code>, so a different compiler means a different result. We ran the whole workflow twice.</p>