5.3-to-5.4.md 3.27 KB
Newer Older
1 2 3 4
---
comments: false
---

5
# From 5.3 to 5.4
6
*Make sure you view this [upgrade guide from the `master` branch](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/update/5.3-to-5.4.md) for the most up to date instructions.*
7

8
## 0. Backup
9

10
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):
11 12 13

```bash
cd /home/git/gitlab
14
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
15 16
```

17
## 1. Stop server
18 19 20

    sudo service gitlab stop

21
## 2. Get latest code
22 23 24 25

```bash
cd /home/git/gitlab
sudo -u git -H git fetch
26
sudo -u git -H git checkout 5-4-stable # Latest version of 5-4-stable addresses CVE-2013-4489
27 28
```

29
## 3. Update gitlab-shell
30 31 32 33

```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
34
sudo -u git -H git checkout v1.7.9 # Addresses multiple critical security vulnerabilities
35 36
```

37
## 4. Install libs, migrations, etc.
38 39 40 41

```bash
cd /home/git/gitlab

42 43 44 45 46
# The Modernizr gem was yanked from RubyGems. It is required for GitLab >= 2.8.0
# Edit `Gemfile` and change `gem "modernizr", "2.5.3"` to
# `gem "modernizr-rails", "2.7.1"``
sudo -u git -H vim Gemfile

47
# MySQL
48 49 50 51 52

# Run a bundle install without deployment to generate the new Gemfile
sudo -u git -H bundle install --without development test postgres --no-deployment

# Install libs (with deployment this time)
53 54
sudo -u git -H bundle install --without development test postgres --deployment

55 56 57 58 59 60
# PostgreSQL

# Run a bundle install without deployment to generate the new Gemfile
sudo -u git -H bundle install --without development test mysql --no-deployment

# Install libs (with deployment this time)
61 62
sudo -u git -H bundle install --without development test mysql --deployment

63
# Both MySQL and PostgreSQL
64
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
65 66

sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
67 68
```

69
## 5. Update config files
70

71 72
- Make `/home/git/gitlab/config/gitlab.yml` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/5-4-stable/config/gitlab.yml.example but with your settings.
- Make `/home/git/gitlab/config/puma.rb` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/5-4-stable/config/puma.rb.example but with your settings.
73

74
## 6. Update Init script
75 76 77

```bash
sudo rm /etc/init.d/gitlab
78
sudo curl --location --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-4-stable/lib/support/init.d/gitlab
79 80 81
sudo chmod +x /etc/init.d/gitlab
```

82
## 7. Start application
83 84 85 86

    sudo service gitlab start
    sudo service nginx restart

87
## 8. Check application status
88 89 90 91 92 93 94 95 96 97 98 99 100 101

Check if GitLab and its environment are configured correctly:

    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

If all items are green, then congratulations upgrade complete!

## Things went south? Revert to previous version (5.3)

### 1. Revert the code to the previous version
102

103
Follow the [upgrade guide from 5.2 to 5.3](5.2-to-5.3.md), except for the database migration (the backup is already migrated to the previous version).
104 105 106 107 108

### 2. Restore from the backup:

```bash
cd /home/git/gitlab
109
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
110
```