Continuous integration, delivery, deployment

Continuous integration (Continuous integrationI)

Is a software engineering process, are all integrated into one kind of software engineers continue initiatives to share the main line (mainline) for the working copy of the software.

The purpose is to allow fast iteration of the product, while maintaining high quality.

The core measure is before the code is integrated into the trunk, you must pass the test automation. As long as there is a test case fails, it can not be integrated.

 

Continuous Delivery (Continuous delivery)

Frequently the new version of the software, delivered to the quality of the team or the user, for review. If the review by the code to enter the production stage.

Continuous integration can be seen as the next step, it is emphasized that no matter how updated version of the software can be delivered anytime, anywhere.

 

Continuous deployment (continuous deployment)

The next step is the continuous delivery, by referring to the code after the review, automated deployment to production.

The goal is the code that can be deployed at any one time is, you can enter the production stage.

If it is able to complete the test automation, build, deploy, and other steps.

Guess you like

Origin www.cnblogs.com/tongyishu/p/11682104.html