jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 11:54:18 -05:00
Code Issues Projects Releases Wiki Activity

Deprecate GHES 3.3 (#34328)

Browse Source 
Co-authored-by: Felicity Chapman <felicitymay@github.com>
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
Co-authored-by: Sam Browning <106113886+sabrowning1@users.noreply.github.com>
This commit is contained in:
Kevin Heis
2023-02-03 09:05:11 -08:00
committed by GitHub
parent 6748ab45c9
commit ac2cd0e47d
155 changed files with 222 additions and 542213 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
View File

@@ -47,13 +47,6 @@ The peak quantity of connected runners without performance loss depends on such
{% endif %}
{%- ifversion ghes = 3.3 %}
{% data reusables.actions.hardware-requirements-3.3 %}
Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
{%- endif %}
{%- ifversion ghes = 3.4 %}
@@ -79,7 +72,6 @@ Maximum concurrency was measured using multiple repositories, job duration of ap
{%- ifversion ghes > 3.5 %}
| vCPUs | Memory | Maximum Connected Runners |
| :---| :--- | :--- |
| 8 | 64 GB | 740 runners |

4
content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
View File

@@ -99,14 +99,14 @@ You can create a runner group to manage access to the runner that you added to y
{% endwarning %}
{%- endif %}
{% data reusables.actions.create-runner-group %}
{%- ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
{%- ifversion ghec or ghes or ghae > 3.3 %}
1. Click the "Runners" tab.
1. In the list of runners, click the runner that you deployed in the previous section.
1. Click **Edit**.
1. Click **Runner groups {% octicon "gear" aria-label="The Gear icon" %}**.
1. In the list of runner groups, click the name of the group that you previously created.
1. Click **Save** to move the runner to the group.
{%- elsif ghes < 3.4 or ghae %}
{%- elsif ghae %}
1. To the right of "Default", click the number of runners in the group to show the runners.
1. Select the runner that you deployed.
1. To the right of "Runner groups", select the **Move to group** dropdown, and click the group that you previously created.

2
content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
View File

@@ -71,7 +71,7 @@ Think about how your enterprise can use features of {% data variables.product.pr
{% data reusables.actions.internal-actions-summary %}
{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
{% ifversion ghec or ghes or ghae > 3.3 %}
{% data reusables.actions.reusable-workflows-enterprise-beta %}
With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
{% endif %}