Skip to content
Snippets Groups Projects
Commit 5453eb7d authored by Hannes Rosenögger's avatar Hannes Rosenögger
Browse files

Merge branch 'workhorse_in_patch_update' into 'master'

Also update gitlab-workhorse in patch updates [ci skip]

Fixes #3747 

See merge request !1959
parents cc525133 0ec0c938
No related branches found
No related tags found
No related merge requests found
Loading
Loading
@@ -6,7 +6,8 @@ For example from 7.14.0 to 7.14.3, also see the [semantic versioning specificati
### 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)
(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab
user on the database version)
 
```bash
cd /home/git/gitlab
Loading
Loading
@@ -15,19 +16,23 @@ sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
 
### 1. Stop server
 
sudo service gitlab stop
```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
```
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`)
 
### 3. Update gitlab-shell to the corresponding version
 
Loading
Loading
@@ -37,12 +42,20 @@ sudo -u git -H git fetch
sudo -u git -H git checkout v`cat /home/git/gitlab/GITLAB_SHELL_VERSION` -b v`cat /home/git/gitlab/GITLAB_SHELL_VERSION`
```
 
### 4. Install libs, migrations, etc.
### 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 v`cat /home/git/gitlab/GITLAB_WORKHORSE_VERSION` -b v`cat /home/git/gitlab/GITLAB_WORKHORSE_VERSION`
```
### 5. Install libs, migrations, etc.
 
```bash
cd /home/git/gitlab
 
#PostgreSQL
# PostgreSQL
sudo -u git -H bundle install --without development test mysql --deployment
 
# MySQL
Loading
Loading
@@ -52,19 +65,25 @@ sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
```
 
### 5. Start application
### 6. Start application
 
sudo service gitlab start
sudo service nginx restart
```bash
sudo service gitlab start
sudo service nginx restart
```
 
### 6. Check application status
### 7. Check application status
 
Check if GitLab and its environment are configured correctly:
 
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
```bash
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:
 
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
```bash
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
```
 
If all items are green, then congratulations upgrade complete!
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment