1.CICD background;
With the development of Internet software and publishing, demand the formation of a set of standard processes, development processes can be divided into the following phases:
→ → → Integrated construct encoding test → → delivery deployment
2. Continuous Integration (Continuous integration, referred to as CI);
(N times or several times a day) often integrated into the trunk code. The part of the software development of individual software to deliver an integral part, often integrated in order to find the mistake faster.
3. Continuous Delivery (Continuous delivery)
It refers frequently to 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.
In the continuous delivery of continuous integration on the basis of the code is deployed to integrate closer to real operating environment of "production-like environment" (production-like environments) in. Continuous delivery in preference to the software throughout the product lifecycle deployment, built on a high level of automated continuous integration.
4. continuous deployment (continuous deployment, the CD)
The next step is the continuous delivery, by referring to the code after the review, automated deployment to production. Continuous deployment goal is that the code can be deployed at any one time is, you can enter the production stage. Continued deployment if you are able to complete the test automation, build, deploy, and other steps.
5.CICD summary
Continuous integration, continuous delivery, continued deployment provides an excellent DevOps environment. For the entire development team, can greatly enhance the development efficiency, the benefits and challenges in parallel. In any case, frequent deployment, fast delivery and the development of testing process automation will become an important part of the future of software engineering.
6.CICD mainstream programs;
