BigW Consortium Gitlab

5.2-to-5.3.md 2.47 KB
Newer Older
1
# From 5.2 to 5.3
2
*Make sure you view this [upgrade guide from the `master` branch](../../../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 34 35 36 37 38 39 40

```bash
cd /home/git/gitlab

# MySQL
sudo -u git -H bundle install --without development test postgres --deployment

#PostgreSQL
sudo -u git -H bundle install --without development test mysql --deployment

sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
41 42

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

45
## 4. Update config files
46

47 48
- 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.
49

50
## 5. Update Init script
51 52 53

```bash
sudo rm /etc/init.d/gitlab
Ben Bodenmiller committed
54
sudo curl -L --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab
55 56 57
sudo chmod +x /etc/init.d/gitlab
```

58
## 6. Start application
59 60 61 62

    sudo service gitlab start
    sudo service nginx restart

63
## 7. Check application status
64 65 66 67 68 69 70 71 72 73 74 75 76 77

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
78

79
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).
80 81 82 83 84

### 2. Restore from the backup:

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