BigW Consortium Gitlab

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

4
## 0. Backup
5 6 7 8 9 10

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

11
## 1. Stop server
12 13 14

    sudo service gitlab stop

15
## 2. Get latest code
16 17 18 19 20 21

```bash
cd /home/git/gitlab
sudo -u git -H git fetch --all
```

22
For GitLab Community Edition:
23 24 25 26 27 28 29 30 31 32 33 34 35

```bash
sudo -u git -H git checkout 6-7-stable
```

OR

For GitLab Enterprise Edition:

```bash
sudo -u git -H git checkout 6-7-stable-ee
```

36
## 3. Update gitlab-shell (and its config)
37 38 39 40

```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
41
sudo -u git -H git checkout v1.9.1
42 43
```

44
## 4. Install libs, migrations, etc.
45 46 47 48

```bash
cd /home/git/gitlab

49 50 51 52 53 54
# MySQL

# 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)
55 56
sudo -u git -H bundle install --without development test postgres --deployment

57
# PostgreSQL
58

59 60 61 62 63
# Run a bundle install without deployment to generate the new Gemfile
sudo -u git -H bundle install --without development test mysql --no-deployment

# Install libs (with deployment this time)
sudo -u git -H bundle install --without development test mysql --deployment
64

65
# Both MySQL and PostgreSQL
66 67 68 69 70 71 72 73
# 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

# Update init.d script
sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
74 75 76

# Update the logrotate configuration (keep logs for 90 days instead of 52 weeks)
sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab
77

78 79 80 81
# Compress existing .log.1 files because we turned off delaycompress in logrotate
sudo -u git -H gzip /home/git/gitlab/log/*.log.1
sudo -u git -H gzip /home/git/gitlab-shell/gitlab-shell.log.1

82
# Close access to gitlab-satellites for others
Michael Krane committed
83
sudo chmod u+rwx,g=rx,o-rwx /home/git/gitlab-satellites
84 85 86

# Add directory for uploads
sudo -u git -H mkdir -p /home/git/gitlab/public/uploads
87 88
```

89
## 5. Start application
90 91 92 93

    sudo service gitlab start
    sudo service nginx restart

94
## 6. Check application status
95 96 97 98 99 100 101 102 103 104 105 106 107 108 109

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 is complete!

## Things went south? Revert to previous version (6.6)

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

110
Follow the [upgrade guide from 6.5 to 6.6](6.5-to-6.6.md), except for the database migration (the backup is already migrated to the previous version).
111 112

### 2. Restore from the backup
113 114 115 116 117

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

119
If you have more than one backup *.tar file(s) please add `BACKUP=timestamp_of_backup` to the command above.