summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorit33 <it33@users.noreply.github.com>2016-01-10 19:42:08 -0800
committerit33 <it33@users.noreply.github.com>2016-01-10 19:42:08 -0800
commita1497aa73fb43a8ba73ba102e3660bd4337d71c3 (patch)
tree24736127401ab20f2d72770e0895dc9869f36358 /doc
parent3e87250b4404de32c677a04b36fb809cabdaf9f1 (diff)
downloadchat-a1497aa73fb43a8ba73ba102e3660bd4337d71c3.tar.gz
chat-a1497aa73fb43a8ba73ba102e3660bd4337d71c3.tar.bz2
chat-a1497aa73fb43a8ba73ba102e3660bd4337d71c3.zip
Update Upgrade-Guide.md
Diffstat (limited to 'doc')
-rw-r--r--doc/install/Upgrade-Guide.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/install/Upgrade-Guide.md b/doc/install/Upgrade-Guide.md
index 4480dedd2..1f3ff9510 100644
--- a/doc/install/Upgrade-Guide.md
+++ b/doc/install/Upgrade-Guide.md
@@ -43,7 +43,7 @@ The following instructions apply to updating installations of Mattermost v0.7-Be
Mattermost is designed to be upgraded sequentially through major version releases. If you skip versions when upgrading GitLab, you may find a `panic: The database schema version of 1.1.0 cannot be upgraded. You must not skip a version` error in your `/var/log/gitlab/mattermost/current` directory. If so:
1. Run `platform -version` to check your version of Mattermost
-2. If your version of the Mattermost binary doesn't match the version listed in the database error message, downgrade the version of the Mattermost binary you are using by [following the manual upgrade steps for Mattermost](/var/log/gitlab/mattermost/current) and using the database schema version listed in the error messages for the version you select in Step 1) iv).
+2. If your version of the Mattermost binary doesn't match the version listed in the database error message, downgrade the version of the Mattermost binary you are using by [following the manual upgrade steps for Mattermost](https://github.com/mattermost/platform/blob/master/doc/install/Upgrade-Guide.md#upgrading-mattermost-to-next-major-release) and using the database schema version listed in the error messages for the version you select in Step 1) iv).
3. Once Mattermost is working again, you can use the same upgrade procedure to upgrade Mattermost version by version to your current GitLab version. After this is done, GitLab automation should continue to work for future upgrades, so long as you don't skip versions.
| GitLab Version | Mattermost Version |