1. Continuous integration
Continuous integration refers to integrating code into the trunk frequently (multiple times a day).
It has two main benefits:
(1) Quickly detect errors. Every time a little update is completed, it is integrated into the backbone, which can quickly find errors and locate errors more easily.
(2) 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.
The purpose of continuous integration is to enable products to be iterated quickly while maintaining high quality. Its core measure is that before the code is integrated into the trunk, it must pass automated testing. As long as one test case fails, it cannot be integrated.
2. Continuous delivery
Continuous delivery refers to frequently delivering new versions of software to the quality team or users for review. If the review passes, the code goes into production.
Continuous delivery can be seen as the next step in continuous integration. It emphasizes that no matter how it is updated, the software can be delivered anytime and anywhere.
3. Continuous deployment
- Definition: Continuous deployment is the next step of continuous delivery, which refers to the automatic deployment to the production environment after the code passes the review.
- Goal: Code is deployable and ready for production at any time.
- Prerequisite: Able to automatically complete testing, construction, deployment and other steps.
4. Introduction to Jenkins
1. Jenkins concept
Jenkins is an open source software project and an extensible continuous integration tool developed based on Java. It is mainly used to continuously and automatically build/test/integrate software projects and monitor some regularly executed tasks.