The purpose of Continuous delivery is to be able to quickly deliver customizations and extensions of your project to production, without interrupting the work of the Live environment, without having downtime, or without the need to manually merge configurations or databases. You ensure your application functions as expected using thorough automation tests on a production-like environment. Propelling the changes through the environments is automated, which makes it more reliable.
The main goal of the process is that after every development iteration, you end up with the same setup, which you started with - code is the same on all environments, the latest database is on the Live environment.
The following chart displays a simplified overview of a Continuous delivery process:
PREREQUISITES: Before using Continuous delivery, you must have set it up. For more information, see Setup the Continuous delivery process.
After all tests pass successfully, export the changes from your Development environment, using Export and deploy code changes, and import them to your Live environment.
All code changes, configuration changes, and changes to the database schema are automatically handles.
RESULT: You have the latest development uploaded to Live. Live environment has not been down and is running with the most current database. All of your environments have the latest code.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity