Skip to content

GHA: remove CACHE_VERSION from bazel disk cache key - #3475

Open
ser-io wants to merge 1 commit into
google:mainfrom
ser-io:gha-unused-BAZEL_REMOTE_CACHE
Open

ser-io wants to merge 1 commit into
google:mainfrom
ser-io:gha-unused-BAZEL_REMOTE_CACHE

Conversation

@ser-io

@ser-io ser-io commented Oct 30, 2026

Copy link
Copy Markdown
Member

CACHE_VERSION was only a kill switch to discard the GHA cache, which is not needed since caches can be deleted from the Actions cache UI. This also stops exporting the unused BAZEL_REMOTE_CACHE into GHA.

Bug: b/576339701

CACHE_VERSION was only a kill switch to discard the GHA cache, which
is not needed since caches can be deleted from the Actions cache UI.
This also stops exporting the unused BAZEL_REMOTE_CACHE into GHA.

Bug: b/576339701
@ser-io
ser-io requested review from Databean and rmuthiah October 30, 2026 18:31
INPUTS_ACTION_NAME: ${{ inputs.action-name }}
- name: Generate cache key prefix
run: echo "CACHE_KEY_PREFIX=${{ runner.os }}-${{ runner.arch }}-bazel-disk-cache-${CACHE_VERSION}-${INPUTS_ACTION_NAME}-${JOB_HASH}" >> $GITHUB_ENV
run: echo "CACHE_KEY_PREFIX=${{ runner.os }}-${{ runner.arch }}-bazel-disk-cache-${INPUTS_ACTION_NAME}-${JOB_HASH}" >> $GITHUB_ENV

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought one of the other motivations of the cache key was to avoid cross-contamination between long-lived version branches and main, is that going to be a problem again?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants