Skip to main content

Getting started with GitHub Actions for GitHub Enterprise Server

Learn about enabling and configuring GitHub Actions on GitHub Enterprise Server for the first time.

Who can use this feature

Site administrators can enable GitHub Actions and configure enterprise settings.

Nota: Actualmente los ejecutores hospedados en GitHub no se admiten en GitHub Enterprise Server. Puede ver más información sobre la compatibilidad futura planeada en GitHub public roadmap.

About GitHub Actions on GitHub Enterprise Server

This article explains how site administrators can configure GitHub Enterprise Server to use GitHub Actions.

GitHub Actions no está habilitado para GitHub Enterprise Server de manera predeterminada. You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from GitHub Actions without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable GitHub Actions for your enterprise, manage access permissions, and add self-hosted runners to run workflows.

Antes de iniciar, debes hacer un plan de cómo introducirás las GitHub Actions a tu empresa. Para obtener más información, vea "Presentar GitHub Actions en su empresa".

Si estás migrando tu empresa a las GitHub Actions desde otro proveedor, hay consideraciones adicionales. Para obtener más información, vea "Migrar la empresa a GitHub Actions."

Review hardware requirements

The CPU and memory resources available to your GitHub Enterprise Server instance determine the number of jobs that can be run concurrently without performance loss. GitHub recomienda un mínimo de 8 vCPU y 64 GB de memoria para ejecutar GitHub Actions.

The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations:

vCPUMemoriaSimultaneidad máxima
864 GB300 trabajos
16128 GB700 trabajos
32160 GB1500 trabajos
64256 GB2500 trabajos
96384 GB4500 trabajos
128550 GB5000 trabajos

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.

If you plan to enable GitHub Actions for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of GitHub Enterprise Server, see "Monitoring your appliance."

For more information about minimum hardware requirements for your GitHub Enterprise Server instance, see the hardware considerations for your instance's platform.

Para más información sobre cómo ajustar los recursos de una instancia existente, vea "Aumento de la capacidad de almacenamiento" y "Aumento de los recursos de CPU o memoria".

External storage requirements

To enable GitHub Actions on GitHub Enterprise Server, you must have access to external blob storage.

GitHub Actions uses blob storage to store data generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of GitHub Actions. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time.

GitHub Actions supports these storage providers:

  • Azure Blob storage
  • Amazon S3
  • S3-compatible MinIO cluster

Note: These are the only storage providers that GitHub supports and can provide assistance with.

Hay otros productos de almacenamiento compatibles con la API de S3 que los partners de GitHub han autovalidado como compatibles con GitHub Actions en GitHub Enterprise Server. Para obtener más información, consulta el repositorio de partners de almacenamiento de GHES.

En el caso de los productos de almacenamiento validados a través del programa de asociación tecnológica GitHub, el proveedor de almacenamiento es responsable del soporte técnico y la documentación para usar el producto de almacenamiento con GitHub Actions.

Networking considerations

Si se habilitan las GitHub Actions para tu empresa, solo los proxies HTTP serán compatibles. No se admiten los servidores proxy SOCKS5 y HTTPS. For more information about using a proxy with GitHub Enterprise Server, see "Configuring an outbound web proxy server."

Enabling GitHub Actions with your storage provider

Follow one of the procedures below to enable GitHub Actions with your chosen storage provider:

Managing access permissions for GitHub Actions in your enterprise

You can use policies to manage access to GitHub Actions. For more information, see "Enforcing GitHub Actions policies for your enterprise."

Adding self-hosted runners

Nota: Actualmente los ejecutores hospedados en GitHub no se admiten en GitHub Enterprise Server. Puede ver más información sobre la compatibilidad futura planeada en GitHub public roadmap.

To run GitHub Actions workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "Adding self-hosted runners."

Managing which actions can be used in your enterprise

You can control which actions your users are allowed to use in your enterprise. This includes setting up GitHub Connect for automatic access to actions from GitHub.com, or manually syncing actions from GitHub.com.

For more information, see "About using actions in your enterprise."

Fortalecimiento de seguridad general para las GitHub Actions

Si quiere más información sobre los procedimientos de seguridad para GitHub Actions, vea "Fortalecimiento de la seguridad para GitHub Actions".

Reserved names

When you enable GitHub Actions for your enterprise, two organizations are created: github and actions. If your enterprise already uses the github organization name, github-org (or github-github-org if github-org is also in use) will be used instead. If your enterprise already uses the actions organization name, github-actions (or github-actions-org if github-actions is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore.