visciang / mbs-example-monorepo Goto Github PK

This is about how we can leverage the caching mechanism of Git Hub Actions.
It is not the way we would cache in a hosted environment where we setup our build cache (for file artifacts and docker images).

We have two docker volumes attached to the MBS docker dind container:
- One that store file artifacts
- One that store the docker dind registry

The content of these volumes could be cached.
The "problem" with this approach is that the cache will grow indefinitely over time.

So we need a cache policy in place to expire things.
This custom cache logic shouldn't be part of MBS but an external user script.