Self-Serviceable Continuous Deployment (CD) Pipelines On Choreo

We’re excited to share that self-serviceable continuous deployment (CD) pipelines are now generally available in Choreo. This feature builds on Choreo’s multi-environment, multi-cluster capabilities and gives platform teams even greater control over deployment workflows.

What are CD pipelines in Choreo?

Choreo’s CD pipelines follow "build once and promote". This means container images are built only once per commit or tag, and then promoted across multiple environments (e.g., development, staging, and production). During promotion, only environment-specific configurations—such as environment variables or file mounts—are applied at runtime.

This strategy ensures that deployments are reproducible, reversible, and avoids issues commonly caused by building separate container images for each environment, which are mostly caused by subtle changes in dependencies pulled from external sources during duplicated builds that are out of your control.

In Choreo, the ordering of environments through which an image is promoted defines a CD pipeline. These pipelines support deployment to environments across multiple data planes (multi-cluster) and even across different cloud providers (multi-cloud), enabling flexible and reliable delivery across complex infrastructure setups.

What’s new?

Before March 2025, Choreo supported dynamic environment creation and allowed you to define a single deployment pipeline—an ordered list of environments applied globally across all projects within an organization.

With the introduction of this feature, CD pipelines are now a first-class concept in Choreo, allowing platform engineering teams to:

• Define multiple CD pipelines via a UI-based editor

Platform engineers can define as many CD pipelines as needed for their organizations using the Choreo Console. They can also set a default deployment pipeline, ensuring that all newly created projects automatically have access to it from the start.

• Platform engineering perspective:

Figure 1: Defining a new CD pipeline for the organization.

• Development perspective:

Figure 2: Using the attached CD pipeline of a project in the deploy view.

• Selectively attach CD pipelines to projects

Not all teams and projects need access to all the environments in an organization. Projects can now selectively deploy to specific environments by attaching the relevant CD pipelines.

Project administrators can choose to attach or detach CD pipelines available in their organization to their projects, granting project teams more control over their CI/CD processes.

Figure 3: Selectively attach CD pipelines to projects

Conclusion

Choreo’s new CD pipelines feature empowers platform engineering teams with greater flexibility and control over their deployment workflows. With the ability to define multiple pipelines, selectively attach them to projects, and promote builds seamlessly across environments, teams can now streamline their CI/CD processes more effectively than ever. We encourage you to explore this feature and see how it can enhance your deployment strategy. To learn more, check out our documentation and try it out in Choreo today!