PageRenderTime 49ms CodeModel.GetById 19ms RepoModel.GetById 0ms app.codeStats 0ms

/doc/update/6.x-or-7.x-to-7.14.md

https://gitlab.com/Hubbitus/gitlab-ee
Markdown | 312 lines | 210 code | 102 blank | 0 comment | 0 complexity | 10c9300b6ee994130890d146164a2ce7 MD5 | raw file
  1. # From 6.x or 7.x to 7.14
  2. *Make sure you view this [upgrade guide from the `master` branch](../../../master/doc/update/6.x-or-7.x-to-7.14.md) for the most up to date instructions.*
  3. This allows you to upgrade any version of GitLab from 6.0 and up (including 7.0 and up) to 7.14.
  4. ## Global issue numbers
  5. As of 6.1 issue numbers are project specific. This means all issues are renumbered and get a new number in their URL. If you use an old issue number URL and the issue number does not exist yet you are redirected to the new one. This conversion does not trigger if the old number already exists for this project, this is unlikely but will happen with old issues and large projects.
  6. ## Editable labels
  7. In GitLab 7.2 we replace Issue and Merge Request tags with labels, making it
  8. possible to edit the label text and color. The characters `?`, `&` and `,` are
  9. no longer allowed however so those will be removed from your tags during the
  10. database migrations for GitLab 7.2.
  11. ## Stash changes
  12. If you [deleted the vendors folder during your original installation](https://github.com/gitlabhq/gitlabhq/issues/4883#issuecomment-31108431), [you will get an error](https://gitlab.com/gitlab-org/gitlab-ce/issues/1494) when you attempt to rebuild the assets in step 7. To avoid this, stash the changes in your GitLab working copy before starting:
  13. git stash
  14. ## 0. Stop server
  15. sudo service gitlab stop
  16. ## 1. Backup
  17. It's useful to make a backup just in case things go south:
  18. (With MySQL, this may require granting "LOCK TABLES" privileges to the GitLab user on the database version)
  19. ```bash
  20. cd /home/git/gitlab
  21. sudo -u git -H bundle exec rake gitlab:backup:create RAILS_ENV=production
  22. ```
  23. ## 2. Update Ruby
  24. If you are still using Ruby 1.9.3 or below, you will need to update Ruby.
  25. You can check which version you are running with `ruby -v`.
  26. If you are you running Ruby 2.0.x, you do not need to upgrade ruby, but can consider doing so for performance reasons.
  27. If you are running Ruby 2.1.1 consider upgrading to 2.1.6, because of the high memory usage of Ruby 2.1.1.
  28. Install, update dependencies:
  29. ```bash
  30. sudo apt-get install build-essential zlib1g-dev libyaml-dev libssl-dev libgdbm-dev libreadline-dev libncurses5-dev libffi-dev curl
  31. ```
  32. Download and compile Ruby:
  33. ```bash
  34. mkdir /tmp/ruby && cd /tmp/ruby
  35. curl --progress https://cache.ruby-lang.org/pub/ruby/2.1/ruby-2.1.6.tar.gz | tar xz
  36. cd ruby-2.1.6
  37. ./configure --disable-install-rdoc
  38. make
  39. sudo make install
  40. ```
  41. Install Bundler:
  42. ```bash
  43. sudo gem install bundler --no-ri --no-rdoc
  44. ```
  45. ## 3. Get latest code
  46. ```bash
  47. cd /home/git/gitlab
  48. sudo -u git -H git fetch --all
  49. sudo -u git -H git checkout -- db/schema.rb # local changes will be restored automatically
  50. ```
  51. For GitLab Community Edition:
  52. ```bash
  53. sudo -u git -H git checkout 7-14-stable
  54. ```
  55. OR
  56. For GitLab Enterprise Edition:
  57. ```bash
  58. sudo -u git -H git checkout 7-14-stable-ee
  59. ```
  60. ## 4. Install additional packages
  61. ```bash
  62. # Add support for logrotate for better log file handling
  63. sudo apt-get install logrotate
  64. # Install pkg-config and cmake, which is needed for the latest versions of rugged
  65. sudo apt-get install pkg-config cmake
  66. # If you want to use Kerberos with GitLab EE for user authentication, install Kerberos header files
  67. # If you don't know what Kerberos is, you can assume you don't need it.
  68. sudo apt-get install libkrb5-dev
  69. # Install nodejs, javascript runtime required for assets
  70. sudo apt-get install nodejs
  71. ```
  72. ## 5. Configure Redis to use sockets
  73. # Configure redis to use sockets
  74. sudo cp /etc/redis/redis.conf /etc/redis/redis.conf.orig
  75. # Disable Redis listening on TCP by setting 'port' to 0
  76. sed 's/^port .*/port 0/' /etc/redis/redis.conf.orig | sudo tee /etc/redis/redis.conf
  77. # Enable Redis socket for default Debian / Ubuntu path
  78. echo 'unixsocket /var/run/redis/redis.sock' | sudo tee -a /etc/redis/redis.conf
  79. # Be sure redis group can write to the socket, enable only if supported (>= redis 2.4.0).
  80. sudo sed -i '/# unixsocketperm/ s/^# unixsocketperm.*/unixsocketperm 0775/' /etc/redis/redis.conf
  81. # Activate the changes to redis.conf
  82. sudo service redis-server restart
  83. # Add git to the redis group
  84. sudo usermod -aG redis git
  85. # Configure Redis connection settings
  86. sudo -u git -H cp config/resque.yml.example config/resque.yml
  87. # Change the Redis socket path if you are not using the default Debian / Ubuntu configuration
  88. sudo -u git -H editor config/resque.yml
  89. # Configure gitlab-shell to use Redis sockets
  90. sudo -u git -H sed -i 's|^ # socket.*| socket: /var/run/redis/redis.sock|' /home/git/gitlab-shell/config.yml
  91. ## 6. Update gitlab-shell
  92. ```bash
  93. cd /home/git/gitlab-shell
  94. sudo -u git -H git fetch
  95. sudo -u git -H git checkout v2.6.5
  96. ```
  97. ## 7. Install libs, migrations, etc.
  98. ```bash
  99. sudo apt-get install libkrb5-dev
  100. cd /home/git/gitlab
  101. # MySQL installations (note: the line below states '--without ... postgres')
  102. sudo -u git -H bundle install --without development test postgres --deployment
  103. # PostgreSQL installations (note: the line below states '--without ... mysql')
  104. sudo -u git -H bundle install --without development test mysql --deployment
  105. # Run database migrations
  106. sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
  107. # Enable internal issue IDs (introduced in GitLab 6.1)
  108. sudo -u git -H bundle exec rake migrate_iids RAILS_ENV=production
  109. # Clean up assets and cache
  110. sudo -u git -H bundle exec rake assets:clean assets:precompile cache:clear RAILS_ENV=production
  111. # Close access to gitlab-satellites for others
  112. sudo chmod u+rwx,g+rx,o-rwx /home/git/gitlab-satellites
  113. # Update init.d script
  114. sudo cp lib/support/init.d/gitlab /etc/init.d/gitlab
  115. ```
  116. ## 8. Update config files
  117. TIP: to see what changed in `gitlab.yml.example` in this release use next command:
  118. ```
  119. git diff 6-0-stable:config/gitlab.yml.example 7-14-stable-ee:config/gitlab.yml.example
  120. ```
  121. * Make `/home/git/gitlab/config/gitlab.yml` the same as https://gitlab.com/gitlab-org/gitlab-ee/blob/7-14-stable-ee/config/gitlab.yml.example but with your settings.
  122. * Make `/home/git/gitlab/config/unicorn.rb` the same as https://gitlab.com/gitlab-org/gitlab-ee/blob/7-14-stable-ee/config/unicorn.rb.example but with your settings.
  123. * Make `/home/git/gitlab-shell/config.yml` the same as https://gitlab.com/gitlab-org/gitlab-shell/blob/v2.6.5/config.yml.example but with your settings.
  124. * Copy rack attack middleware config
  125. ```bash
  126. sudo -u git -H cp config/initializers/rack_attack.rb.example config/initializers/rack_attack.rb
  127. ```
  128. * Set up logrotate
  129. ```bash
  130. sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab
  131. ```
  132. ### Change Nginx settings
  133. * HTTP setups: Make `/etc/nginx/sites-available/gitlab` the same as https://gitlab.com/gitlab-org/gitlab-ee/blob/7-14-stable-ee/lib/support/nginx/gitlab but with your settings.
  134. * HTTPS setups: Make `/etc/nginx/sites-available/gitlab-ssl` the same as https://gitlab.com/gitlab-org/gitlab-ee/blob/7-14-stable-ee/lib/support/nginx/gitlab-ssl but with your settings.
  135. * A new `location /uploads/` section has been added that needs to have the same content as the existing `location @gitlab` section.
  136. ### Check the version of /usr/local/bin/git
  137. If you installed Git from source into /usr/local/bin/git then please [check
  138. your version](7.13-to-7.14.md).
  139. ## 9. Start application
  140. sudo service gitlab start
  141. sudo service nginx restart
  142. ## 10. Check application status
  143. Check if GitLab and its environment are configured correctly:
  144. cd /home/git/gitlab
  145. sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
  146. To make sure you didn't miss anything run a more thorough check with:
  147. sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
  148. If all items are green, then congratulations upgrade complete!
  149. ## 11. Update OmniAuth configuration
  150. When using Google omniauth login, changes of the Google account required.
  151. Ensure that `Contacts API` and the `Google+ API` are enabled in the [Google Developers Console](https://console.developers.google.com/).
  152. More details can be found at the [integration documentation](../../../master/doc/integration/google.md).
  153. ## 12. Optional optimizations for GitLab setups with MySQL databases
  154. Only applies if running MySQL database created with GitLab 6.7 or earlier. If you are not experiencing any issues you may not need the following instructions however following them will bring your database in line with the latest recommended installation configuration and help avoid future issues. Be sure to follow these directions exactly. These directions should be safe for any MySQL instance but to be sure make a current MySQL database backup beforehand.
  155. ```
  156. # Stop GitLab
  157. sudo service gitlab stop
  158. # Secure your MySQL installation (added in GitLab 6.2)
  159. sudo mysql_secure_installation
  160. # Login to MySQL
  161. mysql -u root -p
  162. # do not type the 'mysql>', this is part of the prompt
  163. # Convert all tables to use the InnoDB storage engine (added in GitLab 6.8)
  164. SELECT CONCAT('ALTER TABLE gitlabhq_production.', table_name, ' ENGINE=InnoDB;') AS 'Copy & run these SQL statements:' FROM information_schema.tables WHERE table_schema = 'gitlabhq_production' AND `ENGINE` <> 'InnoDB' AND `TABLE_TYPE` = 'BASE TABLE';
  165. # If previous query returned results, copy & run all shown SQL statements
  166. # Convert all tables to correct character set
  167. SET foreign_key_checks = 0;
  168. SELECT CONCAT('ALTER TABLE gitlabhq_production.', table_name, ' CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;') AS 'Copy & run these SQL statements:' FROM information_schema.tables WHERE table_schema = 'gitlabhq_production' AND `TABLE_COLLATION` <> 'utf8_unicode_ci' AND `TABLE_TYPE` = 'BASE TABLE';
  169. # If previous query returned results, copy & run all shown SQL statements
  170. # turn foreign key checks back on
  171. SET foreign_key_checks = 1;
  172. # Find MySQL users
  173. mysql> SELECT user FROM mysql.user WHERE user LIKE '%git%';
  174. # If git user exists and gitlab user does not exist
  175. # you are done with the database cleanup tasks
  176. mysql> \q
  177. # If both users exist skip to Delete gitlab user
  178. # Create new user for GitLab (changed in GitLab 6.4)
  179. # change $password in the command below to a real password you pick
  180. mysql> CREATE USER 'git'@'localhost' IDENTIFIED BY '$password';
  181. # Grant the git user necessary permissions on the database
  182. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, LOCK TABLES ON `gitlabhq_production`.* TO 'git'@'localhost';
  183. # Delete the old gitlab user
  184. mysql> DELETE FROM mysql.user WHERE user='gitlab';
  185. # Quit the database session
  186. mysql> \q
  187. # Try connecting to the new database with the new user
  188. sudo -u git -H mysql -u git -p -D gitlabhq_production
  189. # Type the password you replaced $password with earlier
  190. # You should now see a 'mysql>' prompt
  191. # Quit the database session
  192. mysql> \q
  193. # Update database configuration details
  194. # See config/database.yml.mysql for latest recommended configuration details
  195. # Remove the reaping_frequency setting line if it exists (removed in GitLab 6.8)
  196. # Set production -> pool: 10 (updated in GitLab 5.3)
  197. # Set production -> username: git
  198. # Set production -> password: the password your replaced $password with earlier
  199. sudo -u git -H editor /home/git/gitlab/config/database.yml
  200. ```
  201. ## Things went south? Revert to previous version (7.0)
  202. ### 1. Revert the code to the previous version
  203. Follow the [upgrade guide from 6.9 to 7.0](6.9-to-7.0.md), except for the database migration (the backup is already migrated to the previous version).
  204. ### 2. Restore from the backup:
  205. ```bash
  206. cd /home/git/gitlab
  207. sudo -u git -H bundle exec rake gitlab:backup:restore RAILS_ENV=production
  208. ```
  209. ## Login issues after upgrade?
  210. If running in HTTPS mode, be sure to read [Can't Verify CSRF token authenticity](https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide#cant-verify-csrf-token-authenticitycant-get-past-login-pageredirected-to-login-page)