Commit aad7c672 authored by Stan Hu's avatar Stan Hu

ci: Bump all global cache keys for Debian bullseye

In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/80362 we
bumped the CI images from Debian buster to bullseye. We bumped the
cache key for everything but the QA gems, which appear to be cached in
the `setup-test-env`.

Since Debian bullseye uses libc 2.29 but buster uses 2.28, this led to
errors in the `14-7-stable-ee` branch running C extensions compiled
against the former
(https://gitlab.com/gitlab-org/gitlab/-/jobs/2091504634).

To avoid any potential conflicts between Debian bullseye and buster,
bump all the `v1` cache keys to `v2`.
parent 2bc3005f
......@@ -56,7 +56,7 @@
policy: pull
.go-pkg-cache: &go-pkg-cache
key: "go-pkg-v1"
key: "go-pkg-v2"
paths:
- .go/pkg/mod/
policy: pull
......@@ -66,7 +66,7 @@
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.node-modules-cache: &node-modules-cache
key: "node-modules-${NODE_ENV}-v1"
key: "node-modules-${NODE_ENV}-v2"
paths:
- node_modules/
- tmp/cache/webpack-dlls/
......@@ -91,7 +91,7 @@
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.storybook-node-modules-cache: &storybook-node-modules-cache
key: "storybook-node-modules-${NODE_ENV}-v1"
key: "storybook-node-modules-${NODE_ENV}-v2"
paths:
- storybook/node_modules/
policy: pull
......@@ -101,7 +101,7 @@
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.rubocop-cache: &rubocop-cache
key: "rubocop-v1"
key: "rubocop-v2"
paths:
- tmp/rubocop_cache/
policy: pull
......@@ -113,7 +113,7 @@
policy: push
.qa-ruby-gems-cache: &qa-ruby-gems-cache
key: "qa-ruby-gems-v1"
key: "qa-ruby-gems-v2"
paths:
- qa/vendor/ruby/
policy: pull
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment