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