![]() ![]() ![]() If you use cache and artifacts to store the same path in your jobs, the cache mightīe overwritten because caches are restored before artifacts. Docker Machine (autoscale runners) The same as the Docker executor. Docker Locally, under Docker volumes: /var/lib/docker/volumes//_data////cache.zip. Runner executor Default path of the cache Shell Locally, under the gitlab-runner user’s home directory: /home/gitlab-runner/cache////cache.zip. The location also depends on the type of executor. Is stored on the machine where GitLab Runner is installed. The runner configuration defines where the file is stored. Where the caches are storedĪll caches defined for a job are archived in a single cache.zip file. Whether different runners are used to pass the cache between jobs.The availability of the cache depends on: To regenerate cached files in each job that needs them.Īfter you define a cache in. v -short Availability of the cacheĬaching is an optimization, but it isn’t guaranteed to always work. go/pkg/mod/ test : image : golang:1.13 extends. go-cache : variables : GOPATH : $CI_PROJECT_DIR/.go before_script : - mkdir -p. Per-cache fallback keys are appended with -protected or -non_protected. If the Use separate caches for protected branches setting is enabled,.If you clear caches manually, per-cache fallback keys are appended. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |