Remove legal notice links, duplicated ARC intro (#56759)
This commit is contained in:
Ben Ahmady
@@ -13,8 +13,6 @@ redirect_from:
|
||||
- /actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-actions-runner-controller
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About {% data variables.product.prodname_actions_runner_controller %}
|
||||
|
||||
{% data reusables.actions.actions-runner-controller-about-arc %}
|
||||
|
||||
@@ -12,8 +12,6 @@ topics:
|
||||
- Actions Runner Controller
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About runner scale sets
|
||||
|
||||
A runner scale set is a group of homogeneous runners that can be assigned jobs from {% data variables.product.prodname_actions %}. The number of active runners owned by a runner scale set can be controlled by auto-scaling runner solutions such as {% data variables.product.prodname_actions_runner_controller %} (ARC).
|
||||
|
||||
@@ -17,8 +17,6 @@ redirect_from:
|
||||
- /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/extending-github-actions-importer-with-custom-transformers
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About custom transformers
|
||||
|
||||
{% data variables.product.prodname_actions_importer %} offers the ability to extend its built-in mapping by creating custom transformers. Custom transformers can be used to:
|
||||
|
||||
@@ -15,8 +15,6 @@ redirect_from:
|
||||
- /actions/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/supplemental-arguments-and-settings
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
This article provides general information for configuring {% data variables.product.prodname_actions_importer %}'s supplemental arguments and settings, such as optional parameters, path arguments, and network settings.
|
||||
|
||||
## Optional parameters
|
||||
|
||||
@@ -15,8 +15,6 @@ redirect_from:
|
||||
- /actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/authenticating-to-the-github-api#deploying-using-personal-access-token-classic-authentication
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
You can authenticate {% data variables.product.prodname_actions_runner_controller %} (ARC) to the {% data variables.product.prodname_dotcom %} API by using a {% data variables.product.prodname_github_app %} or by using a {% data variables.product.pat_v1 %}.
|
||||
|
||||
> [!NOTE]
|
||||
|
||||
@@ -15,8 +15,6 @@ redirect_from:
|
||||
- /actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## Deploying a runner scale set
|
||||
|
||||
To deploy a runner scale set, you must have ARC up and running. For more information, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/quickstart-for-actions-runner-controller).
|
||||
|
||||
@@ -15,14 +15,6 @@ redirect_from:
|
||||
- /actions/tutorials/quickstart-for-actions-runner-controller
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## Introduction
|
||||
|
||||
{% data reusables.actions.actions-runner-controller-about-arc %}
|
||||
|
||||
You can set up ARC on Kubernetes using Helm, then create and run a workflow that uses runner scale sets. For more information about runner scale sets, see [AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller#runner-scale-set).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
In order to use ARC, ensure you have the following.
|
||||
|
||||
@@ -14,8 +14,6 @@ redirect_from:
|
||||
- /actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## Logging
|
||||
|
||||
The {% data variables.product.prodname_actions_runner_controller %} (ARC) resources, which include the controller, listener, and runners, write logs to standard output (`stdout`). We recommend you implement a logging solution to collect and store these logs. Having logs available can help you or GitHub support with troubleshooting and debugging. For more information, see [Logging Architecture](https://kubernetes.io/docs/concepts/cluster-administration/logging/) in the Kubernetes documentation.
|
||||
|
||||
@@ -15,8 +15,6 @@ redirect_from:
|
||||
- /actions/how-tos/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/using-actions-runner-controller-runners-in-a-workflow
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## Using ARC runners in a workflow file
|
||||
|
||||
To assign jobs to run on a runner scale set, you can specify the name of the scale set as the value for the `runs-on` key in your {% data variables.product.prodname_actions %} workflow file.
|
||||
|
||||
@@ -20,8 +20,6 @@ shortTitle: 'Automate migration with {% data variables.product.prodname_actions_
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About {% data variables.product.prodname_actions_importer %}
|
||||
|
||||
You can use {% data variables.product.prodname_actions_importer %} to plan and automatically migrate your CI/CD supported pipelines to {% data variables.product.prodname_actions %}.
|
||||
|
||||
@@ -17,8 +17,6 @@ redirect_from:
|
||||
- /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/migrating-from-azure-devops-with-github-actions-importer
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About migrating from Azure DevOps with GitHub Actions Importer
|
||||
|
||||
The instructions below will guide you through configuring your environment to use {% data variables.product.prodname_actions_importer %} to migrate Azure DevOps pipelines to {% data variables.product.prodname_actions %}.
|
||||
|
||||
@@ -17,8 +17,6 @@ redirect_from:
|
||||
- /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/migrating-from-bamboo-with-github-actions-importer
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About migrating from Bamboo with GitHub Actions Importer
|
||||
|
||||
The instructions below will guide you through configuring your environment to use {% data variables.product.prodname_actions_importer %} to migrate Bamboo pipelines to {% data variables.product.prodname_actions %}.
|
||||
|
||||
@@ -17,8 +17,6 @@ redirect_from:
|
||||
- /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/migrating-from-bitbucket-pipelines-with-github-actions-importer
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About migrating from Bitbucket Pipelines with GitHub Actions Importer
|
||||
|
||||
The instructions below will guide you through configuring your environment to use {% data variables.product.prodname_actions_importer %} to migrate Bitbucket Pipelines to {% data variables.product.prodname_actions %}.
|
||||
|
||||
@@ -17,8 +17,6 @@ redirect_from:
|
||||
- /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/migrating-from-circleci-with-github-actions-importer
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About migrating from CircleCI with GitHub Actions Importer
|
||||
|
||||
The instructions below will guide you through configuring your environment to use {% data variables.product.prodname_actions_importer %} to migrate CircleCI pipelines to {% data variables.product.prodname_actions %}.
|
||||
|
||||
@@ -17,8 +17,6 @@ redirect_from:
|
||||
- /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/migrating-from-gitlab-with-github-actions-importer
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About migrating from GitLab with GitHub Actions Importer
|
||||
|
||||
The instructions below will guide you through configuring your environment to use {% data variables.product.prodname_actions_importer %} to migrate GitLab pipelines to {% data variables.product.prodname_actions %}.
|
||||
|
||||
@@ -17,8 +17,6 @@ redirect_from:
|
||||
- /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/migrating-from-jenkins-with-github-actions-importer
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About migrating from Jenkins with GitHub Actions Importer
|
||||
|
||||
The instructions below will guide you through configuring your environment to use {% data variables.product.prodname_actions_importer %} to migrate Jenkins pipelines to {% data variables.product.prodname_actions %}.
|
||||
|
||||
@@ -17,8 +17,6 @@ redirect_from:
|
||||
- /actions/how-tos/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/migrating-from-travis-ci-with-github-actions-importer
|
||||
---
|
||||
|
||||
[Legal notice](#legal-notice)
|
||||
|
||||
## About migrating from Travis CI with GitHub Actions Importer
|
||||
|
||||
The instructions below will guide you through configuring your environment to use {% data variables.product.prodname_actions_importer %} to migrate Travis CI pipelines to {% data variables.product.prodname_actions %}.
|
||||
|
||||
Reference in New Issue
Block a user