Lazy upgrade GitLab
Upgrading or installing GitLab can be a very simple or very complicated endeavor, depending on how you perform it and what are your requirements.
In my setup, I had GitLab version 12.6.3-ee.0 installed using Omnibus on an Ubuntu 18.04. At the moment, the latest version of GitLab is 13.3, but I chose to upgrade to the latest version of 13.2.x, as I considered it more stable. I will upgrade to 13.3.x when 13.4.x appears.
These are the raw information I used when choosing the upgrade path:
- https://docs.gitlab.com/omnibus/update/gitlab_12_changes.html
- https://docs.gitlab.com/omnibus/update/gitlab_13_changes.html
I chose to perform the upgrade in multiple stages, 7 to be more exact:
- 12.6.3 -> 12.6.8 -> 12.7.9 -> 12.8.10 -> 12.9.10 -> 12.10.14 -> 13.0.14 ->13.2.9
I have chosen the path as I wanted to perform upgrades between minor version to minor version. In addition, upgrade 12.6.3 -> 12.6.8 was added for a safer patch to patch version upgrade (according to semantic versioning MAJOR.MINOR.PATCH).
Besides the apt upgrade, two manual interventions were required:
- update unicorn settings when upgrading from 12.6.3-ee.0 to 12.6.8-ee.0
- upgrade postgres version to v11 after installing GitLab version 12.8.10-ee.0
The following script should not be run automatically, as things can go wrong between every upgrade. Perform functional tests between every upgrade to make sure GitLab works as expected.
The commands should be run with administrative privileges (sudo).