Skip to content
Snippets Groups Projects
Commit 04acbc4a authored by Katrin Leinweber's avatar Katrin Leinweber
Browse files

Docs: Avoid redirects for upgrade path links

parent 5950c84e
No related branches found
No related tags found
2 merge requests!39Bumped oldstable branch to Heptapod 0.21,!31GitLab 13.10
......@@ -51,7 +51,7 @@
if [ -n "${OLD_VERSION_STRING}" ] ; then
# Minimum version from which jumps are permitted to current version.
# Follows https://docs.gitlab.com/ee/update/README.html#upgrade-paths
# Follows https://docs.gitlab.com/ee/update/index.html#upgrade-paths
MIN_VERSION=13.0
# Checking
......@@ -61,7 +61,7 @@
if ! greater_version $OLD_MINOR_VERSION $MIN_VERSION; then
notify "It seems you are upgrading from major version ${OLD_MAJOR_VERSION} to major version ${NEW_MAJOR_VERSION}."
notify "It is required to upgrade to the latest ${MIN_VERSION}.x version first before proceeding."
notify "Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/README.html#upgrade-paths"
notify "Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/index.html#upgrade-paths"
exit 1
fi
fi
......
......@@ -69,7 +69,7 @@
## Updating
- [Upgrade guidance](https://docs.gitlab.com/ee/update/README.html), including [supported upgrade paths](https://docs.gitlab.com/ee/update/README.html#upgrade-paths).
- [Upgrade guidance](https://docs.gitlab.com/ee/update/index.html), including [supported upgrade paths](https://docs.gitlab.com/ee/update/index.html#upgrade-paths).
- [Upgrade from Community Edition to Enterprise Edition](update/README.md#update-community-edition-to-enterprise-edition)
- [Update to the latest version](update/README.md#update-using-the-official-repositories)
- [Downgrade to an earlier version](update/README.md#downgrade)
......
......@@ -8,7 +8,7 @@
Before following these instructions, note the following:
- [Supported upgrade paths](https://docs.gitlab.com/ee/update/README.html#upgrade-paths)
- [Supported upgrade paths](https://docs.gitlab.com/ee/update/index.html#upgrade-paths)
has suggestions on when to upgrade.
- If you are upgrading from a non-Omnibus installation to an Omnibus installation, see
[Upgrading from a non-Omnibus installation to an Omnibus installation](convert_to_omnibus.md).
......@@ -16,7 +16,7 @@
WARNING:
If you aren't [using the current major version](#mandatory-upgrade-paths-for-version-upgrades),
you **must** follow the
[supported upgrade paths](https://docs.gitlab.com/ee/update/README.html#upgrade-paths)
[supported upgrade paths](https://docs.gitlab.com/ee/update/index.html#upgrade-paths)
when updating to the current version.
## Background migrations
......@@ -55,7 +55,7 @@
example 10.3 to 12.7 in one jump) that **can break GitLab
installations** due to multiple reasons like deprecated or removed configuration
settings, upgrade of internal tools and libraries, and so on. Users must follow
the [official upgrade paths](https://docs.gitlab.com/ee/update/README.html#upgrade-paths)
the [official upgrade paths](https://docs.gitlab.com/ee/update/index.html#upgrade-paths)
while upgrading their GitLab instances.
## Updating methods
......@@ -75,7 +75,7 @@
For safety reasons, you should maintain an up-to-date backup on your own if you plan to use this flag.
When upgrading to a new major version, remember to first [check for background migrations](https://docs.gitlab.com/ee/update/README.html#checking-for-background-migrations-before-upgrading).
When upgrading to a new major version, remember to first [check for background migrations](https://docs.gitlab.com/ee/update/index.html#checking-for-background-migrations-before-upgrading).
Unless you are following the steps in [Zero downtime updates](#zero-downtime-updates), your GitLab application will not be available to users while an update is in progress. They will either see a "Deploy in progress" message or a "502" error in their web browser.
......@@ -116,7 +116,7 @@
version can be problematic for older GitLab versions that require a multi-stage
upgrade path.
When following an [upgrade path](https://docs.gitlab.com/ee/update/README.html#upgrade-paths)
When following an [upgrade path](https://docs.gitlab.com/ee/update/index.html#upgrade-paths)
spanning multiple versions, for each upgrade, specify the intended GitLab version
number in your package manager's install or upgrade command:
......
......@@ -7,7 +7,7 @@
# GitLab 12 specific changes
NOTE:
When upgrading to a new major version, remember to first [check for background migrations](https://docs.gitlab.com/ee/update/README.html#checking-for-background-migrations-before-upgrading).
When upgrading to a new major version, remember to first [check for background migrations](https://docs.gitlab.com/ee/update/index.html#checking-for-background-migrations-before-upgrading).
## Prometheus 1.x Removal
......
......@@ -7,7 +7,7 @@
# GitLab 13 specific changes
NOTE:
When upgrading to a new major version, remember to first [check for background migrations](https://docs.gitlab.com/ee/update/README.html#checking-for-background-migrations-before-upgrading).
When upgrading to a new major version, remember to first [check for background migrations](https://docs.gitlab.com/ee/update/index.html#checking-for-background-migrations-before-upgrading).
## 13.0
......
......@@ -6,7 +6,7 @@
unless GitlabCtl::UpgradeCheck.valid?(old_version, new_version)
warn "It seems you are upgrading from major version #{old_version.split('.').first} to major version #{new_version.split('.').first}."
warn "It is required to upgrade to the latest #{GitlabCtl::UpgradeCheck::MIN_VERSION}.x version first before proceeding."
warn "Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/README.html#upgrade-to-a-new-major-version"
warn "Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/index.html#upgrading-to-a-new-major-version"
Kernel.exit 1
end
end
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment