Backend: Opt-out of the cache segregation by protected ref status default behavior
Problem
With the recent change to use a suffix on the cache key determined by the protected status, some customer's workflows are broken because their workflow relies on a shared cache for both protected and non-protected branches.
Related issue(s):
Proposal
- Allow users to configure an opt-out of the cache segregation by protected ref status in the .gitlab-ci.yml file.
using the suggested syntax which adds unprotect:
key
job1:
script:
- echo
cache:
key: "$CI_COMMIT_REF_SLUG"
paths:
- binaries/
unprotect: true # Uses the `non_protected` suffix in all cases
Implementation Details
{placeholder for details}
Edited by Mark Nuzzo