BigW Consortium Gitlab

6.0-to-6.1.md 4.01 KB
Newer Older
1 2 3 4
---
comments: false
---

5
# From 6.0 to 6.1
6
*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.*
7

8
## Warning
9

10
GitLab 6.1 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
11

12 13 14
**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.**
15

16
## Deprecations
17

18
### Global issue numbers
19

20
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.
21

22
## 0. Backup
23

24
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):
25 26 27

```bash
cd /home/git/gitlab
28
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
29 30
```

31
## 1. Stop server
32 33 34

    sudo service gitlab stop

35
## 2. Get latest code
36 37 38

```bash
cd /home/git/gitlab
39
sudo -u git -H git fetch --all
40
sudo -u git -H git checkout 6-1-stable
41
# For GitLab Enterprise Edition: sudo -u git -H git checkout 6-1-stable-ee
42 43
```

44
## 3. Update gitlab-shell
45 46 47 48

```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
49
sudo -u git -H git checkout v1.7.9
50 51
```

52
## 4. Install libs, migrations, etc.
53 54 55 56

```bash
cd /home/git/gitlab

57 58 59 60 61
# 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

62
# MySQL
63 64 65 66 67

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

70 71 72 73
# PostgreSQL

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

75 76
# Install libs (with deployment this time)
sudo -u git -H bundle install --without development test mysql --deployment
77

78
# Both MySQL and PostgreSQL
79 80
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
sudo -u git -H bundle exec rake migrate_iids RAILS_ENV=production
81
sudo -u git -H bundle exec rake assets:clean RAILS_ENV=production
82
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
83
sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
84 85
```

86
## 5. Update config files
87

88 89
- 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.
90

91
## 6. Update Init script
92 93 94

```bash
sudo rm /etc/init.d/gitlab
95
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
96 97
```

98
## 7. Start application
99 100 101 102

    sudo service gitlab start
    sudo service nginx restart

103
## 8. Check application status
104 105 106

Check if GitLab and its environment are configured correctly:

107
    cd /home/git/gitlab
108 109 110 111 112 113 114 115 116 117 118
    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
119

120
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).
121 122 123 124 125

### 2. Restore from the backup:

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