gitlab-org--gitlab-foss/doc/update/5.4-to-6.0.md

From 5.4 to 6.0

Deprecations

Global projects

We deprecated root(global) namespace for projects. So you need to move all your global projects under group/users manually before update or it will be moved automatically to owner namespace during update.

Teams

We drop teams support as separate entity for 6.0 in favor of group membership. So now you will be able to manage group members in order to provide access to corresponding projects.

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)

cd /home/git/gitlab
sudo -u git -H RAILS_ENV=production bundle exec rake gitlab:backup:create

1. Stop server

sudo service gitlab stop

2. Get latest code

cd /home/git/gitlab
sudo -u git -H git fetch
sudo -u git -H git checkout 6-0-dev

3. Install libs, migrations, etc.

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_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

4. Update config files

• Make /home/git/gitlab/config/gitlab.yml same as https://github.com/gitlabhq/gitlabhq/blob/5-3-stable/config/gitlab.yml.example but with your settings.
• Make /home/git/gitlab/config/puma.rb same as https://github.com/gitlabhq/gitlabhq/blob/5-3-stable/config/puma.rb.example but with your settings.

5. Update Init script

sudo rm /etc/init.d/gitlab
sudo curl --output /etc/init.d/gitlab https://raw.github.com/gitlabhq/gitlabhq/5-3-stable/lib/support/init.d/gitlab
sudo chmod +x /etc/init.d/gitlab

6. Start application

sudo service gitlab start
sudo service nginx restart

7. Check application status

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!