BigW Consortium Gitlab

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

4
## 0. Backup
5

6
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):
7 8 9

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

13
## 1. Stop server
14 15 16

    sudo service gitlab stop

17
## 2. Get latest code
18 19 20 21

```bash
cd /home/git/gitlab
sudo -u git -H git fetch
22
sudo -u git -H git checkout 5-4-stable # Latest version of 5-4-stable addresses CVE-2013-4489
23 24
```

25
## 3. Update gitlab-shell
26 27 28 29

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

33
## 4. Install libs, migrations, etc.
34 35 36 37

```bash
cd /home/git/gitlab

38 39 40 41 42
# 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

43
# MySQL
44 45 46 47 48

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

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

59
# Both MySQL and PostgreSQL
60
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
61 62

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

65
## 5. Update config files
66

67 68
- 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.
69

70
## 6. Update Init script
71 72 73

```bash
sudo rm /etc/init.d/gitlab
74
sudo curl --location --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-4-stable/lib/support/init.d/gitlab
75 76 77
sudo chmod +x /etc/init.d/gitlab
```

78
## 7. Start application
79 80 81 82

    sudo service gitlab start
    sudo service nginx restart

83
## 8. Check application status
84 85 86 87 88 89 90 91 92 93 94 95 96 97

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
98

99
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).
100 101 102 103 104

### 2. Restore from the backup:

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