kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/update
History
Achilleas Pipinellis 46813ccc45 Mention limitations of MySQL in docs
2017-06-19 16:58:51 +02:00
..
2.6-to-3.0.md
2.9-to-3.0.md
3.0-to-3.1.md
3.1-to-4.0.md
4.0-to-4.1.md
4.1-to-4.2.md
4.2-to-5.0.md
5.0-to-5.1.md
5.1-to-5.2.md
5.1-to-5.4.md
5.1-to-6.0.md
5.2-to-5.3.md
5.3-to-5.4.md
5.4-to-6.0.md
6.0-to-6.1.md
6.1-to-6.2.md
6.2-to-6.3.md
6.3-to-6.4.md
6.4-to-6.5.md
6.5-to-6.6.md
6.6-to-6.7.md
6.7-to-6.8.md
6.8-to-6.9.md
6.9-to-7.0.md
6.x-or-7.x-to-7.14.md
7.0-to-7.1.md
7.1-to-7.2.md
7.2-to-7.3.md
7.3-to-7.4.md
7.4-to-7.5.md
7.5-to-7.6.md
7.6-to-7.7.md
7.7-to-7.8.md
7.8-to-7.9.md
7.9-to-7.10.md
7.10-to-7.11.md
7.11-to-7.12.md
7.12-to-7.13.md
7.13-to-7.14.md
7.14-to-8.0.md
8.0-to-8.1.md
8.1-to-8.2.md
8.2-to-8.3.md
8.3-to-8.4.md
8.4-to-8.5.md
8.5-to-8.6.md
8.6-to-8.7.md
8.7-to-8.8.md
8.8-to-8.9.md
8.9-to-8.10.md
8.10-to-8.11.md Change to correct directory in update instructions 2017-04-27 09:47:15 +02:00
8.11-to-8.12.md Change to correct directory in update instructions 2017-04-27 09:47:15 +02:00
8.12-to-8.13.md Change to correct directory in update instructions 2017-04-27 09:47:15 +02:00
8.13-to-8.14.md Change to correct directory in update instructions 2017-04-27 09:47:15 +02:00
8.14-to-8.15.md
8.15-to-8.16.md
8.16-to-8.17.md
8.17-to-9.0.md
9.0-to-9.1.md Remove bin/comple from gitlab-shell v5.0.2 deployment procedure. 2017-05-24 01:03:29 +09:00
9.1-to-9.2.md Doc: Add the need to upgrade to Go 1.8.3 in the 9.1->9.2 documentation as the upgrade fails with Go 1.5 (installed with Gitlab 8.1) 2017-06-12 13:15:16 +00:00
9.2-to-9.3.md Go 1.8.3 and Upgrade-9.3 doc 2017-06-02 16:59:17 +02:00
9.3-to-9.4.md Stop using deprecated path field on Gitaly messages 2017-06-14 19:33:43 -04:00
mysql_to_postgresql.md
patch_versions.md Compile gitlab-shell go executables 2017-05-04 11:21:51 +02:00
README.md Mention limitations of MySQL in docs 2017-06-19 16:58:51 +02:00
restore_after_failure.md
upgrader.md Compile gitlab-shell go executables 2017-05-04 11:21:51 +02:00
upgrading_postgresql_using_slony.md

README.md

Updating GitLab

Depending on the installation method and your GitLab version, there are multiple update guides.

There are currently 3 official ways to install GitLab:

  • Omnibus packages
  • Source installation
  • Docker installation

Based on your installation, choose a section below that fits your needs.

Omnibus Packages

Installation from source

Installation using Docker

GitLab provides official Docker images for both Community and Enterprise editions. They are based on the Omnibus package and instructions on how to update them are in a separate document.

Upgrading without downtime

Starting with GitLab 9.1.0 it's possible to upgrade to a newer major, minor, or patch version of GitLab without having to take your GitLab instance offline. However, for this to work there are the following requirements:

  1. You can only upgrade 1 minor release at a time. So from 9.1 to 9.2, not to 9.3.
  2. You have to be on the most recent patch release. For example, if 9.1.15 is the last release of 9.1 then you can safely upgrade from that version to any 9.2.x version. However, if you are running 9.1.14 you first need to upgrade to 9.1.15.
  3. You have to use post-deployment migrations.
  4. You are using PostgreSQL. If you are using MySQL please look at the release post to see if downtime is required.

Upgrading between editions

GitLab comes in two flavors: Community Edition which is MIT licensed, and Enterprise Edition which builds on top of the Community Edition and includes extra features mainly aimed at organizations with more than 100 users.

Below you can find some guides to help you change editions easily.

Community to Enterprise Edition

Note: The following guides are for subscribers of the Enterprise Edition only.

If you wish to upgrade your GitLab installation from Community to Enterprise Edition, follow the guides below based on the installation method:

  • Source CE to EE update guides - Find your version, and follow the -ce-to-ee.md guide. The steps are very similar to a version upgrade: stop the server, get the code, update config files for the new functionality, install libraries and do migrations, update the init script, start the application and check its status.
  • Omnibus CE to EE - Follow this guide to update your Omnibus GitLab Community Edition to the Enterprise Edition.

Enterprise to Community Edition

If you need to downgrade your Enterprise Edition installation back to Community Edition, you can follow this guide to make the process as smooth as possible.

Miscellaneous