1. Overview of CICD and Jenkins
The development and release of Internet software has formed a set of standard procedures. If the development workflow is divided into the following stages:
Coding → Build → Integration → Testing → Delivery → Deployment
As seen in the figure above, Continuous Integration, Continuous Delivery and Continuous Deployment have different software automation delivery cycles.
1. Continuous Integration (CI)
The most important part of the entire process above is continuous integration (CI for short):
Coding → Build → Integration → Test
Continuous integration refers to frequent (multiple times a day) integration of code into the mainline. Deliver the part of the software developed by the individual to the overall part of the software, and integrate it frequently so that errors can be found faster.
It has two main benefits:
- Spot errors quickly. Every time a little update is completed, it is integrated into the backbone, which can quickly find errors and make it easier to locate errors;
- Prevent branches from deviating significantly from the trunk. If it is not integrated frequently and the backbone is constantly updated, it will make it more difficult to integrate in the future, or even difficult to integrate;
Continuous integration does not eliminate bugs, but makes them very easy to find and correct. The purpose of continuous integration is to allow products to iterate quickly while maintaining high quality. Its core measure is that the code must pass automated tests before it is integrated into the backbone. As long as a single test case fails, it cannot be integrated.