Commit 4c698234 authored by lauraMon's avatar lauraMon

Enables ff by default

parent a17818c1
---
title: Enables multiple_cache_per_job feature flag by default
merge_request: 59016
author:
type: added
...@@ -5,4 +5,4 @@ rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/321877 ...@@ -5,4 +5,4 @@ rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/321877
milestone: '13.10' milestone: '13.10'
type: development type: development
group: group::pipeline authoring group: group::pipeline authoring
default_enabled: false default_enabled: true
...@@ -2884,14 +2884,12 @@ You can specify a [fallback cache key](#fallback-cache-key) to use if the specif ...@@ -2884,14 +2884,12 @@ You can specify a [fallback cache key](#fallback-cache-key) to use if the specif
##### Multiple caches ##### Multiple caches
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/32814) in GitLab 13.10. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/32814) in GitLab 13.10,
> - It's [deployed behind a feature flag](../../user/feature_flags.md), disabled by default. > and disabled by default.
> - It's disabled on GitLab.com. > - Enabled by default in GitLab 13.11.
> - It's not recommended for production use. > - Enabled on GitLab.com.
> - To use it in GitLab self-managed instances, ask a GitLab administrator to [enable it](#enable-or-disable-multiple-caches). **(FREE SELF)** > - Recommended for production use.
> - For GitLab self-managed instances, GitLab administrators can opt to [disable it](#enable-or-disable-multiple-caches). **(FREE SELF)**
WARNING:
This feature might not be available to you. Check the **version history** note above for details.
You can have a maximum of four caches: You can have a maximum of four caches:
...@@ -2920,10 +2918,10 @@ the fallback is fetched multiple times if multiple caches are not found. ...@@ -2920,10 +2918,10 @@ the fallback is fetched multiple times if multiple caches are not found.
##### Enable or disable multiple caches **(FREE SELF)** ##### Enable or disable multiple caches **(FREE SELF)**
The multiple caches feature is under development and not ready for production use. The multiple caches feature is under development but ready for production use.
It is deployed behind a feature flag that is **disabled by default**. It is deployed behind a feature flag that is **enabled by default**.
[GitLab administrators with access to the GitLab Rails console](../../administration/feature_flags.md) [GitLab administrators with access to the GitLab Rails console](../../administration/feature_flags.md)
can enable it. can opt to disable it.
To enable it: To enable it:
......
...@@ -8,8 +8,8 @@ module Gitlab ...@@ -8,8 +8,8 @@ module Gitlab
# Entry that represents a cache configuration # Entry that represents a cache configuration
# #
class Cache < ::Gitlab::Config::Entry::Simplifiable class Cache < ::Gitlab::Config::Entry::Simplifiable
strategy :Caches, if: -> (config) { Feature.enabled?(:multiple_cache_per_job) } strategy :Caches, if: -> (config) { Feature.enabled?(:multiple_cache_per_job, default_enabled: :yaml) }
strategy :Cache, if: -> (config) { Feature.disabled?(:multiple_cache_per_job) } strategy :Cache, if: -> (config) { Feature.disabled?(:multiple_cache_per_job, default_enabled: :yaml) }
class Caches < ::Gitlab::Config::Entry::ComposableArray class Caches < ::Gitlab::Config::Entry::ComposableArray
include ::Gitlab::Config::Entry::Validatable include ::Gitlab::Config::Entry::Validatable
......
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