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=productionWe will continue supporting Ruby < 2.3 for the time being but we recommend you upgrade to Ruby 2.3 if you're running a source installation, as this is the same version that ships with our Omnibus package.
You can check which version you are running with ruby -v.
Download and compile Ruby:
mkdir /tmp/ruby && cd /tmp/ruby
curl --remote-name --progress https://cache.ruby-lang.org/pub/ruby/2.3/ruby-2.3.1.tar.gz
echo 'c39b4001f7acb4e334cb60a0f4df72d434bef711 ruby-2.3.1.tar.gz' | shasum --check - && tar xzf ruby-2.3.1.tar.gz
cd ruby-2.3.1
./configure --disable-install-rdoc
make
sudo make installInstall Bundler:
sudo gem install bundler --no-ri --no-rdocsudo -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-12-stableOR
For GitLab Enterprise Edition:
sudo -u git -H git checkout 8-12-stable-eecd /home/git/gitlab-shell
sudo -u git -H git fetch --all --tags
sudo -u git -H git checkout v3.6.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.8.2
sudo -u git -H makecd /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-11-stable:config/gitlab.yml.example origin/8-12-stable:config/gitlab.yml.exampleConfigure Git to generate packfile bitmaps (introduced in Git 2.0) on the GitLab server during git gc.
sudo -u git -H git config --global repack.writeBitmaps trueEnsure you're still up-to-date with the latest NGINX configuration changes:
# For HTTPS configurations
git diff origin/8-11-stable:lib/support/nginx/gitlab-ssl origin/8-12-stable:lib/support/nginx/gitlab-ssl
# For HTTP configurations
git diff origin/8-11-stable:lib/support/nginx/gitlab origin/8-12-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!
In 8.12 release we changed the index mapping and this is why the whole index should be removed and built from scratch. Also the Elasticsearch 2.3.* contains a bug that causes to fail all queries that use highlight feature and Parent Child relationship at once, so we recommend to use the version 2.4 and newer. After updating your Elasticsearch server, please re-create your index by using one of two ways listed below:
Re-create the index. The following command is acceptable for not very big GitLab instances (storage size no more than few gigabytes).
# Omnibus installations
sudo gitlab-rake gitlab:elastic:index
# Installations from source
bundle exec rake gitlab:elastic:indexFor very big GitLab instances you have to remove index first. Note: Consider disabling ES search feature (Admin > Settings) before removing the index, in order to allow your users to use regular search while you recreate the Elasticsearch index.
# Omnibus installations
sudo gitlab-rake gitlab:elastic:delete_indexes
sudo gitlab-rake gitlab:elastic:clear_index_status
# Installations from source
bundle exec rake gitlab:elastic:delete_indexes
bundle exec rake gitlab:elastic:clear_index_statusThen we recommend to follow Add GitLab's data to the Elasticsearch index.
Follow the upgrade guide from 8.10 to 8.11, 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.