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.
CloudBees CD supports the creation, versioning, deployment, required middleware, and infrastructure details for a complete release package. You can model and version applications, microservices, and environments to orchestrate the software release flow and also to standardize and automate the deployment of applications or microservices between environments.
CloudBees CD deploy 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. The model can be broken into these parts of your application or microservice deployment:
What—You are deploying the application or microservice, which contains references to the files being deployed.
Where—The application or microservice will be deployed to a CloudBees CD environment.
How—You run processes that orchestrate deployment tasks to deploy the application or microservice to the environment.