kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/update/upgrading_from_ce_to_ee.md

136 lines
3.8 KiB
Markdown
Raw Normal View History

Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
---
comments: false
---
# Upgrading from Community Edition to Enterprise Edition from source
NOTE: **NOTE** In the past we used separate documents for upgrading from
Community Edition to Enterprise Edition. These documents can be found in the
[`doc/update` directory of Enterprise Edition's source
code][old-ee-upgrade-docs].
Docs: Merge EE doc/​update to CE
2019-05-05 08:17:20 -04:00
If you want to upgrade the version only, for example 11.8 to 11.9, *without* changing the
GitLab edition you are using (Community or Enterprise), see the
[Upgrading from source](upgrading_from_source.md) documentation.
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
## General upgrading steps
This guide assumes you have a correctly configured and tested installation of
GitLab Community Edition. If you run into any trouble or if you have any
questions please contact us at [support@gitlab.com].
In all examples, replace `EE_BRANCH` with the Enterprise Edition branch for the
version you are using, and `CE_BRANCH` with the Community Edition branch.
Branch names use the format `major-minor-stable-ee` for Enterprise Edition, and
`major-minor-stable` for Community Edition. For example, for 11.8.0 you would
use the following branches:
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
- Enterprise Edition: `11-8-stable-ee`
- Community Edition: `11-8-stable`
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
### 0. Backup
Make a backup just in case something goes wrong:
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
```sh
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
For installations using MySQL, this may require granting "LOCK TABLES"
privileges to the GitLab user on the database version.
### 1. Stop server
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
```sh
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
sudo service gitlab stop
```
### 2. Get the EE code
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
```sh
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
cd /home/git/gitlab
sudo -u git -H git remote add -f ee https://gitlab.com/gitlab-org/gitlab-ee.git
sudo -u git -H git checkout EE_BRANCH
```
Update docs to pass new markdownlint Deletes extra spaces and line, makes lists consistent, and fixes links.
2019-08-22 04:50:31 -04:00
### 3. Install libs, migrations, etc
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
```sh
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
Changing badges to use parentheses not brackets Previously, we used brackets to denote the tier badges, but this made Kramdown, the docs site Markdown renderer, show many warnings when building the site. This is now fixed by using parentheses instead of square brackets. This was caused by [PREMIUM] looking like a link to Kramdown, which couldn't find a URL there. See: - https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484 - https://gitlab.com/gitlab-org/gitlab-ce/issues/63800
2019-07-08 04:50:38 -04:00
### 4. Install `gitlab-elasticsearch-indexer` (optional) **(STARTER ONLY)**
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
If you're interested in using GitLab's new [elasticsearch repository
Docs: Convert links in various docs to relative
2019-05-31 07:29:58 -04:00
indexer](../integration/elasticsearch.md) (currently in beta) please follow the instructions on the
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
document linked above and enable the indexer usage in the GitLab admin settings.
### 5. Start application
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
```sh
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
sudo service gitlab start
sudo service nginx restart
```
### 6. Check application status
Check if GitLab and its environment are configured correctly:
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
```sh
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
```
To make sure you didn't miss anything run a more thorough check with:
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
```sh
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
```
If all items are green, then congratulations upgrade complete!
## Things went south? Revert to previous version (Community Edition)
### 1. Revert the code to the previous version
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
```sh
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
cd /home/git/gitlab
sudo -u git -H git checkout CE_BRANCH
```
### 2. Restore from the backup
Enforce consistent prefix for bullet lists Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
2019-06-30 23:36:23 -04:00
```sh
Use a single document for upgrading from CE to EE This changes the guides for upgrading from CE source to EE source so we no longer need separate documents for every version. This removes the need for release managers to create and update these documents, and allows developers to add these instructions as part of their code changes.
2019-02-11 11:08:25 -05:00
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
## Version specific steps
Certain versions of GitLab may require you to perform additional steps when
upgrading from Community Edition to Enterprise Edition. Should such steps be
necessary, they will listed per version below.
<!--
Example:
### 11.8.0
Additional instructions here.
-->
[support@gitlab.com]: mailto:support@gitlab.com
[old-ee-upgrade-docs]: https://gitlab.com/gitlab-org/gitlab-ee/tree/11-8-stable-ee/doc/update
Copy permalink