Updating GitLab via omnibus-gitlab
Upgrading from a non-Omnibus installation to an Omnibus installation
Upgrading from non-Omnibus installations has not been tested by GitLab.com.
If you are using a MySQL database you have to configure a non-packaged MySQL database or convert to PostgreSQL before the backup.
Please be advised that you lose your settings in files such as gitlab.yml, unicorn.rb and smtp_settings.rb. You will have to configure those settings in /etc/gitlab/gitlab.rb. SMTP is not supported in omnibus-gitlab at this time.
Upgrade by creating a backup from the non-Omnibus install and restoring this in the Omnibus installation. Please ensure you are using exactly equal versions of GitLab (for example 6.7.3) when you do this. You might have to upgrade your non-Omnibus installation before creating the backup to archive this.
Updating from GitLab 6.6.x or higher to 6.8.x
First, download the latest CE or EE (subscribers only) package to your GitLab server.
# Stop unicorn and sidekiq so we can do database migrations
sudo gitlab-ctl stop unicorn
sudo gitlab-ctl stop sidekiq
# Create a database backup in case the upgrade fails
sudo gitlab-rake gitlab:backup:create
# Install the latest package
# Ubuntu:
sudo dpkg -i gitlab_6.7.y-omnibus.xxx.deb
# CentOS:
sudo rpm -Uvh gitlab-6.7.y_xxx.rpm
# Reconfigure GitLab (includes database migrations)
sudo gitlab-ctl reconfigure
# Start unicorn and sidekiq
sudo gitlab-ctl start
Done!
Updating from GitLab 6.6.0.pre1 to 6.6.4
First, download the latest package from https://www.gitlab.com/downloads/ to your GitLab server.
# Stop unicorn and sidekiq so we can do database migrations
sudo gitlab-ctl stop unicorn
sudo gitlab-ctl stop sidekiq
# One-time migration because we changed some directories since 6.6.0.pre1
sudo mkdir -p /var/opt/gitlab/git-data
sudo mv /var/opt/gitlab/{repositories,gitlab-satellites} /var/opt/gitlab/git-data/
sudo mv /var/opt/gitlab/uploads /var/opt/gitlab/gitlab-rails/
# Install the latest package
# Ubuntu:
sudo dpkg -i gitlab_6.6.4-omnibus.xxx.deb
# CentOS:
sudo rpm -Uvh gitlab-6.6.4_xxx.rpm
# Reconfigure GitLab (includes database migrations)
sudo gitlab-ctl reconfigure
# Start unicorn and sidekiq
sudo gitlab-ctl start
Done!
Reverting to GitLab 6.6.x
First download a GitLab 6.6.x CE or EE (subscribers only) package.
# Stop GitLab
sudo gitlab-ctl stop unicorn
sudo gitlab-ctl stop sidekiq
# Downgrade GitLab to 6.6
# Ubuntu
sudo dpkg -r gitlab
sudo dpkg -i gitlab-6.6.x-yyy.deb
# CentOS:
sudo rpm -e gitlab
sudo rpm -ivh gitlab-6.6.x-yyy.rpm
# Prepare GitLab for receiving the backup restore
# Due to a backup restore bug in GitLab 6.6, it is needed to drop the database
# _before_ running `gitlab-ctl reconfigure`.
sudo -u gitlab-psql /opt/gitlab/embedded/bin/dropdb gitlabhq_production
sudo gitlab-ctl reconfigure
# Restore your backup
sudo gitlab-rake gitlab:backup:restore BACKUP=12345 # where 12345 is your backup timestamp
# Start GitLab
sudo gitlab-ctl start