BigW Consortium Gitlab

5.1-to-5.4.md 3.3 KB
Newer Older
1
# From 5.1 to 5.4
2
*Make sure you view this [upgrade guide from the `master` branch](../../../master/doc/update/5.1-to-5.4.md) for the most up to date instructions.*
3

4 5
Also works starting from 5.2.

6
## 0. Backup
7

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

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

15
## 1. Stop server
16 17 18

    sudo service gitlab stop

19
## 2. Get latest code
20 21 22 23 24 25 26

```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
```

27
## 3. Update gitlab-shell
28 29 30 31

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

35
## 4. Install libs, migrations, etc.
36 37 38 39

```bash
cd /home/git/gitlab

40 41 42 43 44
# 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

45
# MySQL
46 47 48 49 50

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

53 54 55 56 57 58
# 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)
59 60
sudo -u git -H bundle install --without development test mysql --deployment

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

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

67
## 5. Update config files
68

69 70
- 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.
71

72
## 6. Update Init script
73 74 75 76 77 78 79

```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
```

80
## 7. Create uploads directory
81 82 83 84 85 86 87

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

88
## 8. Start application
89 90 91 92

    sudo service gitlab start
    sudo service nginx restart

93
## 9. Check application status
94 95 96 97 98 99 100 101 102 103 104 105 106 107

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
108

109
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).
110 111 112 113 114 115 116

### 2. Restore from the backup:

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