Skip to main content

About continuous deployment

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

Observação: no momento, não há suporte para os executores hospedados no GitHub no GitHub Enterprise Server. Você pode ver mais informações sobre o suporte futuro planejado no GitHub public roadmap.

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

Starter workflows and third party actions

GitHub Enterprise Server oferece fluxos de trabalho iniciantes de implantação para vários serviços populares, como o aplicativo Azure Web. Para saber como começar a usar um fluxo de trabalho inicial, confira "Como usar fluxos de trabalho iniciais" ou navegue pela lista completa de fluxos de trabalho iniciais de implantação. Confira também nossos guias mais detalhados de fluxos de trabalho de implantação específicos, como "Implantação no Serviço de Aplicativo do Azure".

Muitos prestadores de serviço também oferecem ações em GitHub Marketplace para implantar no seu serviço. Para ver a lista completa, confira GitHub Marketplace.

Further reading