6.0-to-6.8.md 4.41 KB
Newer Older
1
# From 6.0 to 6.8
Jacob Vosmaer's avatar
Jacob Vosmaer committed
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

# In 6.1 we remove a lot of deprecated code.
# You should update to 6.0 before installing 6.1 or higher so all the necessary conversions are run.

### Deprecations

#### Global issue numbers

As of 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.

### 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)

```bash
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

```bash
cd /home/git/gitlab
30
sudo -u git -H git fetch --all
31 32 33 34 35
```

For Gitlab Community Edition:

```bash
36
sudo -u git -H git checkout 6-8-stable
37 38 39 40 41 42 43
```

OR

For GitLab Enterprise Edition:

```bash
44
sudo -u git -H git checkout 6-8-stable-ee
Jacob Vosmaer's avatar
Jacob Vosmaer committed
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59
```


### 3. Install additional packages

```bash
# Add support for lograte for better log file handling
sudo apt-get install logrotate
```

### 4. Update gitlab-shell

```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
Jacob Vosmaer's avatar
Jacob Vosmaer committed
60
sudo -u git -H git checkout v1.9.3 # Addresses multiple critical security vulnerabilities
Jacob Vosmaer's avatar
Jacob Vosmaer committed
61 62 63 64 65 66 67
```

### 5. Install libs, migrations, etc.

```bash
cd /home/git/gitlab

68
# MySQL installations (note: the line below states '--without ... postgres')
Jacob Vosmaer's avatar
Jacob Vosmaer committed
69 70
sudo -u git -H bundle install --without development test postgres --deployment

71
# PostgreSQL installations (note: the line below states '--without ... mysql')
Jacob Vosmaer's avatar
Jacob Vosmaer committed
72 73 74
sudo -u git -H bundle install --without development test mysql --deployment


75
# Run database migrations
Jacob Vosmaer's avatar
Jacob Vosmaer committed
76
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
77 78

# Enable internal issue IDs (introduced in GitLab 6.1)
Jacob Vosmaer's avatar
Jacob Vosmaer committed
79
sudo -u git -H bundle exec rake migrate_iids RAILS_ENV=production
80 81 82

# Clean up assets and cache
sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
83 84 85

# Close access to gitlab-satellites for others
sudo chmod u+rwx,g+rx,o-rwx /home/git/gitlab-satellites
Jacob Vosmaer's avatar
Jacob Vosmaer committed
86 87 88 89 90 91 92
```

### 6. Update config files

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

```
93
git diff 6-0-stable:config/gitlab.yml.example 6-8-stable:config/gitlab.yml.example
Jacob Vosmaer's avatar
Jacob Vosmaer committed
94 95
```

96 97 98
* Make `/home/git/gitlab/config/gitlab.yml` the same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-8-stable/config/gitlab.yml.example but with your settings.
* Make `/home/git/gitlab/config/unicorn.rb` the same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-8-stable/config/unicorn.rb.example but with your settings.
* Make `/etc/nginx/sites-available/nginx` the same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-8-stable/lib/support/nginx/gitlab but with your settings.
Jacob Vosmaer's avatar
Jacob Vosmaer committed
99 100 101 102 103
* Copy rack attack middleware config

```bash
sudo -u git -H cp config/initializers/rack_attack.rb.example config/initializers/rack_attack.rb
```
104

Jacob Vosmaer's avatar
Jacob Vosmaer committed
105 106 107 108 109 110 111 112 113
* Set up logrotate

```bash
sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab
```

### 7. Update Init script

```bash
114
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
Jacob Vosmaer's avatar
Jacob Vosmaer committed
115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146
```

### 8. Start application

    sudo service gitlab start
    sudo service nginx restart

### 9. Check application status

Check if GitLab and its environment are configured correctly:

    cd /home/git/gitlab
    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
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)

### 2. Restore from the backup:

```bash
cd /home/git/gitlab
sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
```
Franz-Robert's avatar
Franz-Robert committed
147 148 149

## Login issues after upgrade?
If running in https mode, be sure to read [Can't Verify csrf token authenticity](https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide#cant-verify-csrf-token-authenticitycant-get-past-login-pageredirected-to-login-page)