BigW Consortium Gitlab

5.2-to-5.3.md 3.12 KB
Newer Older
1
# From 5.2 to 5.3
2
*Make sure you view this [upgrade guide from the `master` branch](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/update/5.2-to-5.3.md) for the most up to date instructions.*
3

4
## Warning
5

6
GitLab 5.3 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
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 26 27 28

```bash
cd /home/git/gitlab
sudo -u git -H git fetch
sudo -u git -H git checkout 5-3-stable
```

29
## 3. Install libs, migrations, etc.
30 31 32 33

```bash
cd /home/git/gitlab

34 35 36 37 38
# 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

39
# MySQL
40 41 42 43 44

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

47 48 49 50 51 52
# 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)
53 54
sudo -u git -H bundle install --without development test mysql --deployment

55
# Both MySQL and PostgreSQL
56
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
57 58

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

61
## 4. Update config files
62

63 64
- Make `/home/git/gitlab/config/gitlab.yml` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/5-3-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-3-stable/config/puma.rb.example but with your settings.
65

66
## 5. Update Init script
67 68 69

```bash
sudo rm /etc/init.d/gitlab
70
sudo curl --location --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab
71 72 73
sudo chmod +x /etc/init.d/gitlab
```

74
## 6. Start application
75 76 77 78

    sudo service gitlab start
    sudo service nginx restart

79
## 7. Check application status
80 81 82 83 84 85 86 87 88 89 90 91 92 93

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.2)

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

95
Follow the [upgrade guide from 5.1 to 5.2](5.1-to-5.2.md), except for the database migration (the backup is already migrated to the previous version).
96 97 98 99 100

### 2. Restore from the backup:

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