info:To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
---
# Updating GitLab installed with the Omnibus GitLab package
# Update GitLab installed with the Omnibus GitLab package
Before following these instructions, note the following:
...
...
@@ -8,6 +10,6 @@
See the[upgrade recommendations](https://docs.gitlab.com/ee/policy/maintenance.html#upgrade-recommendations)
for suggestions on when to upgrade.
If you are upgrading from a non-Omnibus installation to an Omnibus installation,
that can process jobs in the `background_migration` queue.
Updating to major versions might need some manual intervention. For more info,
check the version your are updating to:
...
...
@@ -32,8 +45,8 @@
From version 10.8 onwards, upgrade paths are enforced for version upgrades by
default. This restricts performing direct upgrades that skip major versions (for
example 10.3 to 12.7 in one jump) which can result in breakage of the GitLab
installations due to multiple reasons like deprecated or removed configuration
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 etc. Users will have to follow
the [official upgrade recommendations](https://docs.gitlab.com/ee/policy/maintenance.html#upgrade-recommendations)
while upgrading their GitLab instances.
...
...
@@ -42,8 +55,8 @@
There are two ways to update Omnibus GitLab:
- Using the official repositories
-Manually download the package
-[Using the official repositories](#updating-using-the-official-repositories).
-[Using a manually downloaded package](#updating-using-a-manually-downloaded-package).
Both will automatically back up the GitLab database before installing a newer
GitLab version. You may skip this automatic backup by creating an empty file
...
...
@@ -68,5 +81,7 @@
or [Enterprise Edition](https://about.gitlab.com/install/), then the
official GitLab repository should have already been set up for you.
To update to a newer GitLab version, all you have to do is:
To update to a newer GitLab version, run:
- For GitLab Community Edition:
...
...
@@ -72,6 +87,6 @@
```shell
# Debian/Ubuntu
sudo apt-get update
sudo apt-get install gitlab-ce
```shell
# Debian/Ubuntu
sudo apt-get update
sudo apt-get install gitlab-ce
...
...
@@ -77,5 +92,7 @@
# Centos/RHEL
sudo yum install gitlab-ce
```
# Centos/RHEL
sudo yum install gitlab-ce
```
- For GitLab Enterprise Edition:
...
...
@@ -81,9 +98,15 @@
If you are an Enterprise Edition user, replace `gitlab-ce` with `gitlab-ee` in
the above commands.
```shell
# Debian/Ubuntu
sudo apt-get update
sudo apt-get install gitlab-ee
# Centos/RHEL
sudo yum install gitlab-ee
```
### Updating using a manually downloaded package
If for some reason you don't use the official repositories, it is possible to
[download the package and install it manually](../manual_install.md).
...
...
@@ -84,11 +107,41 @@
### Updating using a manually downloaded package
If for some reason you don't use the official repositories, it is possible to
[download the package and install it manually](../manual_install.md).
1. Depending on the edition you already have installed, visit either:
- The [Community Edition repository](https://packages.gitlab.com/gitlab/gitlab-ce).
- The [Enterprise Edition repository](https://packages.gitlab.com/gitlab/gitlab-ee).
1. Select the package of the version you want to install.
1. Click **Download** to download the package.
1. After the GitLab package is downloaded, install it using the following commands:
- For GitLab Community Edition:
```shell
# GitLab Community Edition
# Debian/Ubuntu
dpkg -i gitlab-ce-<version>.deb
# CentOS/RHEL
rpm -Uvh gitlab-ce-<version>.rpm
```
- For GitLab Enterprise Edition:
```shell
# Debian/Ubuntu
dpkg -i gitlab-ee-<version>.deb
# CentOS/RHEL
rpm -Uvh gitlab-ee-<version>.rpm
```
## Updating Community Edition to Enterprise Edition
To upgrade an existing GitLab Community Edition (CE) server, installed using the
Omnibus packages, to GitLab Enterprise Edition (EE), all you have to do is
install the EE package on top of CE. While upgrading from the same version of
...
...
@@ -90,11 +143,14 @@
## Updating Community Edition to Enterprise Edition
To upgrade an existing GitLab Community Edition (CE) server, installed using the
Omnibus packages, to GitLab Enterprise Edition (EE), all you have to do is
install the EE package on top of CE. While upgrading from the same version of
CE to EE is not explicitly necessary, and any standard upgrade jump (i.e. 8.0
to 8.7) should work, in the following steps we assume that you are upgrading the
same versions.
CE to EE is not explicitly necessary, and any standard upgrade jump (i.e. 12.0
to 12.1) should work, in the following steps we assume that you are upgrading the
same versions as it is recommended that you first **upgrade to the same EE version**.
CAUTION: **Caution:**
When updating to EE from CE, avoid reverting back to CE if you plan on going to EE again in the future. Doing so can cause [database issues](#500-error-when-accessing-project--settings--repository-on-omnibus-installs) that may require Support intervention.
The steps can be summed up to:
...
...
@@ -106,8 +162,8 @@
sudo apt-cache policy gitlab-ce | grep Installed
```
The output should be similar to: `Installed: 8.6.7-ce.0`. In that case,
the equivalent Enterprise Edition version will be: `8.6.7-ee.0`. Write this
The output should be similar to: `Installed: 13.0.4-ce.0`. In that case,
the equivalent Enterprise Edition version will be: `13.0.4-ee.0`. Write this
value down.
**For CentOS/RHEL**
...
...
@@ -116,5 +172,5 @@
sudo rpm -q gitlab-ce
```
The output should be similar to: `gitlab-ce-8.6.7-ce.0.el7.x86_64`. In that
The output should be similar to: `gitlab-ce-13.0.4-ce.0.el8.x86_64`. In that
case, the equivalent Enterprise Edition version will be:
...
...
@@ -120,5 +176,5 @@
case, the equivalent Enterprise Edition version will be:
`gitlab-ee-8.6.7-ee.0.el7.x86_64`. Write this value down.
`gitlab-ee-13.0.4-ee.0.el8.x86_64`. Write this value down.
1. Add the `gitlab-ee`[Apt or Yum repository](https://packages.gitlab.com/gitlab/gitlab-ee/install):
...
...
@@ -141,8 +197,8 @@
1. Next, install the `gitlab-ee` package. Note that this will automatically
uninstall the `gitlab-ce` package on your GitLab server. `reconfigure`
Omnibus right after the `gitlab-ee` package is installed. Make sure that you
install the exact same GitLab version:
Omnibus right after the `gitlab-ee` package is installed. **Make sure that you
install the exact same GitLab version**:
**For Debian/Ubuntu**
...
...
@@ -151,7 +207,7 @@
sudo apt-get update
## Install the package using the version you wrote down from step 1
sudo apt-get install gitlab-ee=8.6.7-ee.0
sudo apt-get install gitlab-ee=13.0.4-ee.0
## Reconfigure GitLab
sudo gitlab-ctl reconfigure
...
...
@@ -161,9 +217,9 @@
```shell
## Install the package using the version you wrote down from step 1
sudo yum install gitlab-ee-8.6.7-ee.0.el7.x86_64
sudo yum install gitlab-ee-13.0.4-ee.0.el8.x86_64
## Reconfigure GitLab
sudo gitlab-ctl reconfigure
```
...
...
@@ -165,13 +221,13 @@
## Reconfigure GitLab
sudo gitlab-ctl reconfigure
```
NOTE: **Note:**
If you want to upgrade to EE and at the same time also update GitLab to the
latest version, you can omit the version check in the above commands. For
Debian/Ubuntu that would be `sudo apt-get install gitlab-ee`and for
CentOS/RHEL `sudo yum install gitlab-ee`.
NOTE: **Note:**
To upgrade to EE and also update GitLab to the latest version at the same time, you
can omit version information from the commands above. That is, run
`sudo apt-get install gitlab-ee` or `sudo yum install gitlab-ee`depending on your
distribution.
1. Now go to the GitLab admin panel of your server (`/admin/license/new`) and
upload your license file.
...
...
@@ -213,10 +269,11 @@
If you meet all the requirements above, follow these instructions in order. There are three sets of steps, depending on your deployment type: