Shulou(Shulou.com)06/02 Report--

1.CICD background

Continuous Integration (Continuous Integration) is a kind of software development practice, which provides a theoretical basis for improving software development efficiency and ensuring software development quality. Jenkins is an open source software project that aims to provide an open and easy-to-use software platform that makes continuous integration possible. This paper starts with the basic concept of continuous integration and introduces how to quickly build a continuous integration environment based on Jenkins through specific examples. Significance of continuous integration

1) any link in continuous integration is completed automatically without too much human intervention, which helps to reduce the repetitive process to save time, cost and workload.

2) continuous integration ensures that the code submitted by team members at each point in time can be integrated successfully. In other words, software integration problems can be found at any point in time, making it possible to release deployable software at any time.

3) continuous integration is also conducive to the development trend of the software itself, which is especially important in situations where requirements are unclear or change frequently. The quality of continuous integration can help the team to make effective decisions and build the team's confidence in the development product.

A set of standard processes that can divide the development workflow into the following phases:

Coding → to build → Integration → Test → delivery → deployment

two。 Continuous integration (Continuous integration, CI)

Integrate code into the trunk frequently (multiple or N times a day). Deliver the part of the personal development of the software to the whole part of the software, and integrate it frequently in order to find the errors more quickly.

3. Continuous delivery (Continuous delivery)

Refers to the frequent delivery of new versions of software to quality teams or users for review. If the review passes, the code goes into production.

Continuous delivery deploys the integrated code to a "production-like environment" (production-like environments) that is closer to the real running environment on the basis of continuous integration. Continuous delivery takes precedence over software deployment throughout the product lifecycle and is based on a high level of automated continuous integration.

4. Continuous deployment (continuous deployment, referred to as CD)

Is the next step in continuous delivery, which means that the code is automatically deployed to the production environment after it has been reviewed. The goal of continuous deployment is that the code is deployable at any time and can go into production. The premise of continuous deployment is to automate the steps of testing, building, deployment, and so on.

5.CICD summary

Continuous integration, continuous delivery, and continuous deployment provide an excellent DevOps environment. For the whole development team, it can greatly improve the development efficiency, and the benefits go hand in hand with the challenges. In any case, frequent deployment, rapid delivery and development test process automation will be an important part of future software engineering.

6.CICD mainstream scheme

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.