From ca0613998e3cebe94930dce68ae0efa80eec4b2c Mon Sep 17 00:00:00 2001 From: Felicity Chapman Date: Wed, 20 Apr 2022 16:49:16 +0100 Subject: [PATCH 1/2] Update codeql-runner-supported.yml (#27036) --- data/features/codeql-runner-supported.yml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/data/features/codeql-runner-supported.yml b/data/features/codeql-runner-supported.yml index f1ea3ca57b..897bc7a079 100644 --- a/data/features/codeql-runner-supported.yml +++ b/data/features/codeql-runner-supported.yml @@ -1,6 +1,5 @@ # Tracking deprecation of CodeQL runner +# https://github.blog/changelog/2022-04-05-codeql-runner-is-now-deprecated/ + versions: - fpt: '*' - ghec: '*' - ghes: '*' - ghae: '*' + ghes: '<=3.3' From 4ee31bf8bc1427ba4b35978474f3c9092ddba262 Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Wed, 20 Apr 2022 10:54:05 -0500 Subject: [PATCH 2/2] Self-hosted runners upgrade strategy for GHES (#27007) --- .../hosting-your-own-runners/about-self-hosted-runners.md | 8 ++++++++ .../monitoring-and-troubleshooting-self-hosted-runners.md | 8 ++++++++ .../upgrading-github-enterprise-server.md | 5 +++-- .../actions/upgrade-runners-before-upgrade-ghes.md | 1 + 4 files changed, 20 insertions(+), 2 deletions(-) create mode 100644 data/reusables/actions/upgrade-runners-before-upgrade-ghes.md diff --git a/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 7adf2c01fc..c1e1ea2515 100644 --- a/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -28,6 +28,14 @@ You can add self-hosted runners at various levels in the management hierarchy: {% data reusables.actions.self-hosted-runner-architecture %} {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs. +{% ifversion ghes %} +{% note %} + +**Note:** {% data reusables.actions.upgrade-runners-before-upgrade-ghes %} + +{% endnote %} +{% endif %} + {% data reusables.actions.self-hosted-runner-auto-removal %} For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." diff --git a/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 6c596084ba..8bc1ed42f1 100644 --- a/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -258,3 +258,11 @@ User=runner-user ``` {% endlinux %} + +{% ifversion ghes %} +## Resolving runners that are offline after an upgrade of {% data variables.product.product_location %} + +{% data reusables.actions.upgrade-runners-before-upgrade-ghes %} + +If your runners are offline for this reason, manually update the runners. For more information, see the installation instructions for [the latest release](https://github.com/actions/runner/releases/latest) in the actions/runner repository. +{% endif %} \ No newline at end of file diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 3a8e381da1..cdd8706294 100644 --- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -28,8 +28,9 @@ shortTitle: Upgrading GHES ## Preparing to upgrade 1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version. -3. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme). -4. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required. +1. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README.md file](https://github.com/github/backup-utils#readme). +1. If {% data variables.product.product_location %} uses ephemeral self-hosted runners for {% data variables.product.prodname_actions %} and you've disabled automatic updates, upgrade your runners to the version of the runner application that your upgraded instance will run. +1. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required. {% note %} diff --git a/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md b/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md new file mode 100644 index 0000000000..05e72ec744 --- /dev/null +++ b/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md @@ -0,0 +1 @@ +If you use ephemeral runners and have disabled automatic updates, before you upgrade {% data variables.product.product_location %}, you should first upgrade your self-hosted runners to the version of the runner application that your upgraded instance will run. Upgrading {% data variables.product.product_location %} before you upgrade ephemeral runners may result in your runners going offline. For more information, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." \ No newline at end of file