From 1eb82b65c554f21d83447f895a6208905fabe112 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Wed, 18 Sep 2019 14:14:39 +0000 Subject: Add latest changes from gitlab-org/gitlab@12-3-auto-deploy-20190916 --- doc/raketasks/backup_restore.md | 2 +- doc/raketasks/cleanup.md | 5 ----- 2 files changed, 1 insertion(+), 6 deletions(-) (limited to 'doc/raketasks') diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index bc9e429c431..c230bb413f2 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -992,7 +992,7 @@ and the lost data can be manually replaced. ### Container Registry push failures after restoring from a backup -If you use the [Container Registry](../user/packages/container_registry/index.md), you +If you use the [Container Registry](../user/project/container_registry.md), you may see pushes to the registry fail after restoring your backup on an Omnibus GitLab instance after restoring the registry data. diff --git a/doc/raketasks/cleanup.md b/doc/raketasks/cleanup.md index e2ec58be367..f84d29cca9a 100644 --- a/doc/raketasks/cleanup.md +++ b/doc/raketasks/cleanup.md @@ -16,11 +16,6 @@ sudo gitlab-rake gitlab:cleanup:dirs bundle exec rake gitlab:cleanup:dirs RAILS_ENV=production ``` -DANGER: **Danger:** -The following task does not currently work as expected. -The use will probably mark more existing repositories as orphaned. -For more information, see the [issue](https://gitlab.com/gitlab-org/gitlab-ee/issues/24633). - Rename repositories from all repository storage paths if they don't exist in GitLab database. The repositories get a `+orphaned+TIMESTAMP` suffix so that they cannot block new repositories from being created. -- cgit v1.2.1