How Caching Works in Tenki
Learn how caching works in Tenki to speed up GitHub Actions runners. Achieve faster builds, performance improvements, and cost improvements with optimized CI caching.
Tenki fully supports GitHub Actions cache to help speed up workflows by reusing dependencies and build artifacts across runs.
No cache expiration
Tenki does not apply any expiration policy to caches. Once a cache is uploaded, it remains available until you explicitly overwrite it or delete it from Tenki UI. There is no time-based eviction.
No storage limits enforced by Tenki
Tenki does not enforce a global storage limit on caches. You can store as many cache entries as you need without worrying about eviction or cleanup from our side.
GitHub Actions cache size limits
While Tenki does not limit cache storage, GitHub Actions enforces a maximum size of 10 GB per cache key. This limit applies to each individual cache entry.
You can, however:
- Use multiple cache keys
- Store multiple 10 GB cache entries
- Keep all of them available in Tenki without eviction
What this means for your workflows
- Large projects can safely cache multiple dependency sets
- Monorepos can split caches by job, path, or dependency type -Long-lived caches remain available across workflow runs
Tenki ensures your GitHub Actions caches stay persistent, predictable, and under your control.