BigW Consortium Gitlab

6.1-to-6.2.md 3.46 KB
Newer Older
1
# From 6.1 to 6.2
2
*Make sure you view this [upgrade guide from the `master` branch](../../../master/doc/update/6.1-to-6.2.md) for the most up to date instructions.*
3

4
**You should update to 6.1 before installing 6.2 so all the necessary conversions are run.**
5

6
## 0. Backup
7

8
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).
9 10 11

```bash
cd /home/git/gitlab
12
sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
13 14
```

15
## 1. Stop server
16 17 18

    sudo service gitlab stop

19
## 2. Get latest code
20 21 22

```bash
cd /home/git/gitlab
23
sudo -u git -H git fetch --all
24
sudo -u git -H git checkout 6-2-stable # Latest version of 6-2-stable addresses CVE-2013-4489
25
# For GitLab Enterprise Edition: sudo -u git -H git checkout 6-2-stable-ee
26 27
```

28
## 3. Update gitlab-shell
29 30 31 32

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

36
## 4. Install additional packages
37 38

```bash
39
# Add support for logrotate for better log file handling
40 41 42
sudo apt-get install logrotate
```

43
## 5. Install libs, migrations, etc.
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

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


sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
sudo -u git -H bundle exec rake assets:clean RAILS_ENV=production
sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production
```

61
## 6. Update config files
62

63
TIP: to see what changed in `gitlab.yml.example` in this release use next command: 
64 65 66 67 68

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

69
-   Make `/home/git/gitlab/config/gitlab.yml` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-2-stable/config/gitlab.yml.example but with your settings.
70

71 72 73 74 75 76 77 78 79 80 81
-   Make `/home/git/gitlab/config/unicorn.rb` same as https://gitlab.com/gitlab-org/gitlab-ce/blob/6-2-stable/config/unicorn.rb.example but with your settings.

-   Copy rack attack middleware config:

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

-   Uncomment `config.middleware.use Rack::Attack` in `/home/git/gitlab/config/application.rb`

-   Set up logrotate.
82

83 84 85
```bash
sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab
```
86

87
## 7. Update Init script
88 89 90

```bash
sudo rm /etc/init.d/gitlab
91
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
92 93
```

94
## 8. Start application
95 96 97 98

    sudo service gitlab start
    sudo service nginx restart

99
## 9. Check application status
100 101 102 103 104 105 106 107 108 109 110 111 112 113

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.1)

### 1. Revert the code to the previous version
114

115
Follow the [upgrade guide from 6.0 to 6.1](6.0-to-6.1.md), except for the database migration (the backup is already migrated to the previous version).
116 117 118 119 120

### 2. Restore from the backup:

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