Sometimes a reboot is required, which you can perform at a later time. Upgrades using a hotpatch usually don't require a maintenance window. Note: The maintenance window depends on the type of upgrade you perform. For more information, see the README in the GitHub Enterprise Server Backup Utilities project documentation. For more information, see " Upgrade requirements" and refer to the Upgrade assistant to find the upgrade path from your current release version.Ĭreate a fresh backup of your instance's primary node with the GitHub Enterprise Server Backup Utilities. To prepare for an upgrade, plan the upgrade path, optionally upgrade GitHub Actions runners, and schedule a maintenance window.ĭetermine an upgrade strategy and choose a version to upgrade to. In some rare cases, for customers with large data volumes, this threshold may differ. GitHub recommends ensuring there is more free storage on the disk. To successfully upgrade your GitHub Enterprise Server instance, the instance's data disk must be at least 15% free. To upgrade an instance, you must plan and communicate the upgrade, choose the appropriate package, back up your data, and then perform the upgrade. For more information, see " About upgrades to new releases." You are responsible for upgrades to your instance. GitHub Enterprise Server is constantly improving, with new functionality and bug fixes introduced through feature and patch releases. About upgrades to GitHub Enterprise Server
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |