CI/CD

You can set up continuous integration and continuous deployment (CI/CD) for your Workers by using either the integrated build system, Workers Builds, or using external providers to optimize your development workflow.

Why use CI/CD?

Using a CI/CD pipeline to deploy your Workers is a best practice because it:

• Automates the build and deployment process, removing the need for manual wrangler deploy commands.
• Ensures consistent builds and deployments across your team by using the same source control management (SCM) system.
• Reduces variability and errors by deploying in a uniform environment.
• Simplifies managing access to production credentials.

Which CI/CD should I use?

Choose Workers Builds if you want a fully integrated solution within Cloudflare's ecosystem that requires minimal setup and configuration for GitHub or GitLab users.

We recommend using external CI/CD providers if:

• You have a self-hosted instance of GitHub or GitLabs, which is currently not supported in Workers Builds' Git integration
• You are using a Git provider that is not GitHub or GitLab

Workers Builds

Workers Builds is Cloudflare's native CI/CD system that allows you to integrate with GitHub or GitLab to automatically deploy changes with each new push to a selected branch (e.g. main).

Ready to streamline your Workers deployments? Get started with Workers Builds.

External CI/CD

You can also choose to set up your CI/CD pipeline with an external provider.

• GitHub Actions
• GitLab CI/CD