About continuous deployment

You can create custom continuous deployment (CD) workflows directly in your GitHub repository with GitHub Actions.

Nota: Los ejecutores hospedados en GitHub no son compatibles con GitHub Enterprise Server actualmente. Puedes encontrar más información sobre el soporte que se tiene planeado en el futuro en el Itinerario público de GitHub.

About continuous deployment

Continuous deployment (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment.

Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "About continuous integration".

About continuous deployment using GitHub Actions

You can set up a GitHub Actions workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying.

You can configure your CD workflow to run when a GitHub Enterprise Server event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "Events that trigger workflows."

GitHub Actions provides features that give you more 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. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "Deploying with GitHub Actions" and "Using environments for deployment."

Workflow templates and third party actions

GitHub Enterprise Server ofrece plantillas de flujo de trabajo de DC para varios servicios populares, tal como Azure Web App. Para aprender cómo comenzar a utilizar una plantilla de flujo de trabajo, consulta la sección "Utilizar plantillas de flujo de trabajo" o busca en la lista completa de plantillas de flujo de trabajo de despliegue. También puedes verificar nuestras guías más detalladas para flujos de trabajo de despliegue específicos, tal como "Desplegar hacia Azure App Service".

Muchos proveedores de servicio también ofrecen acciones en GitHub Marketplace para desplegar a su servicio. Para encontrar la lista completa, consulta GitHub Marketplace.

Further reading

¿Te ayudó este documento?

Política de privacidad

¡Ayúdanos a hacer geniales estos documentos!

Todos los documentos de GitHub son de código abierto. ¿Notas algo que esté mal o que no sea claro? Emite una solicitud de cambios.

Haz una contribución

O, aprende cómo contribuir.