title

intro

versions

type

redirect_from

topics

Continuous deployment

You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.

fpt	ghes	ghec
*	*	*

overview

/actions/deployment/about-continuous-deployment

/actions/deployment/about-deployments/about-continuous-deployment

/actions/deployment/about-deployments

/actions/about-github-actions/about-continuous-deployment

/actions/about-github-actions/about-continuous-deployment-with-github-actions

/actions/concepts/overview/about-continuous-deployment-with-github-actions

/actions/concepts/overview/continuous-deployment

CD

{% data reusables.actions.enterprise-github-hosted-runners %}

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 AUTOTITLE.

About continuous deployment using {% data variables.product.prodname_actions %}

You can set up a {% data variables.product.prodname_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 an 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 AUTOTITLE.

{% data variables.product.prodname_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 AUTOTITLE and AUTOTITLE.

Workflow templates and third-party actions

{% data reusables.actions.cd-templates-actions %}

Next steps

If your {% data variables.product.prodname_actions %} 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. This will let you stop storing these credentials as long-lived secrets and provide other security benefits. For more information, see AUTOTITLE.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!