BigW Consortium Gitlab

6.0-to-6.1.md 3.35 KB
Newer Older
1
# From 6.0 to 6.1
2
*Make sure you view this [upgrade guide from the `master` branch](../../../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 53 54 55 56 57 58 59 60 61

```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
sudo -u git -H bundle exec rake migrate_iids RAILS_ENV=production
62
sudo -u git -H bundle exec rake assets:clean RAILS_ENV=production
63
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
64
sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
65 66
```

67
## 5. Update config files
68

69 70
- 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.
71

72
## 6. Update Init script
73 74 75

```bash
sudo rm /etc/init.d/gitlab
76
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
77 78
```

79
## 7. Start application
80 81 82 83

    sudo service gitlab start
    sudo service nginx restart

84
## 8. Check application status
85 86 87

Check if GitLab and its environment are configured correctly:

88
    cd /home/git/gitlab
89 90 91 92 93 94 95 96 97 98 99
    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
100

101
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).
102 103 104 105 106

### 2. Restore from the backup:

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