About GitHub Actions for enterprises
GitHub Actions permite los usuarios que usen tu instancia de GitHub Enterprise Server mejorar la productividad mediante la automatización de todas las fases del flujo de trabajo de desarrollo de software.
| Task | More information |
|---|---|
| Automatically test and build your application | "Acerca de la integración continua" |
| Deploy your application | "Acerca del despliegue contínuo" |
| Automatically and securely package code into artifacts and containers | "Acerca del empaquetado con Acciones de GitHub" |
| Automate your project management tasks | "Utilizar GitHub Actions para la administración de proyectos" |
GitHub Actions helps your team work faster at scale. When large repositories start using GitHub Actions, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "Writing and shipping code faster" in the State of the Octoverse.
You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. You can restrict your developers to using actions that exist on tu instancia de GitHub Enterprise Server, or you can allow your developers to access actions on GitHub.com. For more information, see "About using actions in your enterprise."
GitHub Actions is developer friendly, because it's integrated directly into the familiar GitHub Enterprise Server experience.
You can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see "Acerca de los ejecutores autohospedados."
GitHub Actions provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. OIDC provides security benefits such as eliminating the need to store credentials as long-lived secrets. For more information, see "Acerca del fortalecimiento de seguridad con OpenID Connect."
GitHub Actions also includes tools to govern your enterprise's software development cycle and meet compliance obligations. For more information, see "Enforcing policies for GitHub Actions in your enterprise."
About getting started with GitHub Actions
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 «Introducing GitHub Actions to your enterprise».
Si estás migrando tu empresa a las GitHub Actions desde otro proveedor, hay consideraciones adicionales. Para obtener más información, vea «Migrating your enterprise to GitHub Actions».
GitHub Actions no está habilitado para GitHub Enterprise Server de manera predeterminada. After you finish planning, you can follow the instructions for enabling GitHub Actions. For example, you may need to upgrade the CPU and memory resources for tu instancia de GitHub Enterprise Server. For more information, see "Getting started with GitHub Actions for GitHub Enterprise Server."