2017-11-01 15:56:40 +00:00
---
comments: false
---
2013-08-20 19:34:14 +00:00
# From 6.0 to 6.1
2017-02-06 14:46:58 +00:00
*Make sure you view this [upgrade guide from the `master` branch ](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/update/6.0-to-6.1.md ) for the most up to date instructions.*
2013-08-20 19:34:14 +00:00
2013-11-02 15:49:26 +00:00
## Warning
2014-04-24 22:48:22 +00:00
2014-03-24 14:17:43 +00:00
GitLab 6.1 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
2013-11-02 15:49:26 +00:00
2014-04-24 22:48:22 +00:00
**In 6.1 we remove a lot of deprecated code.**
**You should update to 6.0 before installing 6.1 so all the necessary conversions are run.**
2013-08-26 18:59:15 +00:00
2014-04-24 22:48:22 +00:00
## Deprecations
2013-08-26 18:59:15 +00:00
2014-04-24 22:48:22 +00:00
### Global issue numbers
2013-08-26 18:59:15 +00:00
2014-04-24 22:48:22 +00:00
In 6.1 issue numbers are project specific. This means all issues are renumbered and get a new number in their URL. If you use an old issue number URL and the issue number does not exist yet you are redirected to the new one. This conversion does not trigger if the old number already exists for this project, this is unlikely but will happen with old issues and large projects.
2013-08-21 09:04:33 +00:00
2014-04-24 22:48:22 +00:00
## 0. Backup
2013-08-20 19:34:14 +00:00
2014-04-24 22:48:22 +00:00
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):
2013-08-20 19:34:14 +00:00
```bash
cd /home/git/gitlab
2013-10-07 12:16:04 +00:00
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
2013-08-20 19:34:14 +00:00
```
2014-04-24 22:48:22 +00:00
## 1. Stop server
2013-08-20 19:34:14 +00:00
sudo service gitlab stop
2014-04-24 22:48:22 +00:00
## 2. Get latest code
2013-08-20 19:34:14 +00:00
```bash
cd /home/git/gitlab
2014-01-20 09:38:16 +00:00
sudo -u git -H git fetch --all
2013-08-20 19:34:14 +00:00
sudo -u git -H git checkout 6-1-stable
2014-01-20 09:38:16 +00:00
# For GitLab Enterprise Edition: sudo -u git -H git checkout 6-1-stable-ee
2013-08-20 19:34:14 +00:00
```
2014-04-24 22:48:22 +00:00
## 3. Update gitlab-shell
2013-08-20 19:34:14 +00:00
```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
2013-11-20 10:34:14 +00:00
sudo -u git -H git checkout v1.7.9
2013-08-20 19:34:14 +00:00
```
2014-04-24 22:48:22 +00:00
## 4. Install libs, migrations, etc.
2013-08-20 19:34:14 +00:00
```bash
cd /home/git/gitlab
2016-06-01 15:01:14 +00:00
# The Modernizr gem was yanked from RubyGems. It is required for GitLab >= 2.8.0
# Edit `Gemfile` and change `gem "modernizr", "2.5.3"` to
# `gem "modernizr-rails", "2.7.1"``
sudo -u git -H vim Gemfile
2013-08-20 19:34:14 +00:00
# MySQL
2016-06-01 15:01:14 +00:00
# Run a bundle install without deployment to generate the new Gemfile
sudo -u git -H bundle install --without development test postgres --no-deployment
# Install libs (with deployment this time)
2013-08-20 19:34:14 +00:00
sudo -u git -H bundle install --without development test postgres --deployment
2016-06-01 15:01:14 +00:00
# PostgreSQL
# Run a bundle install without deployment to generate the new Gemfile
sudo -u git -H bundle install --without development test mysql --no-deployment
2013-08-20 19:34:14 +00:00
2016-06-01 15:01:14 +00:00
# Install libs (with deployment this time)
sudo -u git -H bundle install --without development test mysql --deployment
2013-08-20 19:34:14 +00:00
2016-06-01 15:01:14 +00:00
# Both MySQL and PostgreSQL
2013-08-20 19:34:14 +00:00
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
sudo -u git -H bundle exec rake migrate_iids RAILS_ENV=production
2013-09-19 17:25:40 +00:00
sudo -u git -H bundle exec rake assets:clean RAILS_ENV=production
2013-08-20 19:34:14 +00:00
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
2013-09-10 10:42:53 +00:00
sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
2013-08-20 19:34:14 +00:00
```
2014-04-24 22:48:22 +00:00
## 5. Update config files
2013-08-20 19:34:14 +00:00
2019-01-24 06:52:33 +00:00
- Make `/home/git/gitlab/config/gitlab.yml` same as < https: // gitlab . com / gitlab-org / gitlab-ce / blob / 6-1-stable / config / gitlab . yml . example > but with your settings.
- Make `/home/git/gitlab/config/unicorn.rb` same as < https: // gitlab . com / gitlab-org / gitlab-ce / blob / 6-1-stable / config / unicorn . rb . example > but with your settings.
2013-08-20 19:34:14 +00:00
2014-04-24 22:48:22 +00:00
## 6. Update Init script
2013-08-20 19:34:14 +00:00
```bash
sudo rm /etc/init.d/gitlab
2014-02-13 20:14:20 +00:00
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
2013-08-20 19:34:14 +00:00
```
2014-04-24 22:48:22 +00:00
## 7. Start application
2013-08-20 19:34:14 +00:00
sudo service gitlab start
sudo service nginx restart
2014-04-24 22:48:22 +00:00
## 8. Check application status
2013-08-20 19:34:14 +00:00
Check if GitLab and its environment are configured correctly:
2013-09-23 18:09:29 +00:00
cd /home/git/gitlab
2013-08-20 19:34:14 +00:00
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.0)
### 1. Revert the code to the previous version
2014-04-24 22:48:22 +00:00
2014-08-21 15:25:14 +00:00
Follow the [upgrade guide from 5.4 to 6.0 ](5.4-to-6.0.md ), except for the database migration (the backup is already migrated to the previous version).
2013-08-20 19:34:14 +00:00
### 2. Restore from the backup:
```bash
cd /home/git/gitlab
2013-10-07 12:16:04 +00:00
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
2013-08-20 19:34:14 +00:00
```