Make sure you view this update guide from the tag (version) of GitLab you would like to install. In most cases this should be the highest numbered production tag (without rc in it). You can select the tag in the version dropdown at the top left corner of GitLab (below the menu bar).
If the highest number stable branch is unclear please check the GitLab Blog for installation guide links by version.
sudo service gitlab stopcd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=productionsudo -u git -H git fetch --all
sudo -u git -H git checkout -- db/schema.rb # local changes will be restored automaticallyFor GitLab Community Edition:
sudo -u git -H git checkout 8-10-stableOR
For GitLab Enterprise Edition:
sudo -u git -H git checkout 8-10-stable-eecd /home/git/gitlab-shell
sudo -u git -H git fetch --all --tags
sudo -u git -H git checkout v3.2.1Install and compile gitlab-workhorse. This requires Go 1.5 which should already be on your system from GitLab 8.1.
cd /home/git/gitlab-workhorse
sudo -u git -H git fetch --all
sudo -u git -H git checkout v0.7.8
sudo -u git -H makeIf you are using MySQL you need to grant the GitLab user the necessary permissions on the database:
# Login to MySQL
mysql -u root -p
# Grant the GitLab user the REFERENCES permission on the database
GRANT REFERENCES ON `gitlabhq_production`.* TO 'git'@'localhost';
# Quit the database session
mysql> \qcd /home/git/gitlab
# MySQL installations (note: the line below states '--without postgres')
sudo -u git -H bundle install --without postgres development test --deployment
# PostgreSQL installations (note: the line below states '--without mysql')
sudo -u git -H bundle install --without mysql development test --deployment
# Optional: clean up old gems
sudo -u git -H bundle clean
# 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=productiongitlab.ymlThere are new configuration options available for gitlab.yml. View them with the command below and apply them manually to your current gitlab.yml:
git diff origin/8-9-stable:config/gitlab.yml.example origin/8-10-stable:config/gitlab.yml.exampleDisable git gc --auto because GitLab runs git gc for us already.
sudo -u git -H git config --global gc.auto 0Ensure you're still up-to-date with the latest NGINX configuration changes:
# For HTTPS configurations
git diff origin/8-9-stable:lib/support/nginx/gitlab-ssl origin/8-10-stable:lib/support/nginx/gitlab-ssl
# For HTTP configurations
git diff origin/8-9-stable:lib/support/nginx/gitlab origin/8-10-stable:lib/support/nginx/gitlabIf you are using Apache instead of NGINX please see the updated Apache templates. Also note that because Apache does not support upstreams behind Unix sockets you will need to let gitlab-workhorse listen on a TCP port. You can do this via /etc/default/gitlab.
If you're installing from source and use SMTP to deliver mail, you will need to add the following line to config/initializers/smtp_settings.rb:
ActionMailer::Base.delivery_method = :smtpSee smtp_settings.rb.sample as an example.
Ensure you're still up-to-date with the latest init script changes:
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlabFor Ubuntu 16.04.1 LTS:
sudo systemctl daemon-reloadsudo 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:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=productionIf all items are green, then congratulations, the upgrade is complete!
Follow the upgrade guide from 8.8 to 8.9, 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.