2014-04-24 18:48:22 -04:00
# Universal update guide for patch versions
2016-12-02 06:36:05 -05:00
## 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).
2013-10-28 07:23:09 -04:00
### 0. Backup
It's useful to make a backup just in case things go south:
2015-12-02 08:54:44 -05:00
(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab
user on the database version)
2013-10-28 07:23:09 -04:00
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
### 1. Stop server
2015-12-02 08:54:44 -05:00
```bash
sudo service gitlab stop
```
2013-10-28 07:23:09 -04:00
2013-12-06 05:21:33 -05:00
### 2. Get latest code for the stable branch
2013-10-28 07:23:09 -04:00
2015-12-02 08:54:44 -05:00
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` ).
2013-10-28 07:23:09 -04:00
```bash
cd /home/git/gitlab
2014-02-24 07:04:05 -05:00
sudo -u git -H git fetch --all
2015-08-07 15:13:18 -04:00
sudo -u git -H git checkout -- Gemfile.lock db/schema.rb
2015-10-05 09:27:01 -04:00
sudo -u git -H git checkout LATEST_TAG -b LATEST_TAG
2013-10-28 07:23:09 -04:00
```
2014-10-28 13:57:30 -04:00
### 3. Update gitlab-shell to the corresponding version
2013-11-04 14:28:07 -05:00
```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
2015-09-14 02:54:38 -04:00
sudo -u git -H git checkout v`cat /home/git/gitlab/GITLAB_SHELL_VERSION` -b v`cat /home/git/gitlab/GITLAB_SHELL_VERSION`
2013-11-04 14:28:07 -05:00
```
2015-12-02 08:54:44 -05:00
### 4. Update gitlab-workhorse to the corresponding version
```bash
2016-12-01 10:24:35 -05:00
cd /home/git/gitlab
sudo -u git -H bundle exec rake "gitlab:workhorse:install[/home/git/gitlab-workhorse]" RAILS_ENV=production
2015-12-02 08:54:44 -05:00
```
### 5. Install libs, migrations, etc.
2013-10-28 07:23:09 -04:00
```bash
cd /home/git/gitlab
2015-12-02 08:54:44 -05:00
# PostgreSQL
2016-05-13 12:39:32 -04:00
sudo -u git -H bundle install --without development test mysql --deployment
2013-10-28 07:23:09 -04:00
2014-03-03 19:40:30 -05:00
# MySQL
2016-05-13 12:39:32 -04:00
sudo -u git -H bundle install --without development test postgres --deployment
2014-03-03 19:40:30 -05:00
2016-03-07 09:39:12 -05:00
# Optional: clean up old gems
2016-02-14 04:31:28 -05:00
sudo -u git -H bundle clean
2016-03-07 09:39:12 -05:00
# Run database migrations
2013-10-28 07:23:09 -04:00
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
2016-03-07 09:39:12 -05:00
# Clean up assets and cache
2015-10-19 17:10:17 -04:00
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
2013-10-28 07:23:09 -04:00
```
2015-12-02 08:54:44 -05:00
### 6. Start application
2013-10-28 07:23:09 -04:00
2015-12-02 08:54:44 -05:00
```bash
sudo service gitlab start
sudo service nginx restart
```
2013-10-28 07:23:09 -04:00
2015-12-02 08:54:44 -05:00
### 7. Check application status
2013-10-28 07:23:09 -04:00
Check if GitLab and its environment are configured correctly:
2015-12-02 08:54:44 -05:00
```bash
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
```
2013-10-28 07:23:09 -04:00
To make sure you didn't miss anything run a more thorough check with:
2015-12-02 08:54:44 -05:00
```bash
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
```
2013-10-28 07:23:09 -04:00
If all items are green, then congratulations upgrade complete!