debian-mirror-gitlab/doc/update/patch_versions.md

91 lines
2.5 KiB
Markdown
Raw Normal View History

2014-09-02 18:07:02 +05:30
# Universal update guide for patch versions
2015-04-26 12:48:37 +05:30
*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-09-02 18:07:02 +05:30
2015-09-25 12:07:36 +05:30
For example from 7.14.0 to 7.14.3, also see the [semantic versioning specification](http://semver.org/).
2014-09-02 18:07:02 +05:30
### 0. Backup
It's useful to make a backup just in case things go south:
2015-12-23 02:04:40 +05:30
(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab
user on the database version)
2014-09-02 18:07:02 +05:30
```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
```
### 1. Stop server
2015-12-23 02:04:40 +05:30
```bash
sudo service gitlab stop
```
2014-09-02 18:07:02 +05:30
### 2. Get latest code for the stable branch
2015-12-23 02:04:40 +05:30
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`).
2014-09-02 18:07:02 +05:30
```bash
cd /home/git/gitlab
sudo -u git -H git fetch --all
2015-09-11 14:41:01 +05:30
sudo -u git -H git checkout -- Gemfile.lock db/schema.rb
2015-10-24 18:46:33 +05:30
sudo -u git -H git checkout LATEST_TAG -b LATEST_TAG
2014-09-02 18:07:02 +05:30
```
2015-04-26 12:48:37 +05:30
### 3. Update gitlab-shell to the corresponding version
2014-09-02 18:07:02 +05:30
```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
2015-09-25 12:07:36 +05:30
sudo -u git -H git checkout v`cat /home/git/gitlab/GITLAB_SHELL_VERSION` -b v`cat /home/git/gitlab/GITLAB_SHELL_VERSION`
2014-09-02 18:07:02 +05:30
```
2015-12-23 02:04:40 +05:30
### 4. Update gitlab-workhorse to the corresponding version
```bash
cd /home/git/gitlab-workhorse
sudo -u git -H git fetch
sudo -u git -H git checkout `cat /home/git/gitlab/GITLAB_WORKHORSE_VERSION` -b `cat /home/git/gitlab/GITLAB_WORKHORSE_VERSION`
sudo -u git -H make
2015-12-23 02:04:40 +05:30
```
### 5. Install libs, migrations, etc.
2014-09-02 18:07:02 +05:30
```bash
cd /home/git/gitlab
2015-12-23 02:04:40 +05:30
# PostgreSQL
2014-09-02 18:07:02 +05:30
sudo -u git -H bundle install --without development test mysql --deployment
# MySQL
sudo -u git -H bundle install --without development test postgres --deployment
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
2015-11-26 14:37:03 +05:30
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
2014-09-02 18:07:02 +05:30
```
2015-12-23 02:04:40 +05:30
### 6. Start application
2014-09-02 18:07:02 +05:30
2015-12-23 02:04:40 +05:30
```bash
sudo service gitlab start
sudo service nginx restart
```
2014-09-02 18:07:02 +05:30
2015-12-23 02:04:40 +05:30
### 7. Check application status
2014-09-02 18:07:02 +05:30
Check if GitLab and its environment are configured correctly:
2015-12-23 02:04:40 +05:30
```bash
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
```
2014-09-02 18:07:02 +05:30
To make sure you didn't miss anything run a more thorough check with:
2015-12-23 02:04:40 +05:30
```bash
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
```
2014-09-02 18:07:02 +05:30
If all items are green, then congratulations upgrade complete!