(#500-error-when-accessing-project-settings-repository-on-omnibus-installs)ġ. When updating to EE from CE, avoid reverting back to CE if you plan on going to EE again in the You are upgrading the same version (for example, CE 12.1 to EE 12.1), which is **recommended**. However, in the following steps we assume that (for example, CE 12.0 to EE 12.1) should work. Upgrading from the same version of CE to EE is not explicitly necessary, and any standard upgrade Packages to GitLab () (EE), you install the EE To upgrade an existing GitLab Community Edition (CE) server installed using the Omnibus GitLab # Update Community Edition to Enterprise Edition If for some reason you don't use the official repositories, you can # Update using a manually-downloaded package To update to a newer GitLab version, run: Official GitLab repository should have already been set up for you. They will either see a "Deploy in progress" message or a "502" error in their web browser. Unless you are following the steps in (#zero-downtime-updates), your GitLab application will not be available to users while an update is in progress. When upgrading to a new major version, remember to first (). You may skip this automatic backup by creating an empty fileįor safety reasons, you should maintain an up-to-date backup on your own if you plan to use this flag. (#update-using-a-manually-downloaded-package).īoth will automatically back up the GitLab database before installing a newer (#update-using-the-official-repositories). There are two ways to update Omnibus GitLab: Settings, upgrade of internal tools and libraries etc. Installations** due to multiple reasons like deprecated or removed configuration This restricts performing direct upgrades that skip major versions (forĮxample 10.3 to 12.7 in one jump) that **can break GitLab # Mandatory upgrade paths for version upgradesįrom GitLab 10.8, upgrade paths are enforced for version upgrades byĭefault. Updating to major versions might need some manual intervention. That can process jobs in the `background_migration` queue. Decrease the time required toĬomplete these migrations by increasing the number of Week, to allow time for background migrations to finish.
We recommend performing upgrades between major and minor releases no more than once per To see the current size of the `background_migration` queue, It's important to ensure that any background migrations have been fully completedīefore upgrading to a new major version. If you aren't (#mandatory-upgrade-paths-for-version-upgrades), If you are upgrading from a non-Omnibus installation to an Omnibus installation, see # Update GitLab installed with the Omnibus GitLab packageīefore following these instructions, note the following:
Info: To determine the technical writer assigned to the Stage/Group associated with this page, see
0 kommentar(er)
