Update path starting with 11.99

HI Everyone!
I was asked to upgrade two Gitlab installations. One in a test environment and one under production.
I started with the test environment server. Start: 13.9.1 Target 15.3.2
Worked pretty well only the upgrade to 14.0 resulted in an error about the database and migration errors. They were fixed. For this system it was not urgent so I had time to upgrade and fix.
The production system is a bit more sensitive. I need to do this in the shortest time possible. Unf this starts with 11.99 so more steps are needed.
The plan would be

11.9.9 - 12.0.12 → 12.1.17 → 12.10.14 → 13.0.14 → 13.1.11 → 13.8.8 → 13.12.15 → 14.0.12 → 14.3.6 → 14.9.5 → 14.10.5 → 15.0.2 → 15.3.2

according to the info I found. Is that the shortest and most reliable way? Any hints would be greatly appreciated.

Thanks a lot!

DirkV

Hi,

You can’t do it any shorter than the upgrade path as shown in the Gitlab docs. So this is the same as you have above. That is pretty much the optimal plan, since a lot of those jumps will contain migrations that need to run and finish before you start the next upgrade. If you attempt to start the next upgrade before the migrations have finished, you can have problems with the database and failed migrations (which may break your Gitlab installation). The Gitlab docs explain how to check the background migrations from the console, and in later versions it’s possible to see this in the web admin interface.

I agree with @iwalker, that is the shortest path.

At least assuming that by “11.99” you meant “11.9.9”. As you can see from the path, GitLab has used multi digit component at any part of the version number. “13.111” might mean both “13.1.11” and “13.11.1” (both exists), so be careful not to forget dots.

Cool! Thanks!
Yes there was a missing . thats corrected.
That helped a lot here.