You should know something about ci/cd

【 precondition ： You are already in Linux It's finished Jenkins And the corresponding plugin】

Step1： sketch CI/CD

(1)、 The assembly line in the factory is fast 、 automation 、 Produce consumer goods from raw materials in a repeatable way . Again , Software delivery pipeline to fast 、 Automated and repeatable way to generate releases from source .

(2)、 How to complete the overall design of this work is called “ Continuous delivery ”（CD）.

(3)、 The process of starting an assembly line is called “ Continuous integration ”（CI）.

Continuous integration (Continuous integration) It's a software development practice , That is, team development members often integrate their work , Integrate at least once a day by each member , This means that multiple integrations may occur each day . Each integration is through an automated build （ Including the compilation , Release , automated testing ） To verify , This enables early detection of integration errors .

(4)、 The process of ensuring quality is called “ Keep testing ”.

(5)、 The process of making the final product available to users is called “ Continuous deployment ”.

Continuous deployment （continuous deployment） It's through automated builds 、 Test and deploy cycles to deliver quality products quickly . Sort of represents the extent to which a development team is engineered , After all, fast - moving Internet companies cost more people than machines , Investment machine optimization and development process has relatively improved the efficiency of people , Give Way engineering productivity Maximize .

Some experts make it easy 、 smooth 、 Run efficiently , These people are called O & M development (DevOps) Practitioner .

Step2： What I'm using here is “Scripted Pipeline”

It has two syntax modes: scripted and declarative , Script mode is more powerful , Declarative syntax is more concise .

A scripted code is designed as follows ：

Step3： The effect picture after running