49 lines
2.9 KiB
Markdown
49 lines
2.9 KiB
Markdown
---
|
|
title: About continuous deployment with GitHub Actions
|
|
shortTitle: Continuous deployment
|
|
intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
|
|
versions:
|
|
fpt: '*'
|
|
ghes: '*'
|
|
ghec: '*'
|
|
type: overview
|
|
redirect_from:
|
|
- /actions/deployment/about-continuous-deployment
|
|
- /actions/deployment/about-deployments/about-continuous-deployment
|
|
- /actions/deployment/about-deployments
|
|
- /actions/about-github-actions/about-continuous-deployment
|
|
topics:
|
|
- 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](/actions/automating-builds-and-tests/about-continuous-integration).
|
|
|
|
## 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](/actions/using-workflows/events-that-trigger-workflows).
|
|
|
|
{% 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](/actions/deployment/about-deployments/deploying-with-github-actions) and [AUTOTITLE](/actions/deployment/targeting-different-environments/managing-environments-for-deployment).
|
|
|
|
## Using OpenID Connect to access cloud resources
|
|
|
|
{% data reusables.actions.about-oidc-short-overview %}
|
|
|
|
## Workflow templates and third party actions
|
|
|
|
{% data reusables.actions.cd-templates-actions %}
|
|
|
|
## Further reading
|
|
|
|
* [AUTOTITLE](/actions/use-cases-and-examples/deploying)
|
|
* [AUTOTITLE](/actions/deployment/about-deployments/deploying-with-github-actions)
|
|
* [AUTOTITLE](/actions/deployment/targeting-different-environments/managing-environments-for-deployment){% ifversion fpt or ghec %}
|
|
* [AUTOTITLE](/billing/managing-billing-for-github-actions){% endif %}
|