https://github.com/zozo123/gha-cache-field-guide
MVP POC website for GitHub Actions cache strategy with Incredibuild and Islo
https://github.com/zozo123/gha-cache-field-guide
Last synced: 11 days ago
JSON representation
MVP POC website for GitHub Actions cache strategy with Incredibuild and Islo
- Host: GitHub
- URL: https://github.com/zozo123/gha-cache-field-guide
- Owner: zozo123
- Created: 2026-06-03T14:08:00.000Z (about 1 month ago)
- Default Branch: main
- Last Pushed: 2026-06-03T14:25:46.000Z (about 1 month ago)
- Last Synced: 2026-06-03T16:11:29.783Z (about 1 month ago)
- Language: HTML
- Homepage: https://zozo123.github.io/gha-cache-field-guide/
- Size: 9.77 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# CI Caching Is Not One Cache
Concise MVP POC microsite comparing what to use when accelerating GitHub Actions:
- native dependency/build caches for already-warm state,
- Incredibuild's proprietary Build Cache / CI-CD acceleration for fresh or dirty compiler work,
- BuildKit cache for Docker,
- disposable Islo runners as the clean-runner substrate.
The site is intentionally static so it can be published with GitHub Pages without
a build step.
## Run Locally
```bash
python3 -m http.server 8080
```
Then open:
```text
http://localhost:8080
```
## Publish
Push this repo to GitHub and enable Pages from the repository root, or serve the
folder from any static host.
## Message
Native caches are best when the same workspace is already warm. Incredibuild
Build Cache is strongest when GitHub Actions runners are fresh, ephemeral, or
invalidated by timestamp churn, because it restores compiler artifacts across
jobs and runners.
This is not a universal "IB beats every cache" story. It is a practical
comparison: C/C++ and Rust are strong Incredibuild candidates; Go, Docker, and
JavaScript usually want native/tool-specific caches first.
Docker note: BuildKit cache is the right Docker acceleration layer. Alpine TLS
no longer reproduces in the Islo sandbox; the full upstream `moby/buildkit` cold
Dockerfile still hits a BuildKit stream issue, so the demo should use a
controlled app Dockerfile.
## Links
- GitHub Actions: https://docs.github.com/en/actions
- Blacksmith: https://www.blacksmith.sh/
- Incredibuild CI/CD acceleration: https://www.incredibuild.com/solutions/ci-cd-acceleration
- Islo: https://islo.dev