cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=productionsudo service gitlab stopcd /home/git/gitlab
sudo -u git -H git fetch --allFor GitLab Community Edition:
sudo -u git -H git checkout 6-9-stableOR
For GitLab Enterprise Edition:
sudo -u git -H git checkout 6-9-stable-eecd /home/git/gitlab-shell
sudo -u git -H git fetch
sudo -u git -H git checkout v1.9.4cd /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
# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=productionThere are new configuration options available for gitlab.yml. View them with the command below and apply them to your current gitlab.yml if desired.
git diff 6-8-stable:config/gitlab.yml.example 6-9-stable:config/gitlab.yml.examplesudo service gitlab start
sudo service nginx restartCheck if GitLab and its environment are configured correctly:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=productionTo make sure you didn't miss anything run a more thorough check with:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=productionIf all items are green, then congratulations upgrade is complete!
Follow the upgrade guide from 6.7 to 6.8, except for the database migration
(The backup is already migrated to the previous version)
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=productionIf you have more than one backup *.tar file(s) please add BACKUP=timestamp_of_backup to the command above.