Docker container technology-based continuous integration realizing method

Abstract

The invention relates to a Docker container technology-based continuous integration realizing method. The method comprises the following steps: 1) obtaining a native mirror image; 2) setting a container cluster tool which is used for managing Docker containers; 3) executing the native mirror image, generating a Docker container and configuring related environment parameters; 4) deploying a client plugin of a continuous integration system by the Docker container to ensure that the Docker container becomes a client node; and 5) obtaining information of the client node by a server of the continuous integration system and configuring construction information of the client node to complete the construction task. Compared with the prior art, the method has the advantages of reducing the hardware investment cost and simplifying the continuous integration environment deployment.

Description

technical field [0001] The invention relates to the field of computer software development, in particular to a continuous integration implementation method based on docker container technology. Background technique [0002] As the complexity of software development continues to increase, how to better collaborate among team members to ensure the quality of software development has gradually become an unavoidable problem in the development process. Especially in recent years, agile development has become more and more popular in the field of software engineering, and how to quickly adapt to and ensure the quality of software in the changing needs is also particularly important. [0003] Continuous integration is a software development practice for this type of problem. It advocates that team development members must integrate their work frequently, and integration may even occur multiple times per day. Each integration is verified through automated builds, including automat...

AI Technical Summary

Problems solved by technology

In order to ensure that the software packages of all operating systems are built on demand in a timely manner, the software is usually divided into more than a dozen sub-modules to be built separately, and a set of environments must be prepared for the operating system corresponding to each module. In theory, it is the fastest to build a Software package, the number of required build machines can easily reach more than 100, the required hardware costs are high, and deployment is time-consuming and laborious

[0009] And there is still a big problem, that is, if you need to roll back the code to a certain version and then build a software package, you need to clean up the original environment, download the corresponding code version and start building, it takes a long time, and when you need to return to the mainline version In order to ensure timeliness, we usually choose to deploy another build environment to build the specified code version at any time, which means that the number of build machines described above needs to be doubled, and will Often idle, no matter for any company, it is a huge waste

Images