BigW Consortium Gitlab

5.1-to-5.2.md 2.54 KB
Newer Older
1 2
# From 5.1 to 5.2

3
## Warning
4

5
GitLab 5.2 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
6

7
## 0. Backup
8 9 10 11 12 13

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)

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

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

```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
sudo -u git -H git checkout v1.4.0
```

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

```bash
cd /home/git/gitlab
41 42

# MySQL
43
sudo -u git -H bundle install --without development test postgres --deployment
44 45 46 47

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

48
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
49 50

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

53
## 5. Update config files
54

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

58
## 6. Update Init script
59 60

```bash
61
cd /home/git/gitlab
62
sudo rm /etc/init.d/gitlab
63
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab 
64 65 66
sudo chmod +x /etc/init.d/gitlab
```

67
## 7. Create uploads directory
68 69 70 71 72 73 74

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

75
## 8. Start application
76 77

    sudo service gitlab start
78 79
    sudo service nginx restart

80
## 9. Check application status
81 82 83 84 85 86 87 88 89 90 91 92 93 94 95

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

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

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

### 2. Restore from the backup
99 100 101

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