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

Original articles, welcome to reprint. Reprint please indicate: reproduced from IT Story Association, thank you!

Original link address: "Advanced articles" docker understanding CICD and DevOps (41)

I have already said that mesos,swarm,k8s has been deployed, but I did not deploy K8s because of machine problems. With the basis of micro-service and service orchestration, we can learn about CICD and DevOps together. As mentioned in the intermediate article, let's review and study together.

The generation of it

Compilation failed

Out of pain, small companies are understaffed. Developers need to deal with bug and development tasks every day. When they reached a stage, I said that bug repair was ready for testing. I told QA,QA to enter the intranet to execute the deployed script, publish it to the test environment, tell me that the release failed, tell the compiler that there was an error, and that the error code was written by someone else. I need to call someone else to see whose problem it is. Soon one of them said that he had forgotten to submit a class and told me after submitting the code that I told QA that it was ready to republish. At first, everyone put up with it once or twice, but later found that careless old guys often made mistakes of this or that. Some people failed to submit a class or a configuration less, so I thought of a way to find a dedicated server. Each time the code is submitted, a webhook is triggered to repeat the code, and if a compilation error is found, the corresponding code submitter is compiled, which is the initial continuous integration. (veteran drivers may have met, in fact, this is the earliest continuous integration)

Runtime exception

Although the previous compilation exception has been solved, the runtime exception has been highlighted again, so on this basis, we have added the code style check, unit test, coverage, and add the Alibaba coding specification plug-in. Here, I would like to complain. It is said that the code specification is for outsiders, but insiders do not abide by it. In fact, the specification is very good, compliance and style unity is conducive to maintenance, do not dig holes, old man.

Publish manually

For new projects, apply for resources, apply for ports, and configure nginx. The old project is not simple, there is no operation and maintenance in second-tier cities, stop offline services.

Manual deployment

Upload code, restart, verify, go online. In fact, it is repetitive work, but this job needs very news. In case you meet a stupid rm-rf, everyone will drink from the west.

Pain point optimization above

Slowly optimize from the details, optimize each link, in order to make the process smoother and more elegant, this is the origin of CICD.

Learn about CICD and DevOps

CI is continuous integration. CD is continuously deployed.

CI

In traditional software, integration is basically the final phase of the project, and it takes us weeks or months. Continuous integration is to advance the integration, to the development stage, while developing while integrating. A process that allows build and testing to be repeated frequently. Continuous integration typically involves multiple developers writing code for the same product at the same time. Put the code in a source database, and then the developer builds and integrates through a CI-server tool. First of all, continuous integration requires developers to test their own code and test their own code separately to ensure that they can work properly, and the test becomes a unit test. When all the code passed smoothly, I thought they were integrated smoothly. The performance of the code is also expected. The advantage is that integration is no longer a headache, and the software is writing integration all the time. Before continuous integration, the development of software was carried out uniformly to the end. I don't know how long it will take, but CI is about integrating our integration into our day-to-day work.

CD

Continuous deployment is based on continuous integration, and continuous deployment means that developers test the code in other environments as they develop and test it. Deployment in different environments is usually called deployment pipeline. Our company's deployment pipeline: development environment, test environment, quasi-production environment, production environment. According to different companies, different products, different teams, all the code will pass the previous test before entering the next assembly line. In this way, after the developer submits the code, it is done automatically. This process is called continuous deployment.

DevOps

Better to optimize the development, operation and maintenance, testing process. Make the development and operation and maintenance through highly automated tools to make the software release and construction more fast, frequent and reliable. Devops is actually an extension of the idea of CICD. Without CICD, DevOps is actually a castle in the air. It doesn't make sense. CICD optimizes all aspects of development and operation and maintenance testing based on it. DevOps contains a lot of things, and there are a variety of landing plans.

PS:CICD and DevOps have a better understanding, next time start to do an environmental running practice for CICD.

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.