Skip to content

configuring-larger-runners-for-default-setup.md

Latest commit

 

History

History
45 lines (34 loc) · 5.47 KB

configuring-larger-runners-for-default-setup.md

File metadata and controls

45 lines (34 loc) · 5.47 KB
title Configuring larger runners for default setup
shortTitle Configure larger runners
intro Run {% data variables.product.prodname_code_scanning %} default setup more quickly on bigger codebases using {% data variables.actions.hosted_runners %}.
product {% data reusables.actions.larger-runner-permissions %}
versions
feature
default-setup-larger-runners
redirect_from
/code-security/code-scanning/managing-your-code-scanning-configuration/configuring-larger-runners-for-default-setup
/code-security/how-tos/scan-code-for-vulnerabilities/manage-your-configuration/configuring-larger-runners-for-default-setup
contentType how-tos
category
Find and fix code vulnerabilities

{% data reusables.code-scanning.beta-larger-runners-support %}

{% ifversion ghec %}

Provisioning enterprise-level {% data variables.actions.hosted_runners %} for default setup

  1. Add a {% data variables.actions.hosted_runner %} to your enterprise. For more information, see AUTOTITLE.
    • To add the code-scanning label to your {% data variables.actions.hosted_runner %}, name the runner code-scanning. An enterprise can only have one {% data variables.actions.hosted_runner %} named code-scanning, and that runner will handle all {% data variables.product.prodname_code_scanning %} jobs for all organizations and repositories within your enterprise that:
      • Have access to the enterprise-level runner, and
      • Don't have access to an organization-level {% data variables.actions.hosted_runner %} named code-scanning. If an organization or repository also has access to an organization-level {% data variables.actions.hosted_runner %} named code-scanning, each {% data variables.product.prodname_code_scanning %} job will be randomly assigned to either the organization-level or enterprise-level runner. {% data reusables.actions.org-access-to-github-hosted-runners %}
  2. To analyze repositories with default setup, grant the desired repositories access to the runner group your {% data variables.actions.hosted_runner %} is assigned to. For more information, see AUTOTITLE.
  3. You can now configure default setup for your enterprise, organizations, and repositories, and your {% data variables.actions.hosted_runner %} will automatically pick up {% data variables.product.prodname_code_scanning %} jobs as previously specified. For more information on configuring default setup, see AUTOTITLE and AUTOTITLE. {% endif %}

Provisioning organization-level {% data variables.actions.hosted_runners %} for default setup

  1. Add a {% data variables.actions.hosted_runner %} to your organization. See AUTOTITLE.

    • To add a custom label to your {% data variables.actions.hosted_runner %}, give the runner a name that matches that label. You can use this custom label when you configure default setup with {% data variables.actions.hosted_runners %}.

  2. By default, all repositories in your organization have access to organization-level runners, meaning every repository can use your {% data variables.actions.hosted_runner %}. For information on granting only select repositories access to a {% data variables.actions.hosted_runner %}, see AUTOTITLE.

  3. You can now configure default setup for your organization and repositories, and your {% data variables.actions.hosted_runner %} will automatically pick up {% data variables.product.prodname_code_scanning %} jobs. For more information on configuring default setup, see AUTOTITLE and AUTOTITLE.

Extra steps for Swift analysis

Currently, Swift analysis is not available on {% data variables.actions.hosted_runners %} for default setup. Additionally, if your repository has access to a runner with the code-scanning label, such as a {% data variables.actions.hosted_runner %} provisioned for default setup, default setup workflows will only use runners labeled code-scanning. If you would like to configure default setup on {% data variables.actions.hosted_runners %} and analyze Swift, you have two options:

  • Provision a self-hosted macOS runner with the code-scanning label in addition to your {% data variables.actions.hosted_runner %}. For more information, see {% ifversion ghec %}AUTOTITLE.{% else %}AUTOTITLE.{% endif %}
  • Ensure any repositories containing Swift do not have access to runners with the label code-scanning. Default setup workflows for that repository will only use standard runners