About larger runners

Overview of executor maiors

Além dos executores hospedados GitHub padrão, o GitHub oferece aos clientes de planos GitHub Team e GitHub Enterprise Cloud um intervalo de máquinas virtuais gerenciadas com mais RAM, CPU e espaço em disco. Esses executores são hospedados por GitHub e têm o aplicativo executor e outras ferramentas pré-instalados.

When you add a executor maior to an organization, you are defining a type of machine from a selection of available hardware specifications and operating system images. GitHub will then create multiple instances of this runner that scale up and down to match the job demands of your organization, based on the autoscaling limits you define.

Understanding billing

Compared to standard GitHub-hosted runners, executor maiors are billed differently. Executor maior são cobrados somente pela taxa por minuto do tempo em que os fluxos de trabalho são executados neles. Não há nenhum custo associado à criação de um executor maior que não está sendo usado pelo fluxo de trabalho. For more information, see "Sobre a cobrança das GitHub Actions."

Machine sizes for executor maiors

Processor (CPU)	Memory (RAM)	Storage (SSD)	Operating system (OS)
4	16 GB	150 GB	Ubuntu
8	32 GB	300 GB	Ubuntu, Windows
16	64 GB	600 GB	Ubuntu, Windows
32	128 GB	1200 GB	Ubuntu, Windows
64	256 GB	2040 GB	Ubuntu, Windows

Additional features for executor maiors

Compared to standard GitHub-hosted runners, executor maiors have the following additional features:

• For Ubuntu runners, hardware acceleration for the Android SDK tools is enabled. This makes running Android tests much faster and consumes fewer minutes. For more information on Android hardware acceleration, see Configure hardware acceleration for the Android Emulator in the Android Developers documentation.
• Executor maiors can be assigned static IP addresses from specific ranges, which enables you to use the ranges to configure a firewall allowlist. For more information, see "Networking for executor maiors."
• Executor maiors can automatically scale up to a maximum limit set by you, so your workflows can run concurrently. For more information, see "Autoscaling executor maiors."
• Runner groups allow you to control access to executor maiors for your organizations, repositories, and workflows. For more information, see "Controlling access to larger runners."

For a full list of included tools for each runner operating system, see the GitHub Actions Runner Images repository.

About runner groups

Runner groups enable administrators to control access to runners at the organization and enterprise levels. With runner groups, you can collect sets of runners and create a security boundary around them. You can then decide which organizations or repositories are permitted to run jobs on those sets of machines. During the executor maior deployment process, the runner can be added to an existing group, otherwise it will join a default group. You can create a group by following the steps in "Controlling access to larger runners."

Architectural overview of executor maiors

Executor maiors are managed at the organization level, where they are arranged into groups that can contain multiple instances of the runner. They can also be created at the enterprise level and shared with organizations in the hierarchy. Once you've created a group, you can then add a runner to the group and update your workflows to target either the group name or the label assigned to the executor maior. You can also control which repositories are permitted to send jobs to the group for processing. For more information about groups, see "Controlling access to larger runners."

In the following diagram, a class of hosted runner named ubuntu-20.04-16core has been defined with customized hardware and operating system configuration.

1. Instances of this runner are automatically created and added to a group called grp-ubuntu-20.04-16core.
2. The runners have been assigned the label ubuntu-20.04-16core.
3. Workflow jobs use the ubuntu-20.04-16core label in their runs-on key to indicate the type of runner they need to execute the job.
4. GitHub Actions checks the runner group to see if your repository is authorized to send jobs to the runner.
5. The job runs on the next available instance of the ubuntu-20.04-16core runner.

Autoscaling executor maiors

Executor maiors can automatically scale to suit your needs. You can provision machines to run a specified maximum number of jobs when jobs are submitted for processing. Each machine only handles one job at a time, so these settings effectively determine the number of jobs that can be run concurrently.

You can configure the maximum job concurrency, which allows you to control your costs by setting the maximum parallel number of jobs that can be run using this set. A higher value here can help avoid workflows being blocked due to parallelism. For more information, see "Managing larger runners."

Networking for executor maiors

By default, executor maiors receive a dynamic IP address that changes for each job run. Optionally, GitHub Enterprise Cloud customers can configure their executor maiors to receive static IP addresses from GitHub's IP address pool. For more information, see "Sobre os endereços IP do GitHub."

When enabled, instances of the executor maior will receive IP addresses from specific ranges that are unique to the runner, allowing you to use the ranges to configure a firewall allowlist. You can use up to 10 executor maiors with static IP address ranges in total across all your executor maiors. For more information, see "Managing larger runners."

Para usar mais de 10 executores maiores com intervalos de endereços IP estáticos, entre em contato com Suporte do GitHub.