We have version gitlab-ee 10.6.4 running on Ubuntu 16.04.06. We recently stood a new server with Ubuntu 18.04.4. The installer added a newer version of GITLab, so we cannot import the repositories. If we run the apt-get install gitlab-ee from the 10.6.4 version, will it step to the next version each time we run the command or will it go to the newest version? We would like to move to the newer box.
Describe your question in as much detail as possible:
What are you seeing, and how does it differ from what you expect to see?
Consider including screenshots, error messages, and/or other helpful visuals
What version are you on (Hint: /help) ? and are you using self-managed or gitlab.com?
What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
Thanks for taking the time to be thorough in your request, it really helps!
Which version do you have on the new box, and where did you get it from?
Is the old server set up with a repository that has newer version than 10.6.4? Why are you still running 10.6.4? It’s from 9 April 2018, and not even the last version in the 10.6 series, so it has known security issues.
The old server is 16.04 with the 10.6.4. The new server, stood locally, is 18.04 with version 12.7.5. Both where installed from the repositories with APT. They are still running 10.6.4, because they appear
to be a bit lazy in doing updates and upgrades on that box, but that is another issue all together. I know that I cannot go directly from 10.6.4 to 12.7.5, so I’m hoping that the apt install will only take me up a version at a time.
There er several apt repositories out there with GitLab in them, so that doesn’t really answer where you got them from.
If a version is available in the repos you use, you can install it/upgrade to it with apt install gitlab-ee=<version_number>, so you can upgrade to e.g. 11.0.2 (that would be silly, but for illustration I believe it’s better to go with something you shouldn’t just copy) with apt install gitlab-ee=11.0.2-ee.0 (’-ee.0’ is part of the version number, I have no idea why). There are plenty of threads on this forum about selecting which versions to include on the upgrade path, and as I don’t remember the link to the page with the official advice, I won’t go into that now.
Thank you that method, following the release and maintenance page allowed me to step through. I noticed on the 18.04/12.0.9 box, the apt update/upgrade, went to the next version 12.5.8 by just using apt update
and apt upgrade. Again, thank you for taking the time to help me with this.
Side note: The first one to 10.8.7 gave me a database migration error. I turned off the auto-configure, ran the update, then manually ran gitlab-rake db:migrate --trace. It then ran without issue. Someone
else may run into that.
I should probably have mentioned that without instructions to do otherwise the apt-tools will do as all(?) other installation/upgrade tools and go straight to the newest available version, and in most cases that is what you want so it makes sense. But it explains what you saw on the 18.04 box.
I can’t tell you why you ran into that database migration error but I’m glad you solved it so easily.
