actions/cache works as it does on any self-hosted runner, and the
shared pool a new organization starts on has no Docker yet (see Limits). A Coreload cache
next to the machines, on dedicated machines first. (coming soon) Then the same cache for every job on the shared pool. (coming soon)
Nothing in your workflow needs to change when it arrives.Runners
Caching
Caching on Coreload: no Coreload cache for customer jobs yet; dedicated machines first, then the shared pool, both coming soon.
There is no Coreload cache for customer jobs yet: