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. Para obtener más información acerca de la integración contínua, consulta la sección "Acerca de la Integración Contínua".
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 AE 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."
GitHub AE offers CD starter workflow for several popular services, such as Azure Web App. To learn how to get started using a starter workflow, see "Using starter workflows" or browse the full list of deployment starter workflows. 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.