BigW Consortium Gitlab

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

4
## Warning
5

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

8 9 10
**In 6.1 we remove a lot of deprecated code.**

**You should update to 6.0 before installing 6.1 so all the necessary conversions are run.**
11

12
## Deprecations
13

14
### Global issue numbers
15

16
In 6.1 issue numbers are project specific. This means all issues are renumbered and get a new number in their URL. If you use an old issue number URL and the issue number does not exist yet you are redirected to the new one. This conversion does not trigger if the old number already exists for this project, this is unlikely but will happen with old issues and large projects.
17

18
## 0. Backup
19

20
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):
21 22 23

```bash
cd /home/git/gitlab
24
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
25 26
```

27
## 1. Stop server
28 29 30

    sudo service gitlab stop

31
## 2. Get latest code
32 33 34

```bash
cd /home/git/gitlab
35
sudo -u git -H git fetch --all
36
sudo -u git -H git checkout 6-1-stable
37
# For GitLab Enterprise Edition: sudo -u git -H git checkout 6-1-stable-ee
38 39
```

40
## 3. Update gitlab-shell
41 42 43 44

```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
45
sudo -u git -H git checkout v1.7.9
46 47
```

48
## 4. Install libs, migrations, etc.
49 50 51 52

```bash
cd /home/git/gitlab

53 54 55 56 57
# 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

58
# MySQL
59 60 61 62 63

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

66 67 68 69
# PostgreSQL

# Run a bundle install without deployment to generate the new Gemfile
sudo -u git -H bundle install --without development test mysql --no-deployment
70

71 72
# Install libs (with deployment this time)
sudo -u git -H bundle install --without development test mysql --deployment
73

74
# Both MySQL and PostgreSQL
75 76
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
sudo -u git -H bundle exec rake migrate_iids RAILS_ENV=production
77
sudo -u git -H bundle exec rake assets:clean RAILS_ENV=production
78
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
79
sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
80 81
```

82
## 5. Update config files
83

84 85
- Make `/home/git/gitlab/config/gitlab.yml` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-1-stable/config/gitlab.yml.example but with your settings.
- Make `/home/git/gitlab/config/unicorn.rb` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-1-stable/config/unicorn.rb.example but with your settings.
86

87
## 6. Update Init script
88 89 90

```bash
sudo rm /etc/init.d/gitlab
91
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
92 93
```

94
## 7. Start application
95 96 97 98

    sudo service gitlab start
    sudo service nginx restart

99
## 8. Check application status
100 101 102

Check if GitLab and its environment are configured correctly:

103
    cd /home/git/gitlab
104 105 106 107 108 109 110 111 112 113 114
    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 (6.0)

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

116
Follow the [upgrade guide from 5.4 to 6.0](5.4-to-6.0.md), except for the database migration (the backup is already migrated to the previous version).
117 118 119 120 121

### 2. Restore from the backup:

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