935c684ad3
This reverts commit66d8ef1ad9, reversing changes made to6a8359f3d3. The `--with` option was added in Bundler 1.10 but in this case it shouldn't even be needed: I've tested the original command locally and the pg gem was installed, so I believe the user that opened the original MR ran the wrong command (i.e. `sudo -u git -H bundle install --without development test postgres --deployment` instead of `sudo -u git -H bundle install --without development test mysql --deployment`. See discussion at66d8ef1ad9for more context.
96 lines
2.7 KiB
Markdown
96 lines
2.7 KiB
Markdown
# Universal update guide for patch versions
|
|
*Make sure you view this [upgrade guide](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/patch_versions.md) from the `master` branch for the most up to date instructions.*
|
|
|
|
For example from 7.14.0 to 7.14.3, also see the [semantic versioning specification](http://semver.org/).
|
|
|
|
### 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
|
|
|
|
```bash
|
|
sudo service gitlab stop
|
|
```
|
|
|
|
### 2. Get latest code for the stable branch
|
|
|
|
In the commands below, replace `LATEST_TAG` with the latest GitLab tag you want
|
|
to update to, for example `v8.0.3`. Use `git tag -l 'v*.[0-9]' --sort='v:refname'`
|
|
to see a list of all tags. Make sure to update patch versions only (check your
|
|
current version with `cat VERSION`).
|
|
|
|
```bash
|
|
cd /home/git/gitlab
|
|
sudo -u git -H git fetch --all
|
|
sudo -u git -H git checkout -- Gemfile.lock db/schema.rb
|
|
sudo -u git -H git checkout LATEST_TAG -b LATEST_TAG
|
|
```
|
|
|
|
### 3. Update gitlab-shell to the corresponding version
|
|
|
|
```bash
|
|
cd /home/git/gitlab-shell
|
|
sudo -u git -H git fetch
|
|
sudo -u git -H git checkout v`cat /home/git/gitlab/GITLAB_SHELL_VERSION` -b v`cat /home/git/gitlab/GITLAB_SHELL_VERSION`
|
|
```
|
|
|
|
### 4. Update gitlab-workhorse to the corresponding version
|
|
|
|
```bash
|
|
cd /home/git/gitlab-workhorse
|
|
sudo -u git -H git fetch
|
|
sudo -u git -H git checkout v`cat /home/git/gitlab/GITLAB_WORKHORSE_VERSION` -b v`cat /home/git/gitlab/GITLAB_WORKHORSE_VERSION`
|
|
sudo -u git -H make
|
|
```
|
|
|
|
### 5. Install libs, migrations, etc.
|
|
|
|
```bash
|
|
cd /home/git/gitlab
|
|
|
|
# PostgreSQL
|
|
sudo -u git -H bundle install --without development test mysql --deployment
|
|
|
|
# MySQL
|
|
sudo -u git -H bundle install --without development test postgres --deployment
|
|
|
|
# Optional: clean up old gems
|
|
sudo -u git -H bundle clean
|
|
|
|
# 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
|
|
```
|
|
|
|
### 6. Start application
|
|
|
|
```bash
|
|
sudo service gitlab start
|
|
sudo service nginx restart
|
|
```
|
|
|
|
### 7. Check application status
|
|
|
|
Check if GitLab and its environment are configured correctly:
|
|
|
|
```bash
|
|
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:
|
|
|
|
```bash
|
|
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
|
|
```
|
|
|
|
If all items are green, then congratulations upgrade complete!
|