# Lint and Test — generate-cache-key
+ md5sum yarn.lock | awk '{print "my-service-"$1;}' > .cache_key
+ cat .cache_key
my-service-3915dae472a35a3dbba39b10e3ef37c1
+ ls /cache
my-service-3915dae472a35a3dbba39b10e3ef37c1
+ ls /cache/$(cat .cache_key) || exit 0
node_modules
# Lint and Test — restore-yarn-cache
Found a .cache_key file to be used as the cache path!
No cache for ./node_modules
# Lint and Test — install
+ yarn --offline
yarn install v1.19.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
[5/5] Building fresh packages...
Done in 88.63s.
# Lint and Test — rebuild-yarn-cache
Found a .cache_key file to be used as the cache path!
Warning! .cache_key will be used as-is. Sanitization is your responsibility to make it filename friendly!
Rebuilding cache for folder ./node_modules...
node_modules exists in the cache directory for the cache key generated so I'm a little confused why this isn't a hit.
drone.yaml:
Relevant output:
node_modules
exists in the cache directory for the cache key generated so I'm a little confused why this isn't a hit.