I have the following gitlab ci yaml file:
image: steveedson/ci
stages:
- build
cache:
untracked: true
key: "$CI_PROJECT_ID"
paths:
- node_modules/
- _site/vendor/
- .bundled/
- .yarn
build:
stage: build
script:
- ls -l
- yarn config set cache-folder .yarn
- yarn install
- ...
When my successful builds finish, they show:
Creating cache 1970478...
Created cache
And when the next commit triggers a build, I get:
Checking cache for 1970478...
Successfully extracted cache
But the ls -l
in my first step doesn't show the cached directories. I've tried caching the cache key but this doesn't help.
This is running on gitlab.com, not a private server.
By default, the cache is stored in the same place where GitLab Runner is installed. If the distributed cache is configured, S3 works as storage.
Caching in GitLab CI/CD (FREE) A cache is one or more files that a job downloads and saves. Subsequent jobs that use the same cache don't have to download the files again, so they execute more quickly.
all tiers. self-managed. By default, GitLab caches application settings for 60 seconds.
So, my configuration is correct, and Gitlab does support caches between jobs, however they have not added this to shared runners on gitlab.com, yet.
The issue is here https://gitlab.com/gitlab-com/infrastructure/issues/919 and should be added soon.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With