104 lines
2.8 KiB
Markdown
104 lines
2.8 KiB
Markdown
# Universal update guide for patch versions
|
|
|
|
## Select Version to Install
|
|
|
|
Make sure you view [this update guide](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/patch_versions.md) from the tag (version) of GitLab you would like to install.
|
|
In most cases this should be the highest numbered production tag (without rc in it).
|
|
You can select the tag in the version dropdown in the top left corner of GitLab (below the menu bar).
|
|
|
|
### 0. Backup
|
|
|
|
It's useful to make a backup just in case things go south:
|
|
(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab
|
|
user on the database version)
|
|
|
|
```bash
|
|
cd /home/git/gitlab
|
|
|
|
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
|
|
```
|
|
|
|
### 1. Stop server
|
|
|
|
```bash
|
|
sudo service gitlab stop
|
|
```
|
|
|
|
### 2. Get latest code for the stable branch
|
|
|
|
In the commands below, replace `LATEST_TAG` with the latest GitLab tag you want
|
|
to update to, for example `v8.0.3`. Use `git tag -l 'v*.[0-9]' --sort='v:refname'`
|
|
to see a list of all tags. Make sure to update patch versions only (check your
|
|
current version with `cat VERSION`).
|
|
|
|
```bash
|
|
cd /home/git/gitlab
|
|
|
|
sudo -u git -H git fetch --all
|
|
sudo -u git -H git checkout -- Gemfile.lock db/schema.rb
|
|
sudo -u git -H git checkout LATEST_TAG -b LATEST_TAG
|
|
```
|
|
|
|
### 3. Install libs, migrations, etc.
|
|
|
|
```bash
|
|
cd /home/git/gitlab
|
|
|
|
# PostgreSQL
|
|
sudo -u git -H bundle install --without development test mysql --deployment
|
|
|
|
# MySQL
|
|
sudo -u git -H bundle install --without development test postgres --deployment
|
|
|
|
# Optional: clean up old gems
|
|
sudo -u git -H bundle clean
|
|
|
|
# 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 yarn:install gitlab:assets:clean gitlab:assets:compile cache:clear RAILS_ENV=production NODE_ENV=production
|
|
```
|
|
|
|
### 4. Update gitlab-workhorse to the corresponding version
|
|
|
|
```bash
|
|
cd /home/git/gitlab
|
|
|
|
sudo -u git -H bundle exec rake "gitlab:workhorse:install[/home/git/gitlab-workhorse]" RAILS_ENV=production
|
|
```
|
|
|
|
### 5. Update gitlab-shell to the corresponding version
|
|
|
|
```bash
|
|
cd /home/git/gitlab-shell
|
|
|
|
sudo -u git -H git fetch --all --tags
|
|
sudo -u git -H git checkout v`cat /home/git/gitlab/GITLAB_SHELL_VERSION` -b v`cat /home/git/gitlab/GITLAB_SHELL_VERSION`
|
|
sudo -u git -H sh -c 'if [ -x bin/compile ]; then bin/compile; fi'
|
|
```
|
|
|
|
### 6. Start application
|
|
|
|
```bash
|
|
sudo service gitlab start
|
|
sudo service nginx restart
|
|
```
|
|
|
|
### 7. Check application status
|
|
|
|
Check if GitLab and its environment are configured correctly:
|
|
|
|
```bash
|
|
cd /home/git/gitlab
|
|
|
|
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:
|
|
|
|
```bash
|
|
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
|
|
```
|
|
|
|
If all items are green, then congratulations upgrade complete!
|