BigW Consortium Gitlab

6.6-to-6.7.md 3.18 KB
Newer Older
1 2 3 4
---
comments: false
---

5
# From 6.6 to 6.7
6
*Make sure you view this [upgrade guide from the `master` branch](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/update/6.6-to-6.7.md) for the most up to date instructions.*
7

8
## 0. Backup
9 10 11 12 13 14

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

15
## 1. Stop server
16 17 18

    sudo service gitlab stop

19
## 2. Get latest code
20 21 22 23 24 25

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

26
For GitLab Community Edition:
27 28 29 30 31 32 33 34 35 36 37 38 39

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

40
## 3. Update gitlab-shell (and its config)
41 42 43 44

```bash
cd /home/git/gitlab-shell
sudo -u git -H git fetch
45
sudo -u git -H git checkout v1.9.1
46 47
```

48
## 4. Install libs, migrations, etc.
49 50 51 52

```bash
cd /home/git/gitlab

53 54 55 56 57 58
# 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)
59 60
sudo -u git -H bundle install --without development test postgres --deployment

61
# PostgreSQL
62

63 64 65 66 67
# 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
68

69
# Both MySQL and PostgreSQL
70 71 72 73 74 75 76 77
# 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
78 79 80

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

82 83 84 85
# 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

86
# Close access to gitlab-satellites for others
Michael Krane committed
87
sudo chmod u+rwx,g=rx,o-rwx /home/git/gitlab-satellites
88 89 90

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

93
## 5. Start application
94 95 96 97

    sudo service gitlab start
    sudo service nginx restart

98
## 6. Check application status
99 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 is complete!

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

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

114
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).
115 116

### 2. Restore from the backup
117 118 119 120 121

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

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