Instances with lots of users) > 16.3 > latest 16.Y.Z. GitLab instances with multiple web nodes) > 15.4.6 > To shareįeedback and help improve the tool, create an issue or MR in the upgrade-path project.įind where your version sits in the upgrade path: If you don’t want any downtime, read how to upgrade with zero downtime.įor a dynamic view of examples of supported upgrade paths, try the Upgrade Path tool Upgrading across multiple GitLab versions in one go is only possible by accepting downtime. This ensuresĬompatibility with GitLab versions. Important to upgrade them to match the current GitLab version. If your GitLab instance has any runners associated with it, it is very.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |