Upgrade Path
You can check the upgrade path on the following site: https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/. This website is made by Gitlab, and will give a good overview about changes and new features for the upgrades you selected.
Checks
https://docs.gitlab.com/ee/update/index.html#checking-for-background-migrations-before-upgrading Check pending and failed DB migrations.
|
|
OPTIONAL: Check pending elasticsearch migrations
|
|
Update check
|
|
Pre-upgrade
Create a snapshot on the environment you are hosting your gitlab environment.
Set instance in maintenance mode:
|
|
Create a gitlab backup of latest version! https://docs.gitlab.com/ee/administration/backup_restore/ Make sure gitlab has the rights to read and write with the backup.
Disable advanced search before upgrading to a new major version. This is because of the index changes that are possible coming with new version. Checkout my reindex guide on gitlab advanced search to re-enable it.
Before the upgrade is started we need to stop subprocess puma and sidekiq on the gitlab server
|
|
We can check with following command if the services are really stopped.
|
|
The Upgrade
https://docs.gitlab.com/ee/update/package/index.html Upgrading to a specific version:
|
|
Upgrade to latest version:
|
|
Reconfigure and restart gitlab instance:
|
|
Turn maintenance mode off:
|
|
Enjoy newer version
Login on UI, to checkout the UI and the new features.