Continuous Deployment (CD) in software development

Continuous Deployment describes the continuous deployment of changes to an application on a server that the customer cannot access. Through the continuous deployment the test team can always check the latest version of the software.

A Continuous Deployment pipeline can be implemented with the help of CI/CD servers like Jenkins.

Differentiation between Continuous Delivery and Continuous Deployment

In difference to Continuous Delivery, Continuous Deployment does not deliver each change to the customer automatically. Each change gets deployed on a server and can be tested there manually. That means that the degree of automation of Continuous Deployment is lower than Continuous Delivery.

Compared to Continuous Integration, the automation is higher, because the latest version is always ready to be tested. In Continuous Integration that is not the case.

Continuous Deployment with the Cloudogu EcoSystem (CES)

To implement a Continuous Deployment pipeline with the Cloudogu EcoSystem you only have to provide a deployment target for Jenkins.

Cloudogu EcoSystem Download

Download Cloudogu EcoSystem

Would you like to set up the CES independently? No problem, we provide you with a free download for the Community Edition.

Download CES