5.1-to-5.4.md 3.37 KB
Newer Older
1 2 3 4
---
comments: false
---

5
# From 5.1 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.1-to-5.4.md) for the most up to date instructions.*
7

8 9
Also works starting from 5.2.

10
## 0. Backup
11

12
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):
13 14 15 16 17 18

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

19
## 1. Stop server
20 21 22

    sudo service gitlab stop

23
## 2. Get latest code
24 25 26 27 28 29 30

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

31
## 3. Update gitlab-shell
32 33 34 35

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

39
## 4. Install libs, migrations, etc.
40 41 42 43

```bash
cd /home/git/gitlab

44 45 46 47 48
# 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

49
# MySQL
50 51 52 53 54

# 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)
55 56
sudo -u git -H bundle install --without development test postgres --deployment

57 58 59 60 61 62
# 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)
63 64
sudo -u git -H bundle install --without development test mysql --deployment

65
# Both MySQL and PostgreSQL
66 67 68 69 70
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production

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

71
## 5. Update config files
72

73 74
- 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.
75

76
## 6. Update Init script
77 78 79 80 81 82 83

```bash
sudo rm /etc/init.d/gitlab
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
sudo chmod +x /etc/init.d/gitlab
```

84
## 7. Create uploads directory
85 86 87 88 89 90 91

```bash
cd /home/git/gitlab
sudo -u git -H mkdir public/uploads
sudo chmod -R u+rwX  public/uploads
```

92
## 8. Start application
93 94 95 96

    sudo service gitlab start
    sudo service nginx restart

97
## 9. Check application status
98 99 100 101 102 103 104 105 106 107 108 109 110 111

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
112

113
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).
114 115 116 117 118 119 120

### 2. Restore from the backup:

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