4.3 KiB
From 6.0 to 6.7
In 6.1 we remove a lot of deprecated code.
You should update to 6.0 before installing 6.1 or higher so all the necessary conversions are run.
Deprecations
Global issue numbers
As of 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.
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 bundle exec rake gitlab:backup:create RAILS_ENV=production
1. Stop server
sudo service gitlab stop
2. Get latest code
cd /home/git/gitlab
sudo -u git -H git fetch --all
For Gitlab Community Edition:
sudo -u git -H git checkout 6-7-stable
OR
For GitLab Enterprise Edition:
sudo -u git -H git checkout 6-7-stable-ee
3. Install additional packages
# Add support for lograte for better log file handling
sudo apt-get install logrotate
4. Update gitlab-shell
cd /home/git/gitlab-shell
sudo -u git -H git fetch
sudo -u git -H git checkout v1.9.1 # Addresses multiple critical security vulnerabilities
5. Install libs, migrations, etc.
cd /home/git/gitlab
# MySQL installations (note: the line below states '--without ... postgres')
sudo -u git -H bundle install --without development test postgres --deployment
# PostgreSQL installations (note: the line below states '--without ... mysql')
sudo -u git -H bundle install --without development test mysql --deployment
# Run database migrations
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
# Enable internal issue IDs (introduced in GitLab 6.1)
sudo -u git -H bundle exec rake migrate_iids RAILS_ENV=production
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
# Close access to gitlab-satellites for others
sudo chmod u+rwx,g+rx,o-rwx /home/git/gitlab-satellites
6. Update config files
TIP: to see what changed in gitlab.yml.example in this release use next command:
git diff 6-0-stable:config/gitlab.yml.example 6-7-stable:config/gitlab.yml.example
- Make
/home/git/gitlab/config/gitlab.ymlsame as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-7-stable/config/gitlab.yml.example but with your settings. - Make
/home/git/gitlab/config/unicorn.rbsame as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-7-stable/config/unicorn.rb.example but with your settings. - Copy rack attack middleware config
sudo -u git -H cp config/initializers/rack_attack.rb.example config/initializers/rack_attack.rb
- Set up logrotate
sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab
7. Update Init script
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
8. Start application
sudo service gitlab start
sudo service nginx restart
9. Check application status
Check if GitLab and its environment are configured correctly:
cd /home/git/gitlab
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
Follow the upgrade guide from 5.4 to 6.0, except for the database migration
(The backup is already migrated to the previous version)
2. Restore from the backup:
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
Login issues after upgrade?
If running in https mode, be sure to read Can't Verify csrf token authenticity