I added an option to read the cache key from a .cache_key file if present. This works very similar to how .tags file works with the drone/docker plugin.
This way, user can generate the cache key dynamically and in other build steps (currently cache.sh only reads from environment variables which cannot be shared between steps).
I explained in details how it can be used in DOCS.md. I also added an option to skip sanitization (yaml key is cache_key_disable_sanitize: true).
This allows for a simulation of how CircleCI caching works. For example:
I added an option to read the cache key from a
.cache_key
file if present. This works very similar to how.tags
file works with thedrone/docker
plugin.This way, user can generate the cache key dynamically and in other build steps (currently cache.sh only reads from environment variables which cannot be shared between steps).
I explained in details how it can be used in DOCS.md. I also added an option to skip sanitization (yaml key is
cache_key_disable_sanitize: true
).This allows for a simulation of how CircleCI caching works. For example: