Skip to content

Instantly share code, notes, and snippets.

@mbohun

mbohun/NOTES.md

Last active August 12, 2022 02:02
Show Gist options
  • Save mbohun/326659674071bb91de7528930db8ca23 to your computer and use it in GitHub Desktop.
Save mbohun/326659674071bb91de7528930db8ca23 to your computer and use it in GitHub Desktop.
Download ZIP
GitHub Enterprise upgrade
Raw
NOTES.md

GitHub Enterprise UPGRADE

(In 1024 simple steps)

TYPICAL GitHub 💩

Recommendations

Include as few upgrades as possible in your upgrade process. For example, instead of upgrading from GitHub Enterprise 3.3 to 3.4 to 3.5, you could upgrade from GitHub Enterprise 3.3 to 3.5. Use the Upgrade assistant to find the upgrade path from your current release version.
HOWEVER the next paragraph:

Requirements

You must upgrade from a feature release that's at most two releases behind. For example, to upgrade to GitHub Enterprise 3.5, you must be on GitHub Enterprise 3.4 or 3.3.

https://docs.github.com/en/[email protected]/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements

Moral of the story

In our case (3.0.x -> 3.5.x) It is going to be a THREE STEP upgrade, according to their "upgrade path finder":

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment