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

How to understand DevOps, CI and CD? in view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

DevOps

DevOps, a combination of Development and Operations, is a methodology and a group of processes, methods and systems, which are used to promote communication, cooperation and integration among application development, application operation and maintenance and quality assurance (QA) departments. With a view to breaking down the barriers and gaps between traditional development and operation.

DevOps is a culture, sport, or practice that values communication and cooperation between "software developers (Dev)" and "IT operation and maintenance technicians (Ops)". Build, test, and release software more quickly, frequently and reliably by automating the process of "software delivery" and "architecture change". Specifically, it is to improve the efficiency of communication and collaboration in the process of software delivery and deployment, in order to release higher quality products faster and more reliably.

In other words, DevOps is a general term for a set of processes and methods, and does not refer to a particular software tool or combination of software tools. A variety of tools or combinations of software can implement the conceptual approach of DevOps. Its essence is a complete set of methodology, not a collection of certain tools. Similar to OOP, AOP, IOC (or DI) designed in software development, it is an abstraction or pronoun of a theory or process or method.

CI

The English name of CI is Continuous Integration, and its Chinese translation is continuous integration.

In CI, developers will frequently submit code to the trunk, and these newly committed code will need to be compiled and validated by automated test streams before they are finally merged into the trunk.

Continuous integration (CI) is the process of automatically detecting, pulling, building, and (in most cases) unit testing after source code changes. The goal of continuous integration is to quickly ensure that newly submitted changes by developers are good and suitable for further use in the code base. The process execution and theoretical practice of CI allow us to determine whether the new code and the original code can be properly integrated.

CD

CD can correspond to multiple English names for continuous delivery of Continuous Delivery and continuous deployment of Continuous Deployment, which are described below.

Looking up some data, the concepts of continuous interaction and continuous deployment are confusing, and the following concept summary is based on most of the data.

Continuous delivery

After completing the automated process of building and unit and integration testing in CI, continuous delivery automatically publishes the validated code to the repository. In order to achieve an efficient continuous delivery process, it is important to ensure that CI is built into the development pipeline. The goal of continuous delivery is to have a code base that can be deployed to a production environment at any time.

In continuous delivery, each phase (from the merging of code changes to the delivery of production-ready builds) involves test automation and code release automation. At the end of the process, the operations team can quickly and easily deploy the application to the production environment or release it to the end-user.

Continuous deployment

For a mature CI/CD pipeline (Pipeline), the final phase is continuous deployment. As an extension of continuous delivery, which automatically releases production-ready builds to the code repository, continuous deployment can automatically release applications to the production environment.

Continuous deployment means that all changes are automatically deployed to the production environment. Continuous delivery means that all changes can be deployed to a production environment, but for business reasons, you can choose not to deploy. If you want to implement continuous deployment, you must first implement continuous delivery.

Continuous delivery does not mean that every change to the software should be deployed to the production environment as soon as possible, it means that any code change can be deployed at any time.

Continuous delivery represents a capability, while continuous deployment represents a way. Continuous deployment is the highest stage of continuous delivery.

Agile Development

Another concept, the so-called agile development, doesn't seem to have an acronym yet, and it seems to be abused at home. Agile development focuses on a development approach that embraces change and rapid iteration. How to achieve agile development, it seems that there is no perfect tool chain at present, but it is more of a concept, another way to tease the saying that "you want a horse to run fast and not to eat grass."

The picture above reveals some of the connotations and goals of agile development, which seems to be a bit of real nonsense.

CI, CD, DevOps relationship

Everyone has a different understanding of the conceptual content. Just like the word CGI, which can be understood as a protocol like CGI or a software tool that implements the CGI protocol, there is no problem. Leave a picture:

This is the answer to the question about how to understand DevOps, CI and CD. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

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.