Configuring larger runners for default setup

You can run code scanning default setup more quickly on bigger codebases using 大型运行器.

谁可以使用此功能？

大型运行器 目前仅对使用 GitHub Team 或 GitHub Enterprise Cloud 计划的组织和企业可用。

本文内容

注意

对于 code scanning 默认设置的 大型运行器 支持目前为 公共预览版，可能会更改。

About 大型运行器 for default setup

GitHub Team 和 GitHub Enterprise Cloud 计划的客户可以从一系列托管的虚拟机中选择，这些虚拟机比标准 GitHub 托管的运行器拥有更多资源。 这些计算机称为“大型运行器”。 具有以下高级功能：

  • 更多内存、CPU 和磁盘空间
  • 静态 IP 地址
  • Azure 专用网络
  • 分组运行器的能力
  • 自动缩放以支持并发工作流
  • GPU 支持的运行程序

这些 大型运行器 由 GitHub 托管，并预安装了运行器应用程序和其他工具。 For more information about 大型运行器, see 大型运行器.

Consider configuring 大型运行器 for default setup if:

  • Your scans with standard GitHub-hosted runners are taking too long.
  • Your scans with standard GitHub-hosted runners are returning memory or disk errors.
  • You want to customize aspects of your code scanning runner like the runner size, runner image, and job concurrency without using self-hosted runners.

警告

Currently, Swift analysis is not available on 大型运行器 for default setup. Additionally, if your repository has access to a runner with the code-scanning label, such as a 大型运行器 provisioned for default setup, default setup workflows will only use runners labeled code-scanning. If you would like to configure default setup on 大型运行器 and analyze Swift, you have two options:

  • Provision a self-hosted macOS runner with the code-scanning label in addition to your 大型运行器. For more information, see 为企业中的代码扫描配置自托管式运行器.
  • 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.

Provisioning enterprise-level 大型运行器 for default setup

  1. Add a 大型运行器 to your enterprise. For more information, see 管理较大的运行器.
    • To add the code-scanning label to your 大型运行器, name the runner code-scanning. An enterprise can only have one 大型运行器 named code-scanning, and that runner will handle all 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 大型运行器 named code-scanning. If an organization or repository also has access to an organization-level 大型运行器 named code-scanning, each code scanning job will be randomly assigned to either the organization-level or enterprise-level runner.
  2. 若要允许组织访问 大型运行器，请指定哪些组织可以使用已分配运行器的运行器组。 有关详细信息，请参阅“控制对较大运行器的访问”。
  3. To analyze repositories with default setup, grant the desired repositories access to the runner group your 大型运行器 is assigned to. For more information, see 管理较大的运行器.
  4. You can now configure default setup for your enterprise, organizations, and repositories, and your 大型运行器 will automatically pick up code scanning jobs as previously specified. For more information on configuring default setup, see Configuring default setup for code scanning and 配置大规模代码扫描的默认设置.

Provisioning organization-level 大型运行器 for default setup

  1. Add a 大型运行器 to your organization. See 管理较大的运行器.
    • To add a custom label to your 大型运行器, give the runner a name that matches that label. You can use this custom label when you configure default setup with 大型运行器. For more information, see Configuring default setup for code scanning.
  2. By default, all repositories in your organization have access to organization-level runners, meaning every repository can use your 大型运行器. For information on granting only select repositories access to a 大型运行器, see 管理较大的运行器.
  3. You can now configure default setup for your organization and repositories, and your 大型运行器 will automatically pick up code scanning jobs. For more information on configuring default setup, see Configuring default setup for code scanning and 配置大规模代码扫描的默认设置.