BigW Consortium Gitlab

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

4
## Warning
5

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

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

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
15
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
16 17
```

18
## 1. Stop server
19 20 21

    sudo service gitlab stop

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

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

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

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

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

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

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

48
# MySQL
49 50 51 52 53

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

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

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

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

70
## 5. Update config files
71

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

75
## 6. Update Init script
76 77

```bash
78
cd /home/git/gitlab
79
sudo rm /etc/init.d/gitlab
80
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab 
81 82 83
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

    sudo service gitlab start
95 96
    sudo service nginx restart

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

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

113
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).
114 115

### 2. Restore from the backup
116 117 118

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