Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
0ec0c938
Commit
0ec0c938
authored
Dec 02, 2015
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Also update gitlab-workhorse in patch updates [ci skip]
parent
09e712c0
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
32 additions
and
13 deletions
+32
-13
doc/update/patch_versions.md
doc/update/patch_versions.md
+32
-13
No files found.
doc/update/patch_versions.md
View file @
0ec0c938
...
@@ -6,7 +6,8 @@ For example from 7.14.0 to 7.14.3, also see the [semantic versioning specificati
...
@@ -6,7 +6,8 @@ For example from 7.14.0 to 7.14.3, also see the [semantic versioning specificati
### 0. Backup
### 0. Backup
It's useful to make a backup just in case things go south:
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)
(With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab
user on the database version)
```
bash
```
bash
cd
/home/git/gitlab
cd
/home/git/gitlab
...
@@ -15,19 +16,23 @@ sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
...
@@ -15,19 +16,23 @@ sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
### 1. Stop server
### 1. Stop server
sudo service gitlab stop
```
bash
sudo
service gitlab stop
```
### 2. Get latest code for the stable branch
### 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
```
bash
cd
/home/git/gitlab
cd
/home/git/gitlab
sudo
-u
git
-H
git fetch
--all
sudo
-u
git
-H
git fetch
--all
sudo
-u
git
-H
git checkout
--
Gemfile.lock db/schema.rb
sudo
-u
git
-H
git checkout
--
Gemfile.lock db/schema.rb
sudo
-u
git
-H
git checkout LATEST_TAG
-b
LATEST_TAG
sudo
-u
git
-H
git checkout LATEST_TAG
-b
LATEST_TAG
```
```
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`
)
### 3. Update gitlab-shell to the corresponding version
### 3. Update gitlab-shell to the corresponding version
...
@@ -37,12 +42,20 @@ sudo -u git -H git fetch
...
@@ -37,12 +42,20 @@ 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
`
sudo
-u
git
-H
git checkout v
`
cat
/home/git/gitlab/GITLAB_SHELL_VERSION
`
-b
v
`
cat
/home/git/gitlab/GITLAB_SHELL_VERSION
`
```
```
### 4. Install libs, migrations, etc.
### 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
`
```
### 5. Install libs, migrations, etc.
```
bash
```
bash
cd
/home/git/gitlab
cd
/home/git/gitlab
#PostgreSQL
#
PostgreSQL
sudo
-u
git
-H
bundle
install
--without
development
test
mysql
--deployment
sudo
-u
git
-H
bundle
install
--without
development
test
mysql
--deployment
# MySQL
# MySQL
...
@@ -52,19 +65,25 @@ sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
...
@@ -52,19 +65,25 @@ sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
sudo
-u
git
-H
bundle
exec
rake assets:clean assets:precompile cache:clear
RAILS_ENV
=
production
sudo
-u
git
-H
bundle
exec
rake assets:clean assets:precompile cache:clear
RAILS_ENV
=
production
```
```
###
5
. Start application
###
6
. Start application
sudo service gitlab start
```
bash
sudo service nginx restart
sudo
service gitlab start
sudo
service nginx restart
```
###
6
. Check application status
###
7
. Check application status
Check if GitLab and its environment are configured correctly:
Check if GitLab and its environment are configured correctly:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
```
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:
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
```
bash
sudo
-u
git
-H
bundle
exec
rake gitlab:check
RAILS_ENV
=
production
```
If all items are green, then congratulations upgrade complete!
If all items are green, then congratulations upgrade complete!
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment