5.4-to-6.0.md 4.52 KB
Newer Older
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
1 2
# From 5.4 to 6.0

3
## Warning
4
GitLab 6.0 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
5

Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
6 7 8 9
### Deprecations

#### Global projects

Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
10
The root (global) namespace for projects is deprecated.
John Weis's avatar
John Weis committed
11
So you need to move all your global projects under groups or users manually before update or they will be automatically moved to the project owner namespace during the update. When a project is moved all its members will receive an email with instructions how to update their git remote url. Please make sure you disable sending email when you do a test of the upgrade.
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
12 13 14

#### Teams

15
We introduce group membership in 6.0 as a replacement for teams.
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
16 17 18 19 20 21 22 23 24 25 26 27 28 29
The old combination of groups and teams was confusing for a lot of people.
And when the members of a team where changed this wasn't reflected in the project permissions.
In GitLab 6.0 you will be able to add members to a group with a permission level for each member.
These group members will have access to the projects in that group.
Any changes to group members will immediately be reflected in the project permissions.
You can even have multiple owners for a group, greatly simplifying administration.

### 0. Backup

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
30
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
31 32 33 34 35 36 37 38 39 40 41
```

### 1. Stop server

    sudo service gitlab stop

### 2. Get latest code

```bash
cd /home/git/gitlab
sudo -u git -H git fetch
lurdan's avatar
lurdan committed
42
sudo -u git -H git checkout 6-0-stable
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
43 44
```

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

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

### 4. Install additional packages
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
54 55 56 57 58 59

```bash
# For reStructuredText markup language support install required package:
sudo apt-get install python-docutils
```

60
### 5. Install libs, migrations, etc.
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
61 62 63 64 65 66 67

```bash
cd /home/git/gitlab

# MySQL
sudo -u git -H bundle install --without development test postgres --deployment

68
# PostgreSQL
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
69 70 71 72 73 74 75
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_groups RAILS_ENV=production
sudo -u git -H bundle exec rake migrate_global_projects RAILS_ENV=production
sudo -u git -H bundle exec rake migrate_keys RAILS_ENV=production
sudo -u git -H bundle exec rake migrate_inline_notes RAILS_ENV=production
76
sudo -u git -H bundle exec rake gitlab:satellites:create RAILS_ENV=production
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
77

78 79
# Clear redis cache
sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
80

81 82 83
# Clear and precompile assets
sudo -u git -H bundle exec rake assets:clean RAILS_ENV=production
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
84 85
```

86
### 6. Update config files
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
87

88 89
Note: We switched from Puma in GitLab 5.4 to unicorn in GitLab 6.0.

90 91
* Make `/home/git/gitlab/config/gitlab.yml` the same as https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/gitlab.yml.example but with your settings.
* Make `/home/git/gitlab/config/unicorn.rb` the same as https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/unicorn.rb.example but with your settings.
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
92

93
### 7. Update Init script
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
94 95 96

```bash
sudo rm /etc/init.d/gitlab
97
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
98 99 100
sudo chmod +x /etc/init.d/gitlab
```

101
### 8. Start application
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
102 103 104 105

    sudo service gitlab start
    sudo service nginx restart

106
### 9. Check application status
Sytse Sijbrandij's avatar
Sytse Sijbrandij committed
107 108 109 110 111 112 113 114 115 116

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!
117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134

### Troubleshooting
The migrations in this update are very sensitive to incomplete or inconsistent data. If you have a long-running GitLab installation and some of the previous upgrades did not work out 100% correct this may bite you now. The following commands can be run in the rails console to look for 'bad' data.

All project owners should have an owner
```
Project.all.select { |project| project.owner.blank? }
```

Every user should have a namespace
```
User.all.select { |u| u.namespace.blank? }
```

Projects in the global namespace should not conflict with projects in the owner namespace
```
Project.where(namespace_id: nil).select { |p| Project.where(path: p.path, namespace_id: p.owner.try(:namespace).try(:id)).present? }
```