PageRenderTime 22ms CodeModel.GetById 35ms RepoModel.GetById 0ms app.codeStats 0ms

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

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