Updating the virtual machine and physical resources
Upgrading the virtual software and virtual hardware requires some downtime for your instance, so be sure to plan your upgrade in advance.
Before upgrading GitHub Enterprise Server, review these recommendations and requirements to plan your upgrade strategy.
Upgrading GitHub Enterprise Server→
Upgrade GitHub Enterprise Server to get the latest features and security updates.
Enabling automatic update checks→
You can enable automatic update checks so that your GitHub Enterprise Server instance checks for and downloads the latest GitHub Enterprise Server release.
Increasing storage capacity→
You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.
Increasing CPU or memory resources→
To add CPU or memory resources to an existing GitHub Enterprise Server instance, shut down the instance and use the underlying virtual platform's tools to allocate the resources to the virtual machine. The newly allocated resources are automatically recognized on boot and no additional configuration is necessary.
Migrating from GitHub Enterprise 11.10.x to 2.1.23→
To migrate from GitHub Enterprise 11.10.x to 2.1.23, you'll need to set up a new appliance instance and migrate data from the previous instance.
Migrating Elasticsearch indices to GitHub Enterprise Server 2.14 or later→
To prepare for an upgrade to GitHub Enterprise Server 2.14, you'll need to migrate your indices to Elasticsearch 5.6 with our migration script.