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.

1. Stop server

sudo service gitlab stop

2. Backup

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

3. Get latest code

sudo -u git -H git fetch --all
sudo -u git -H git checkout -- db/schema.rb # local changes will be restored automatically

For GitLab Community Edition:

sudo -u git -H git checkout 8-8-stable

For GitLab Enterprise Edition:

sudo -u git -H git checkout 8-8-stable-ee

4. Update gitlab-shell

cd /home/git/gitlab-shell
sudo -u git -H git fetch --all --tags
sudo -u git -H git checkout v2.7.2

5. Update gitlab-workhorse

Install 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.1
sudo -u git -H make

6. Install libs, migrations, etc.

cd /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=production

7. Update configuration files

New configuration options for `gitlab.yml`

There 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-7-stable:config/gitlab.yml.example origin/8-8-stable:config/gitlab.yml.example

Git configuration

Disable git gc --auto because GitLab runs git gc for us already.

sudo -u git -H git config --global gc.auto 0

Nginx configuration

Ensure you're still up-to-date with the latest NGINX configuration changes:

# For HTTPS configurations
git diff origin/8-7-stable:lib/support/nginx/gitlab-ssl origin/8-8-stable:lib/support/nginx/gitlab-ssl

# For HTTP configurations
git diff origin/8-7-stable:lib/support/nginx/gitlab origin/8-8-stable:lib/support/nginx/gitlab

If 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.

Init script

Ensure you're still up-to-date with the latest init script changes:

sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab

For Ubuntu 16.04.1 LTS:

sudo systemctl daemon-reload

8. Start application

sudo service gitlab start
sudo service nginx restart

9. 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:

sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

If all items are green, then congratulations, the upgrade is complete!

10. Elasticsearch indexes update (if you currently use Elasticsearch)

When index mapping is changed the whole index should be removed and built from the scratch.

Delete old indexes:

# Omnibus installations
sudo gitlab-rake gitlab:elastic:delete_indexes

# Installations from source
bundle exec rake gitlab:elastic:delete_indexes

Clear repository index status:

# Omnibus installations
sudo gitlab-rake gitlab:elastic:clear_index_status

# Installations from source
bundle exec rake gitlab:elastic:clear_index_status

Create new, empty indexes:

# Omnibus installations
sudo gitlab-rake gitlab:elastic:create_empty_indexes

# Installations from source
bundle exec rake gitlab:elastic:create_empty_indexes

Fill newly created indexes. 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:index
```

If your instance is big we recommend to follow Add GitLab's data to the Elasticsearch index

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

If you have more than one backup *.tar file(s) please add BACKUP=timestamp_of_backup to the command above.

GitSwarm-EE 2017.2-1 Documentation

From 8.7 to 8.8