Sometimes GitHub Enterprise instances don't have access to the outside internet, so following instructions on how to upgrade from the help docs may not be possible. But, anyone who's upgrading will have ssh
access to their instance, so using scp
to get it up there should be valid.
Coming from 2.4.x
we need to download two separate packages and upload them and upgrade one at a time. I'll download them to just our local user directory on OS X
curl -L -o ~/github-enterprise-esx-2.6.12.pkg https://github-enterprise.s3.amazonaws.com/ova/updates/github-enterprise-esx-2.6.12.pkg
curl -L -o ~/github-enterprise-esx-2.8.2.pkg https://github-enterprise.s3.amazonaws.com/ova/updates/github-enterprise-esx-2.8.2.pkg
Now we're left with two packages in our home directory that we can scp up to the server.
Because the partition switches after an upgrade, we can only scp
the packages one at a time. Note the capital P
on the command for scp
that is different than the lowercase p
of ssh
to connect to the server.
scp -P 122 ~/github-enterprise-esx-2.6.12.pkg admin@YOUR_GITHUB_ENTERPRISE_SERVER:/home/admin
Once you've used scp
to get the package up to your instance, you just need to follow the normal upgrade instructions but skipping step 3, because you already have the package in the home directory of the admin user.
Once that is finished, we need to scp
the last package to the instance.
scp -P 122 ~/github-enterprise-esx-2.8.2.pkg admin@YOUR_GITHUB_ENTERPRISE_SERVER:/home/admin
Lastly, we would again follow the instructions for upgrading and skipping step 3.