6.2-to-6.3.md 2.85 KB
Edit Raw Blame History


From 6.2 to 6.3
Requires version: 6.1 or 6.2
0. Backup
It's useful to make a backup just in case things go south:
(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version)


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

  
1. Stop server

  
    sudo service gitlab stop

  
2. Get latest code

  
    cd /home/git/gitlab
sudo -u git -H git fetch
sudo -u git -H git checkout 6-3-stable

  
3. Update gitlab-shell (and its config)

  
    cd /home/git/gitlab-shell
sudo -u git -H git fetch
sudo -u git -H git checkout v1.7.9 # Addresses multiple critical security vulnerabilities

  
The Gitlab-shell config changed recently, so check for config file changes and make /home/git/gitlab-shell/config.yml the same as https://github.com/gitlabhq/gitlab-shell/blob/master/config.yml.example
4. Install libs, migrations, etc.

  
    cd /home/git/gitlab

# MySQL
sudo -u git -H bundle install --without development test postgres --deployment

# PostgreSQL
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=production

  
5. Update config files
TIP: to see what changed in gitlab.yml.example in this release use next command: 


    git diff 6-2-stable:config/gitlab.yml.example 6-3-stable:config/gitlab.yml.example

  
Make /home/git/gitlab/config/gitlab.yml same as https://github.com/gitlabhq/gitlabhq/blob/6-3-stable/config/gitlab.yml.example but with your settings.
Make /home/git/gitlab/config/unicorn.rb same as https://github.com/gitlabhq/gitlabhq/blob/6-3-stable/config/unicorn.rb.example but with your settings.
Copy rack attack middleware config

6. Update Init script

  
    sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
sudo chmod +x /etc/init.d/gitlab

  
7. Start application

  
    sudo service gitlab start
sudo service nginx restart

  
8. 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 with:


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

  
If all items are green, then congratulations upgrade complete!
Things went south? Revert to previous version (6.2)
1. Revert the code to the previous version
Follow the <code>upgrade guide from 6.1 to 6.2</code>, except for the database migration 
(The backup is already migrated to the previous version)
2. Restore from the backup:

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