2016-04-21 06:07:33 -04:00
|
|
|
# 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.
|
|
|
|
|
|
2014-10-02 06:39:26 -04:00
|
|
|
## Omnibus Packages
|
|
|
|
|
|
2016-05-13 17:17:01 -04:00
|
|
|
- The [Omnibus update guide](http://docs.gitlab.com/omnibus/update/README.html)
|
2016-04-21 06:07:33 -04:00
|
|
|
contains the steps needed to update an Omnibus GitLab package.
|
2014-10-02 06:39:26 -04:00
|
|
|
|
2015-02-16 12:10:07 -05:00
|
|
|
## Installation from source
|
2014-10-02 06:39:26 -04:00
|
|
|
|
2016-04-21 06:07:33 -04:00
|
|
|
- [Upgrading Community Edition from source][source-ce] - The individual
|
|
|
|
|
upgrade guides are for those who have installed GitLab CE from source.
|
|
|
|
|
- [Upgrading Enterprise Edition from source][source-ee] - The individual
|
|
|
|
|
upgrade guides are for those who have installed GitLab EE from source.
|
2016-04-19 12:12:12 -04:00
|
|
|
- [Patch versions](patch_versions.md) guide includes the steps needed for a
|
2016-04-21 06:07:33 -04:00
|
|
|
patch version, eg. 6.2.0 to 6.2.1, and apply to both Community and Enterprise
|
|
|
|
|
Editions.
|
|
|
|
|
|
|
|
|
|
## 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][omnidocker].
|
|
|
|
|
|
2017-04-12 12:15:19 -04:00
|
|
|
## Upgrading without downtime
|
|
|
|
|
|
2017-04-13 11:39:06 -04:00
|
|
|
Starting with GitLab 9.1.0 it's possible to upgrade to a newer major, minor, or patch version of GitLab
|
2017-04-12 12:15:19 -04:00
|
|
|
without having to take your GitLab instance offline. However, for this to work
|
|
|
|
|
there are the following requirements:
|
|
|
|
|
|
2017-04-13 11:39:06 -04:00
|
|
|
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.
|
2017-04-12 12:15:19 -04:00
|
|
|
However, if you are running 9.1.14 you first need to upgrade to 9.1.15.
|
|
|
|
|
2. You have to use [post-deployment
|
|
|
|
|
migrations](../development/post_deployment_migrations.md).
|
2017-04-13 11:39:06 -04:00
|
|
|
3. You are using PostgreSQL. If you are using MySQL please look at the release post to see if downtime is required.
|
2017-04-12 12:15:19 -04:00
|
|
|
|
2016-04-21 06:07:33 -04:00
|
|
|
## Upgrading between editions
|
|
|
|
|
|
|
|
|
|
GitLab comes in two flavors: [Community Edition][ce] which is MIT licensed,
|
|
|
|
|
and [Enterprise Edition][ee] 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][source-ee] - 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][omni-ce-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][ee-ce] to make the process as smooth as
|
|
|
|
|
possible.
|
2014-10-02 06:39:26 -04:00
|
|
|
|
|
|
|
|
## Miscellaneous
|
|
|
|
|
|
2016-04-19 12:12:12 -04:00
|
|
|
- [MySQL to PostgreSQL](mysql_to_postgresql.md) guides you through migrating
|
|
|
|
|
your database from MySQL to PostgreSQL.
|
2016-04-21 06:07:33 -04:00
|
|
|
- [MySQL installation guide](../install/database_mysql.md) contains additional
|
|
|
|
|
information about configuring GitLab to work with a MySQL database.
|
2016-03-08 17:52:48 -05:00
|
|
|
- [Restoring from backup after a failed upgrade](restore_after_failure.md)
|
2016-10-06 07:41:20 -04:00
|
|
|
- [Upgrading PostgreSQL Using Slony](upgrading_postgresql_using_slony.md), for
|
|
|
|
|
upgrading a PostgreSQL database with minimal downtime.
|
2016-04-21 06:07:33 -04:00
|
|
|
|
2016-05-13 17:17:01 -04:00
|
|
|
[omnidocker]: http://docs.gitlab.com/omnibus/docker/README.html
|
2016-04-21 06:07:33 -04:00
|
|
|
[source-ee]: https://gitlab.com/gitlab-org/gitlab-ee/tree/master/doc/update
|
|
|
|
|
[source-ce]: https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/update
|
|
|
|
|
[ee-ce]: ../downgrade_ee_to_ce/README.md
|
|
|
|
|
[ce]: https://about.gitlab.com/features/#community
|
|
|
|
|
[ee]: https://about.gitlab.com/features/#enterprise
|
2016-05-13 17:17:01 -04:00
|
|
|
[omni-ce-ee]: http://docs.gitlab.com/omnibus/update/README.html#from-community-edition-to-enterprise-edition
|
