2018-03-17 18:26:18 +05:30
---
comments: false
---
2014-09-02 18:07:02 +05:30
# From 4.1 to 4.2
2017-08-17 22:00:37 +05:30
*Make sure you view this [upgrade guide from the `master` branch ](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/update/4.1-to-4.2.md ) for the most up to date instructions.*
2014-09-02 18:07:02 +05:30
## 1. Stop server & Resque
sudo service gitlab stop
## 2. Update code & DB
```bash
#Set the working directory
cd /home/gitlab/gitlab/
# Get latest code
sudo -u gitlab -H git fetch
sudo -u gitlab -H git checkout 4-2-stable
2016-08-24 12:49:21 +05:30
# The Modernizr gem was yanked from RubyGems. It is required for GitLab >= 2.8.0
# Edit `Gemfile` and change `gem "modernizr", "2.5.3"` to
# `gem "modernizr-rails", "2.7.1"``
sudo -u gitlab -H vim Gemfile
# Run a bundle install without deployment to generate the new Gemfile
sudo -u gitlab -H bundle install --without development test postgres --no-deployment
# Install libs (with deployment this time)
2014-09-02 18:07:02 +05:30
sudo -u gitlab -H bundle install --without development test postgres --deployment
# update db
sudo -u gitlab -H bundle exec rake db:migrate RAILS_ENV=production
```
## 3. Check GitLab's status
```bash
sudo -u gitlab -H bundle exec rake gitlab:check RAILS_ENV=production
```
## 4. Start all
sudo service gitlab start