How to upgrade Gitlab 5.0 to 5.1 on CentOS 6 or RHEL6

Last modified: [last-modified]

These are instructions on how to upgrade Gitlab 5.0 to 5.1 on CentOS 6.

This guide assumes you already followed my How to install Gitlab 5.0 on CentOS 6 or RHEL6 post.

  1. As the root user stop the Gitlab service

     
  2. Switch to the ‘sa_gitlab’ user account and move into your gitlab directory

     
  3. Update Gitlab source from 5.0 to 5.1

     
  4. Configure Puma which is replacing Unicorn

     
  5. Redeploy Gitlab (I think that’s what this does anyway)

     
  6. Switch back to root and update the Gitlab start-up script

     
  7. Start up Gitlab and then restart Apache if your using mod_proxy

     
  8. Update Gitlab Shell

All done! Hopefully this went slightly more smoothly for you then it did me. I noticed the first time loading Gitlab after the upgrade as a bit slow but things were nice and quick after that.

Updated April 26th, 2013 – Added instructions for updating Gitlab shell.

Updated May 22nd, 2013 – Wrote an article on How to go from 5.1 to 5.2

7 thoughts on “How to upgrade Gitlab 5.0 to 5.1 on CentOS 6 or RHEL6

  1. 1. I used your 50 install instructions, worked great. So came back for the 51 upgrade. Wondering why you left out the gitlab-shell step 1.2.0 -> 1.3.0
    2. After the migration steps I could not login with admin, new or default values. But my initial gitlab install was last night, so I just reran the gitlab:setup to get the default admin account created. I’m sure there was a better way but it’s day #2 with git & gitlab so clumsy brute force was quick.
    3. Thanks for the nice write-up.

    • I didn’t realize there had been an update to Gitshell. I was following the instructions I found on the Gitlab site. I’ll have to update the article.

      Strange your admin account disappeared. I did not have this happen with mine.

      You’re welcome :)

  2. These are very good instructions. Was able to follow them to the T and upgrade to 5.1
    Thanks soooo very much!

Leave a Reply

Your email address will not be published. Required fields are marked *