Commit 8436b72f authored by Alex Hanselka's avatar Alex Hanselka

Merge branch '11-9-stable-prepare-rc9' into '11-9-stable'

Prepare 11.9.0-rc9 release

See merge request gitlab-org/gitlab-ce!26322
parents 2eaeda28 26be8a1e
...@@ -18,7 +18,7 @@ gem 'gitlab-default_value_for', '~> 3.1.1', require: 'default_value_for' ...@@ -18,7 +18,7 @@ gem 'gitlab-default_value_for', '~> 3.1.1', require: 'default_value_for'
gem 'mysql2', '~> 0.4.10', group: :mysql gem 'mysql2', '~> 0.4.10', group: :mysql
gem 'pg', '~> 1.1', group: :postgres gem 'pg', '~> 1.1', group: :postgres
gem 'rugged', '~> 0.27' gem 'rugged', '~> 0.28'
gem 'grape-path-helpers', '~> 1.0' gem 'grape-path-helpers', '~> 1.0'
gem 'faraday', '~> 0.12' gem 'faraday', '~> 0.12'
......
...@@ -785,7 +785,7 @@ GEM ...@@ -785,7 +785,7 @@ GEM
rubyntlm (0.6.2) rubyntlm (0.6.2)
rubypants (0.2.0) rubypants (0.2.0)
rubyzip (1.2.2) rubyzip (1.2.2)
rugged (0.27.5) rugged (0.28.0)
safe_yaml (1.0.4) safe_yaml (1.0.4)
sanitize (4.6.6) sanitize (4.6.6)
crass (~> 1.0.2) crass (~> 1.0.2)
...@@ -1138,7 +1138,7 @@ DEPENDENCIES ...@@ -1138,7 +1138,7 @@ DEPENDENCIES
ruby-progressbar ruby-progressbar
ruby_parser (~> 3.8) ruby_parser (~> 3.8)
rubyzip (~> 1.2.2) rubyzip (~> 1.2.2)
rugged (~> 0.27) rugged (~> 0.28)
sanitize (~> 4.6) sanitize (~> 4.6)
sass (~> 3.5) sass (~> 3.5)
sass-rails (~> 5.0.6) sass-rails (~> 5.0.6)
......
...@@ -13,9 +13,9 @@ export default class VisualTokenValue { ...@@ -13,9 +13,9 @@ export default class VisualTokenValue {
} }
render(tokenValueContainer, tokenValueElement) { render(tokenValueContainer, tokenValueElement) {
const { tokenType } = this; const { tokenType, tokenValue } = this;
if (['none', 'any'].includes(tokenType)) { if (['none', 'any'].includes(tokenValue.toLowerCase())) {
return; return;
} }
......
export default (fn, interval = 2000, timeout = 60000) => { export default (fn, { interval = 2000, timeout = 60000 } = {}) => {
const startTime = Date.now(); const startTime = Date.now();
return new Promise((resolve, reject) => { return new Promise((resolve, reject) => {
const stop = arg => (arg instanceof Error ? reject(arg) : resolve(arg)); const stop = arg => (arg instanceof Error ? reject(arg) : resolve(arg));
const next = () => { const next = () => {
if (Date.now() - startTime < timeout) { if (timeout === 0 || Date.now() - startTime < timeout) {
setTimeout(fn.bind(null, next, stop), interval); setTimeout(fn.bind(null, next, stop), interval);
} else { } else {
reject(new Error('SIMPLE_POLL_TIMEOUT')); reject(new Error('SIMPLE_POLL_TIMEOUT'));
......
...@@ -20,6 +20,7 @@ export default class SSHMirror { ...@@ -20,6 +20,7 @@ export default class SSHMirror {
this.$btnDetectHostKeys = this.$form.find('.js-detect-host-keys'); this.$btnDetectHostKeys = this.$form.find('.js-detect-host-keys');
this.$btnSSHHostsShowAdvanced = this.$form.find('.btn-show-advanced'); this.$btnSSHHostsShowAdvanced = this.$form.find('.btn-show-advanced');
this.$dropdownAuthType = this.$form.find('.js-mirror-auth-type'); this.$dropdownAuthType = this.$form.find('.js-mirror-auth-type');
this.$hiddenAuthType = this.$form.find('.js-hidden-mirror-auth-type');
this.$wellAuthTypeChanging = this.$form.find('.js-well-changing-auth'); this.$wellAuthTypeChanging = this.$form.find('.js-well-changing-auth');
this.$wellPasswordAuth = this.$form.find('.js-well-password-auth'); this.$wellPasswordAuth = this.$form.find('.js-well-password-auth');
...@@ -167,6 +168,7 @@ export default class SSHMirror { ...@@ -167,6 +168,7 @@ export default class SSHMirror {
this.$wellPasswordAuth.collapse('hide'); this.$wellPasswordAuth.collapse('hide');
this.$wellSSHAuth.collapse('hide'); this.$wellSSHAuth.collapse('hide');
this.updateHiddenAuthType(selectedAuthType);
// This request should happen only if selected Auth type was SSH // This request should happen only if selected Auth type was SSH
// and SSH Public key was not present on page load // and SSH Public key was not present on page load
...@@ -234,6 +236,12 @@ export default class SSHMirror { ...@@ -234,6 +236,12 @@ export default class SSHMirror {
toggleAuthWell(authType) { toggleAuthWell(authType) {
this.$wellPasswordAuth.collapse(authType === AUTH_METHOD.PASSWORD ? 'show' : 'hide'); this.$wellPasswordAuth.collapse(authType === AUTH_METHOD.PASSWORD ? 'show' : 'hide');
this.$wellSSHAuth.collapse(authType === AUTH_METHOD.SSH ? 'show' : 'hide'); this.$wellSSHAuth.collapse(authType === AUTH_METHOD.SSH ? 'show' : 'hide');
this.updateHiddenAuthType(authType);
}
updateHiddenAuthType(authType) {
this.$hiddenAuthType.val(authType);
this.$hiddenAuthType.prop('disabled', authType === AUTH_METHOD.SSH);
} }
/** /**
......
...@@ -165,9 +165,12 @@ export default { ...@@ -165,9 +165,12 @@ export default {
}); });
}, },
initiateMergePolling() { initiateMergePolling() {
simplePoll((continuePolling, stopPolling) => { simplePoll(
this.handleMergePolling(continuePolling, stopPolling); (continuePolling, stopPolling) => {
}); this.handleMergePolling(continuePolling, stopPolling);
},
{ timeout: 0 },
);
}, },
handleMergePolling(continuePolling, stopPolling) { handleMergePolling(continuePolling, stopPolling) {
this.service this.service
...@@ -198,6 +201,7 @@ export default { ...@@ -198,6 +201,7 @@ export default {
}) })
.catch(() => { .catch(() => {
new Flash(__('Something went wrong while merging this merge request. Please try again.')); // eslint-disable-line new Flash(__('Something went wrong while merging this merge request. Please try again.')); // eslint-disable-line
stopPolling();
}); });
}, },
initiateRemoveSourceBranchPolling() { initiateRemoveSourceBranchPolling() {
......
...@@ -23,7 +23,10 @@ ...@@ -23,7 +23,10 @@
} }
.settings { .settings {
border-bottom: 1px solid $gray-darker; // border-top for each item except the top one
+ .settings {
border-top: 1px solid $border-color;
}
&:first-of-type { &:first-of-type {
margin-top: 10px; margin-top: 10px;
......
...@@ -15,7 +15,7 @@ class Admin::ProjectsController < Admin::ApplicationController ...@@ -15,7 +15,7 @@ class Admin::ProjectsController < Admin::ApplicationController
format.html format.html
format.json do format.json do
render json: { render json: {
html: view_to_html_string("admin/projects/_projects", locals: { projects: @projects }) html: view_to_html_string("admin/projects/_projects", projects: @projects)
} }
end end
end end
......
...@@ -26,7 +26,7 @@ class Dashboard::ProjectsController < Dashboard::ApplicationController ...@@ -26,7 +26,7 @@ class Dashboard::ProjectsController < Dashboard::ApplicationController
end end
format.json do format.json do
render json: { render json: {
html: view_to_html_string("dashboard/projects/_projects", locals: { projects: @projects }) html: view_to_html_string("dashboard/projects/_projects", projects: @projects)
} }
end end
end end
...@@ -43,7 +43,7 @@ class Dashboard::ProjectsController < Dashboard::ApplicationController ...@@ -43,7 +43,7 @@ class Dashboard::ProjectsController < Dashboard::ApplicationController
format.html format.html
format.json do format.json do
render json: { render json: {
html: view_to_html_string("dashboard/projects/_projects", locals: { projects: @projects }) html: view_to_html_string("dashboard/projects/_projects", projects: @projects)
} }
end end
end end
......
...@@ -15,7 +15,7 @@ class Explore::ProjectsController < Explore::ApplicationController ...@@ -15,7 +15,7 @@ class Explore::ProjectsController < Explore::ApplicationController
format.html format.html
format.json do format.json do
render json: { render json: {
html: view_to_html_string("explore/projects/_projects", locals: { projects: @projects }) html: view_to_html_string("explore/projects/_projects", projects: @projects)
} }
end end
end end
...@@ -30,7 +30,7 @@ class Explore::ProjectsController < Explore::ApplicationController ...@@ -30,7 +30,7 @@ class Explore::ProjectsController < Explore::ApplicationController
format.html format.html
format.json do format.json do
render json: { render json: {
html: view_to_html_string("explore/projects/_projects", locals: { projects: @projects }) html: view_to_html_string("explore/projects/_projects", projects: @projects)
} }
end end
end end
...@@ -44,7 +44,7 @@ class Explore::ProjectsController < Explore::ApplicationController ...@@ -44,7 +44,7 @@ class Explore::ProjectsController < Explore::ApplicationController
format.html format.html
format.json do format.json do
render json: { render json: {
html: view_to_html_string("explore/projects/_projects", locals: { projects: @projects }) html: view_to_html_string("explore/projects/_projects", projects: @projects)
} }
end end
end end
......
...@@ -3,7 +3,6 @@ ...@@ -3,7 +3,6 @@
module Projects module Projects
module Settings module Settings
class OperationsController < Projects::ApplicationController class OperationsController < Projects::ApplicationController
before_action :check_license
before_action :authorize_update_environment! before_action :authorize_update_environment!
helper_method :error_tracking_setting helper_method :error_tracking_setting
...@@ -65,10 +64,6 @@ module Projects ...@@ -65,10 +64,6 @@ module Projects
] ]
} }
end end
def check_license
render_404 unless helpers.settings_operations_available?
end
end end
end end
end end
...@@ -7,7 +7,7 @@ class ApplicationSetting < ActiveRecord::Base ...@@ -7,7 +7,7 @@ class ApplicationSetting < ActiveRecord::Base
include IgnorableColumn include IgnorableColumn
include ChronicDurationAttribute include ChronicDurationAttribute
add_authentication_token_field :runners_registration_token, encrypted: -> { Feature.enabled?(:application_settings_tokens_optional_encryption) ? :optional : :required } add_authentication_token_field :runners_registration_token, encrypted: -> { Feature.enabled?(:application_settings_tokens_optional_encryption, default_enabled: true) ? :optional : :required }
add_authentication_token_field :health_check_access_token add_authentication_token_field :health_check_access_token
DOMAIN_LIST_SEPARATOR = %r{\s*[,;]\s* # comma or semicolon, optionally surrounded by whitespace DOMAIN_LIST_SEPARATOR = %r{\s*[,;]\s* # comma or semicolon, optionally surrounded by whitespace
......
...@@ -10,7 +10,7 @@ module Ci ...@@ -10,7 +10,7 @@ module Ci
include FromUnion include FromUnion
include TokenAuthenticatable include TokenAuthenticatable
add_authentication_token_field :token, encrypted: -> { Feature.enabled?(:ci_runners_tokens_optional_encryption) ? :optional : :required } add_authentication_token_field :token, encrypted: -> { Feature.enabled?(:ci_runners_tokens_optional_encryption, default_enabled: true) ? :optional : :required }
enum access_level: { enum access_level: {
not_protected: 0, not_protected: 0,
......
...@@ -56,7 +56,7 @@ class Group < Namespace ...@@ -56,7 +56,7 @@ class Group < Namespace
validates :two_factor_grace_period, presence: true, numericality: { greater_than_or_equal_to: 0 } validates :two_factor_grace_period, presence: true, numericality: { greater_than_or_equal_to: 0 }
add_authentication_token_field :runners_token, encrypted: -> { Feature.enabled?(:groups_tokens_optional_encryption) ? :optional : :required } add_authentication_token_field :runners_token, encrypted: -> { Feature.enabled?(:groups_tokens_optional_encryption, default_enabled: true) ? :optional : :required }
after_create :post_create_hook after_create :post_create_hook
after_destroy :post_destroy_hook after_destroy :post_destroy_hook
......
...@@ -298,6 +298,11 @@ class MergeRequestDiff < ActiveRecord::Base ...@@ -298,6 +298,11 @@ class MergeRequestDiff < ActiveRecord::Base
private private
def encode_in_base64?(diff_text)
(diff_text.encoding == Encoding::BINARY && !diff_text.ascii_only?) ||
diff_text.include?("\0")
end
def create_merge_request_diff_files(diffs) def create_merge_request_diff_files(diffs)
rows = rows =
if has_attribute?(:external_diff) && Gitlab.config.external_diffs.enabled if has_attribute?(:external_diff) && Gitlab.config.external_diffs.enabled
...@@ -350,7 +355,7 @@ class MergeRequestDiff < ActiveRecord::Base ...@@ -350,7 +355,7 @@ class MergeRequestDiff < ActiveRecord::Base
diff_hash.tap do |hash| diff_hash.tap do |hash|
diff_text = hash[:diff] diff_text = hash[:diff]
if diff_text.encoding == Encoding::BINARY && !diff_text.ascii_only? if encode_in_base64?(diff_text)
hash[:binary] = true hash[:binary] = true
hash[:diff] = [diff_text].pack('m0') hash[:diff] = [diff_text].pack('m0')
end end
......
...@@ -313,6 +313,14 @@ class Note < ActiveRecord::Base ...@@ -313,6 +313,14 @@ class Note < ActiveRecord::Base
!system? !system?
end end
# Since we're using `updated_at` as `last_edited_at`, it could be touched by transforming / resolving a note.
# This makes sure it is only marked as edited when the note body is updated.
def edited?
return false if updated_by.blank?
super
end
def cross_reference_not_visible_for?(user) def cross_reference_not_visible_for?(user)
cross_reference? && !all_referenced_mentionables_allowed?(user) cross_reference? && !all_referenced_mentionables_allowed?(user)
end end
......
...@@ -85,7 +85,7 @@ class Project < ActiveRecord::Base ...@@ -85,7 +85,7 @@ class Project < ActiveRecord::Base
default_value_for :snippets_enabled, gitlab_config_features.snippets default_value_for :snippets_enabled, gitlab_config_features.snippets
default_value_for :only_allow_merge_if_all_discussions_are_resolved, false default_value_for :only_allow_merge_if_all_discussions_are_resolved, false
add_authentication_token_field :runners_token, encrypted: -> { Feature.enabled?(:projects_tokens_optional_encryption) ? :optional : :required } add_authentication_token_field :runners_token, encrypted: -> { Feature.enabled?(:projects_tokens_optional_encryption, default_enabled: true) ? :optional : :required }
before_validation :mark_remote_mirrors_for_removal, if: -> { RemoteMirror.table_exists? } before_validation :mark_remote_mirrors_for_removal, if: -> { RemoteMirror.table_exists? }
......
...@@ -9,6 +9,7 @@ ...@@ -9,6 +9,7 @@
= f.select :auth_method, = f.select :auth_method,
options_for_select(auth_options, mirror.auth_method), options_for_select(auth_options, mirror.auth_method),
{}, { class: "form-control js-mirror-auth-type qa-authentication-method" } {}, { class: "form-control js-mirror-auth-type qa-authentication-method" }
= f.hidden_field :auth_method, value: "password", class: "js-hidden-mirror-auth-type"
.form-group .form-group
.collapse.js-well-changing-auth .collapse.js-well-changing-auth
......
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
- setting = error_tracking_setting - setting = error_tracking_setting
%section.settings.expanded.border-0.no-animate %section.settings.expanded.no-animate
.settings-header .settings-header
%h4 %h4
= _('Error Tracking') = _('Error Tracking')
......
...@@ -2,5 +2,6 @@ ...@@ -2,5 +2,6 @@
- page_title _('Operations Settings') - page_title _('Operations Settings')
- breadcrumb_title _('Operations Settings') - breadcrumb_title _('Operations Settings')
= render_if_exists 'projects/settings/operations/incidents'
= render 'projects/settings/operations/error_tracking', expanded: true = render 'projects/settings/operations/error_tracking', expanded: true
= render_if_exists 'projects/settings/operations/tracing' = render_if_exists 'projects/settings/operations/tracing'
---
title: Disable timeout on merge request merging poll
merge_request: 25988
author:
type: fixed
---
title: Fix notes being marked as edited after resolving
merge_request: 26143
author:
type: fixed
---
title: Fix undefined variable error on json project views
merge_request: 26297
author:
type: fixed
---
title: Fix error creating a merge request when diff includes a null byte
merge_request: 26190
author:
type: fixed
...@@ -34,17 +34,59 @@ export ID_FROM=20 ...@@ -34,17 +34,59 @@ export ID_FROM=20
export ID_TO=50 export ID_TO=50
``` ```
You can monitor the progress in the _Admin > Monitoring > Background jobs_ screen. You can monitor the progress in the **Admin Area > Monitoring > Background Jobs** page.
There is a specific Queue you can watch to see how long it will take to finish: **project_migrate_hashed_storage** There is a specific Queue you can watch to see how long it will take to finish:
`hashed_storage:hashed_storage_project_migrate`
After it reaches zero, you can confirm every project has been migrated by running the commands bellow. After it reaches zero, you can confirm every project has been migrated by running the commands bellow.
If you find it necessary, you can run this migration script again to schedule missing projects. If you find it necessary, you can run this migration script again to schedule missing projects.
Any error or warning will be logged in the sidekiq's log file. Any error or warning will be logged in Sidekiq's log file.
You only need the `gitlab:storage:migrate_to_hashed` rake task to migrate your repositories, but we have additional You only need the `gitlab:storage:migrate_to_hashed` rake task to migrate your repositories, but we have additional
commands below that helps you inspect projects and attachments in both legacy and hashed storage. commands below that helps you inspect projects and attachments in both legacy and hashed storage.
## Rollback from Hashed storage to Legacy storage
If you need to rollback the storage migration for any reason, you can follow the steps described here.
NOTE: **Note:** Hashed Storage will be required in future version of GitLab.
To prevent new projects from being created in the Hashed storage,
you need to undo the [enable hashed storage][storage-migration] changes.
This task will schedule all your existing projects and associated attachments to be rolled back to the
Legacy storage type.
For Omnibus installations, run the following:
```bash
sudo gitlab-rake gitlab:storage:rollback_to_legacy
```
For source installations, run the following:
```bash
sudo -u git -H bundle exec rake gitlab:storage:rollback_to_legacy RAILS_ENV=production
```
Both commands accept a range as environment variable:
```bash
# to rollback any migrated project from ID 20 to 50.
export ID_FROM=20
export ID_TO=50
```
You can monitor the progress in the **Admin Area > Monitoring > Background Jobs** page.
On the **Queues** tab, you can watch the `hashed_storage:hashed_storage_project_rollback` queue to see how long the process will take to finish.
After it reaches zero, you can confirm every project has been rolled back by running the commands bellow.
If some projects weren't rolled back, you can run this rollback script again to schedule further rollbacks.
Any error or warning will be logged in Sidekiq's log file.
## List projects on Legacy storage ## List projects on Legacy storage
To have a simple summary of projects using **Legacy** storage: To have a simple summary of projects using **Legacy** storage:
......
...@@ -2,6 +2,24 @@ ...@@ -2,6 +2,24 @@
> [Introduced][ce-28283] in GitLab 10.0. > [Introduced][ce-28283] in GitLab 10.0.
Two different storage layouts can be used
to store the repositories on disk and their characteristics.
GitLab can be configured to use one or multiple repository shard locations
that can be:
- Mounted to the local disk
- Exposed as an NFS shared volume
- Acessed via [gitaly] on its own machine.
In GitLab, this is configured in `/etc/gitlab/gitlab.rb` by the `git_data_dirs({})`
configuration hash. The storage layouts discussed here will apply to any shard
defined in it.
The `default` repository shard that is available in any installations
that haven't customized it, points to the local folder: `/var/opt/gitlab/git-data`.
Anything discussed below is expected to be part of that folder.
## Legacy Storage ## Legacy Storage
Legacy Storage is the storage behavior prior to version 10.0. For historical Legacy Storage is the storage behavior prior to version 10.0. For historical
...@@ -66,34 +84,7 @@ by another folder with the next 2 characters. They are both stored in a special ...@@ -66,34 +84,7 @@ by another folder with the next 2 characters. They are both stored in a special
"@hashed/#{hash[0..1]}/#{hash[2..3]}/#{hash}.wiki.git" "@hashed/#{hash[0..1]}/#{hash[2..3]}/#{hash}.wiki.git"
``` ```
### How to migrate to Hashed Storage ### Hashed object pools
In GitLab, go to **Admin > Settings**, find the **Repository Storage** section
and select "_Use hashed storage paths for newly created and renamed projects_".
To migrate your existing projects to the new storage type, check the specific
[rake tasks].
[ce-28283]: https://gitlab.com/gitlab-org/gitlab-ce/issues/28283
[rake tasks]: raketasks/storage.md#migrate-existing-projects-to-hashed-storage
[storage-paths]: repository_storage_types.md
#### Rollback
There is no automated rollback implemented. Below are the steps required to rollback
from each storage migration.
The rollback has to be performed in the reverse order. To get into "Legacy" state,
you need to rollback Attachments first, then Project.
Also note that if Geo is enabled, after the migration was triggered, an event is generated
to replicate the operation on any Secondary node. That means the on disk changes will also
need to be performed on these nodes as well. Database changes will propagate without issues.
You must make sure the migration event was already processed or otherwise it may migrate
the files back to Hashed state again.
#### Hashed object pools
For deduplication of public forks and their parent repository, objects are pooled For deduplication of public forks and their parent repository, objects are pooled
in an object pool. These object pools are a third repository where shared objects in an object pool. These object pools are a third repository where shared objects
...@@ -110,36 +101,60 @@ enabled for individual projects by executing ...@@ -110,36 +101,60 @@ enabled for individual projects by executing
be on hashed storage, should not be a fork itself, and hashed storage should be be on hashed storage, should not be a fork itself, and hashed storage should be
enabled for all new projects. enabled for all new projects.
##### Attachments ### How to migrate to Hashed Storage
To rollback single Attachment migration, rename `aa/bb/abcdef1234567890...` folder back to `namespace/project`. To start a migration, enable Hashed Storage for new projects:
1. Go to **Admin > Settings** and expand the **Repository Storage** section.
2. Select the **Use hashed storage paths for newly created and renamed projects** checkbox.
Both folder names can be generated by the `FileUploader.absolute_base_dir(project)`, you Check if the change breaks any existing integration you may have that
just need to switch the version from the `project` back to the previous one. either runs on the same machine as your repositories are located, or may login to that machine
to access data (for example, a remote backup solution).
```ruby To schedule a complete rollout, see the
project.storage_version [rake task documentation for storage migration][rake/migrate-to-hashed] for instructions.
# => 2
FileUploader.absolute_base_dir(project) If you do have any existing integration, you may want to do a small rollout first,
# => "/opt/gitlab/embedded/service/gitlab-rails/public/uploads/@hashed/d4/73/d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35" to validate. You can do so by specifying a range with the operation.
project.storage_version = 1 This is an example of how to limit the rollout to Project IDs 50 to 100, running in
an Omnibus Gitlab installation:
FileUploader.absolute_base_dir(project) ```bash
# => "/opt/gitlab/embedded/service/gitlab-rails/public/uploads/gitlab/gitlab-shell-renamed" sudo gitlab-rake gitlab:storage:migrate_to_hashed ID_FROM=50 ID_TO=100
``` ```
##### Project Check the [documentation][rake/migrate-to-hashed] for additional information and instructions for
source-based installation.
#### Rollback
Similar to the migration, to disable Hashed Storage for new
projects:
To rollback single Project migration, move `@hashed/aa/bb/aabbcdef1234567890abcdef.git` and `@hashed/aa/bb/aabbcdef1234567890abcdef.wiki.git` 1. Go to **Admin > Settings** and expand the **Repository Storage** section.
back to `namespace/project.git` and `namespace/project.wiki.git` respectively and switch the version from the `project` back to `null`. 2. Uncheck the **Use hashed storage paths for newly created and renamed projects** checkbox.
To schedule a complete rollback, see the
[rake task documentation for storage rollback][rake/rollback-to-legacy] for instructions.
The rollback task also supports specifying a range of Project IDs. Here is an example
of limiting the rollout to Project IDs 50 to 100, in an Omnibus Gitlab installation:
```bash
sudo gitlab-rake gitlab:storage:rollback_to_legacy ID_FROM=50 ID_TO=100
```
If you have a Geo setup, please note that the rollback will not be reflected automatically
on the **secondary** node. You may need to wait for a backfill operation to kick-in and remove
the remaining repositories from the special `@hashed/` folder manually.
### Hashed Storage coverage ### Hashed Storage coverage
We are incrementally moving every storable object in GitLab to the Hashed We are incrementally moving every storable object in GitLab to the Hashed
Storage pattern. You can check the current coverage status below (and also see Storage pattern. You can check the current coverage status below (and also see
the [issue](https://gitlab.com/gitlab-com/infrastructure/issues/2821)). the [issue][ce-2821]).
Note that things stored in an S3 compatible endpoint will not have the downsides Note that things stored in an S3 compatible endpoint will not have the downsides
mentioned earlier, if they are not prefixed with `#{namespace}/#{project_name}`, mentioned earlier, if they are not prefixed with `#{namespace}/#{project_name}`,
...@@ -156,6 +171,7 @@ which is true for CI Cache and LFS Objects. ...@@ -156,6 +171,7 @@ which is true for CI Cache and LFS Objects.
| CI Artifacts | No | No | Yes | 9.4 / 10.6 | | CI Artifacts | No | No | Yes | 9.4 / 10.6 |
| CI Cache | No | No | Yes | - | | CI Cache | No | No | Yes | - |
| LFS Objects | Yes | Similar | Yes | 10.0 / 10.7 | | LFS Objects | Yes | Similar | Yes | 10.0 / 10.7 |
| Repository pools| No | Yes | - | 11.6 |