Advanced, Model-Based Deployment

Advanced Model-Based Deployment separates the What, Where, and How of release orchestration to allow targeting a different endpoint, like Google GCP or Amazon AWS, without needing to change the process or the payload. It provides CloudBees CD users different deployment and rollback strategies out of the box, like blue/green, canary, or component vs. whole, plus the flexibility to schedule deployments based on resource availability or block-out dates. It also helps in troubleshooting, auditing, and planning with fine-grained visibility into exactly what is deployed in each environment - from application version down to artifact version. Advanced Model-Based Deployment drives application and deployment master component reuse to foster standardized, auditable practices and repeatable enterprise-wide deployment processes. Deployments in previous stages will be repeated exactly in Production.

Quick links

Troubleshooting

Model-based deployment to any environment

CloudBees CD makes deployments manageable, reproducible, and error-proof by modeling the application or microservice, the environments to which it will be deployed, and automating the workflow needed for the deployment. Environments are modeled using resources that are statically defined on the system, dynamically spun up at deployment time, or a combination of both.

Microservices and container orchestration

CloudBees CD brings the application release automation practices of modeling, automation, and coordination to containers and microservices. This model-based solution avoids cloud provider or container lock-in by separating application models from environment models that are platform specific.

Automated roll back

When an application process has a predefined rollback step and the application deployment fails, CloudBees CD automatically reverses what was deployed up to the failure point in the process flow.

Environments on demand

Environments can be static, dynamic, or hybrid. Environments can have a combination of static and cloud resources that are provisioned and configured dynamically.

Reusable components

Use master components to create a library of standardized prebuilt components, which can help to promote best practices across the enterprise. Application authoring can be streamlined by leveraging these prebuilt components and corresponding component-process logic.

Advanced deployment strategies

CloudBees CD provides several ways to deploy applications, including deployment policies such as rolling deployments, blue/green, canary, and dark launch and deployment options such as smart deploy, staging artifacts, and error handling.

Environment inventory and drift tracking

When troubleshooting or auditing, you can directly compare inventories of two environments such as a pre-production environment to a production environment to determine the degree to which the environments have drifted.