- Ubicloud Transparent Cache (Recommended)
- Ubicloud Cache Actions
Ubicloud Transparent Cache
It is the recommended way to use Ubicloud’s cache infrastructure. Transparent cache gives you immense flexibility when using Ubicloud’s runners, allowing you to switch between Ubicloud’s runners and GitHub’s default runners without modifying your workflow files.Transparent cache is enabled by default. If you need to disable it, you can do so in the Ubicloud console.
-
File/Folder Caching with
actions/cache
: Cache specific files or directories like dependencies or build outputs to speed up workflows. -
Package Manager Caching with
actions/setup-*
: Automatically caches dependencies for languages such as Python (actions/setup-python
), Node.js (actions/setup-node
), and Go (actions/setup-go
). 3rd party actions are also supported for some languages like Rust (Swatinem/rust-cache
). -
Docker Layer Caching with
docker/build-push-action
: Speeds up container builds by caching unchanged layers usingtype=gha
:
Ubicloud Cache Actions
Ubicloud Cache Actions are drop-in replacements foractions/cache
as ubicloud/cache
and actions/setup-*
as ubicloud/setup-*
.
It requires you to change the action names in your workflow files. It also doesn’t support docker layer caching. Only advantage of using Ubicloud Cache Actions over Transparent Cache is that it has 65% better save performance as it is optimized to increase concurrency during file uploads. We are working on improving Transparent Cache’s upload performance to match it.
Migrating to ubicloud/cache
Replace actions/cache
with ubicloud/cache
in your workflows. Ubicloud Cache fully supports GitHub Actions Cache functionality.
Migrating to Ubicloud’s Language-Specific Cache Actions
Ubicloud offers optimized replacements foractions/setup-*
. To migrate, replace actions/setup-*
with ubicloud/setup-*
in your workflows.