A cloud platform-based DevOps continuous integration delivery system

Abstract

The application belongs to the technical field of Internet software development and operation and maintenance, and particularly relates to a DevOps continuous integration and delivery system based on a cloud platform, which comprises a project management module and a product library module; through integration of the advantages of elastic computing, high availability and automatic management of cloud computing and the concept of integration of agile development and operation and maintenance of DevOps, a full-automatic system from code submission to production deployment of software development is realized.

Description

Technical Field

[0001] The present invention belongs to the technical field of Internet software development and operation and maintenance, and specifically relates to a DevOps continuous integration and delivery system based on a cloud platform. Background Art

[0002] With the rapid development of cloud computing, the boundaries between software development and operations are becoming increasingly blurred, creating an urgent need for efficient, automated continuous integration and delivery processes. Traditional development and operations models suffer from poor communication, long delivery cycles, and difficulty ensuring quality. Cloud computing, with its elasticity, scalability, and on-demand services, provides powerful infrastructure support for software development and operations. DevOps technology breaks down the barriers between development and operations, integrating close collaboration and automated processes across development, testing, and operations to improve software delivery efficiency and quality. Summary of the Invention

[0003] In view of this, the present invention provides a DevOps continuous integration delivery system based on a cloud platform, which aims to realize a fully automated system for software development from code submission to production deployment by integrating the elastic computing, high availability and automated management advantages of cloud computing with the agile development and operation and maintenance integration concept of DevOps.

[0004] The technical solution of the present invention:

[0005] A cloud-based DevOps continuous integration and delivery system, including a project management module and an artifact library module;

[0006] The project management module is used to plan, execute, and monitor all projects, including project information tables, operation and maintenance cloud platform management, development libraries, operation and maintenance libraries, and test libraries;

[0007] The artifact library module serves as a centralized storage platform for storing and managing components and documents related to software delivery, including environment and tool installation packages, development domain artifacts, test domain artifacts, and production domain artifacts.

[0008] The project management module and the artifact library module interact based on pipeline scripts, which implement the distribution of environment packages and intermediate artifacts as well as the continuous integration and delivery of codes; wherein the environment packages are delivered based on the CI pipeline, and the intermediate artifacts are delivered based on the CD pipeline.

[0009] Furthermore, the operation process of the continuous integration delivery system includes the following steps:

[0010] S1: Break down the software requirements and issues of the project, and distribute the tasks through requirement sheets or issue sheets in the project management module;

[0011] S2: Configure the cloud computing platform as the operation support of the DevOps system;

[0012] S:3: Iteratively develop project code based on requirements or issues;

[0013] S4: Execute the CI pipeline to compile the submitted code, perform code static checking, perform unit testing, and package the image;

[0014] S5: Execute the CD pipeline, pull intermediate artifacts, deploy environment packages, perform system testing, and release artifacts;

[0015] S6: Conduct detailed testing on the project system and transfer the artifacts from the development domain environment to the test domain environment;

[0016] S7: After the product passes the test, it is transferred from the test domain to the production domain, the release record is saved, and the deployment is completed in the production domain.

[0017] Furthermore, the development library is used to store the code written by developers, the corresponding version of the product, and the corresponding branch information of the product. Each development library contains a CI pipeline; when the developer makes changes to the code based on the requirement form or problem form, the code is submitted to the development library, which automatically triggers the pipeline to perform continuous integration operations.

[0018] Furthermore, the operation and maintenance library is used to maintain the CI pipeline scripts and CD pipeline scripts written by the operation and maintenance personnel. The CI pipeline scripts and CD pipeline scripts are stored in the CI library and CD library respectively; each product of the project corresponds to a CI pipeline, and each project corresponds to a CD pipeline.

[0019] Furthermore, the test library is used to maintain the automated test code, use cases, and test documents written by testers. When the code is submitted to the development library or the CD pipeline is started, the test code is pulled into the environment, deployed, and run.

[0020] Furthermore, the environment and tool installation packages are used to store the environment and tool installation packages required for all projects. Project-related personnel can manually download and install the environment and tools from the artifact library module. The CI pipeline scripts and CD pipeline scripts can be automatically downloaded to the execution node through the network interface.

[0021] Furthermore, the permissions for computing nodes and products are limited to development, testing, and production;

[0022] The development domain is limited to developers, who build new environments based on their needs to verify their development artifacts.

[0023] The test domain is limited to testers. Testers build the environment according to the requirements document and systematically verify the final product. After the test, the results are archived in the test domain.

[0024] Limit the production domain to be used by users;

[0025] The CI pipeline script and the CD pipeline script are executed based on the cloud computing nodes of the cloud computing platform.

[0026] Furthermore, the development library, test library, and operation and maintenance library are all set up with different branches, and different branches correspond to different projects.

[0027] Furthermore, the specific process of the development library executing the CI pipeline is as follows:

[0028] S4.1 Environment Pull: Pull the compilation environment compressed package from the artifact library and build the compilation environment locally;

[0029] S4.2 CI code pull: pull the latest version of the CI script from the operation and maintenance configuration library to the local specified directory;

[0030] S4.3 Code Pull: Pull the latest version of the code to the local specified directory;

[0031] S4.4 Compile: Execute the compilation script and compile the code into binary;

[0032] S4.5 Static Check: Call the scanning tool API to scan the code and return the result of whether the scan passes;

[0033] S4.6 Unit testing: Execute unit test cases and return test results;

[0034] S4.7 Upload products: Upload the compiled products to the corresponding path of the product library.

[0035] Furthermore, the specific process of the operation and maintenance library executing the CD pipeline is as follows:

[0036] S5.1 Pull artifacts: Pull the project artifacts that need to be tested from the artifact library;

[0037] S5.2 Deploy the system: Deploy components to each node and build the system according to deployment requirements;

[0038] S5.3 Pull test code: Pull the corresponding test code from the test code library according to the project model and version;

[0039] S5.4 System Test: Initialize the test code and execute system test. The pipeline user can skip some test cases by configuring keywords.

[0040] S5.5 release: After all test processes are passed, the product will be uploaded to the product library delivery installation package directory, and the product usage document will be written and attached with the test result report.

[0041] Beneficial effects of the present invention:

[0042] The present invention builds a bridge connecting DevOps and project management. Each iteration cycle realizes the automated management of the entire process of project-product-requirement / problem-code, which greatly improves product quality and team efficiency. Three code bases are established respectively: development, operation and maintenance, and testing. The responsibilities of different project personnel are effectively divided, and strict authority management and access control policies are implemented to effectively prevent unauthorized access and operations. More comprehensive automated testing can be performed through the pipeline, including unit testing, integration testing, regression testing, and performance testing, etc., to ensure that each code change can be fully verified to discover and fix potential problems. With the elastic expansion capability provided by the cloud computing platform, pipeline resources can be automatically expanded or resized according to actual needs, avoiding resource waste and complex capacity planning, and better helping enterprises reduce operation and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0044] Figure 1 This is a diagram of the architecture of the present invention;

[0045] Figure 2 1 is an execution flow chart of the present invention. DETAILED DESCRIPTION

[0046] The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0047] The following describes the embodiments of the present disclosure through specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present disclosure. It should be noted that, in the absence of conflict, the following embodiments and features in the embodiments can be combined with each other. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

[0048] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein can be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on this disclosure, it should be understood by those skilled in the art that an aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects described herein can be used to implement an apparatus and / or practice a method. In addition, other structures and / or functionalities other than one or more of the aspects described herein can be used to implement this apparatus and / or practice this method.

[0049] It should also be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present disclosure. The illustrations only show components related to the present disclosure and are not drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component can be changed at will, and the component layout type may also be more complicated.

[0050] Additionally, in the following description, specific details are provided to provide a thorough understanding of the examples. However, one skilled in the art will appreciate that the aspects described can be practiced without these specific details.

[0051] In one embodiment of the present invention, a DevOps continuous integration delivery system based on a cloud platform is proposed, comprising a project management module and an artifact library module;

[0052] The project management module is used to plan, execute, and monitor all projects, including project information tables, operation and maintenance cloud platform management, development libraries, operation and maintenance libraries, and test libraries;

[0053] The artifact library module serves as a centralized storage platform for storing and managing components and documents related to software delivery, including environment and tool installation packages, development domain artifacts, test domain artifacts, and production domain artifacts.

[0054] The project management module and the artifact library module interact based on pipeline scripts, which implement the distribution of environment packages and intermediate artifacts as well as the continuous integration and delivery of codes; wherein the environment packages are delivered based on the CI pipeline, and the intermediate artifacts are delivered based on the CD pipeline.

[0055] In this embodiment, the operation process of the continuous integration delivery system includes the following steps:

[0056] S1: Break down the software requirements and issues of the project, and distribute the tasks through requirement sheets or issue sheets in the project management module;

[0057] S2: Configure the cloud computing platform as the operation support of the DevOps system;

[0058] S3: Iteratively develop project code based on requirements or issues;

[0059] S4: Execute the CI pipeline to compile the submitted code, perform code static checking, perform unit testing, and package the image;

[0060] S5: Execute the CD pipeline, pull intermediate artifacts, deploy environment packages, perform system testing, and release artifacts;

[0061] S6: Conduct detailed testing on the project system and transfer the artifacts from the development domain environment to the test domain environment;

[0062] S7: After the product passes the test, it is transferred from the test domain to the production domain, the release record is saved, and the deployment is completed in the production domain.

[0063] In this embodiment, the development library is used to store the code written by developers, the corresponding version of the product, and the corresponding branch information of the product. Each development library contains a CI pipeline; when the developer makes changes to the code based on the requirement form or problem form, the code is submitted to the development library, which automatically triggers the pipeline to perform continuous integration operations.

[0064] In this embodiment, the operation and maintenance library is used to maintain the CI pipeline scripts and CD pipeline scripts written by the operator. The CI pipeline scripts and CD pipeline scripts are stored in the CI library and CD library respectively; each product of the project corresponds to a CI pipeline, and each project corresponds to a CD pipeline.

[0065] In this embodiment, the test library is used to maintain the automated test code, use cases and test documents written by the tester. When the code is submitted to the development library or the CD pipeline is started, the test code is pulled into the environment, deployed and run.

[0066] In this embodiment, the environment and tool installation packages are used to store the environment and tool installation packages required for all projects. Project-related personnel can manually download and install the environment and tools from the product library module. The CI pipeline script and CD pipeline script can be automatically downloaded to the execution node through the network interface.

[0067] In this embodiment, the permissions for computing nodes and products are limited to development, testing, and production;

[0068] The development domain is limited to developers, who build new environments based on their needs to verify their development artifacts.

[0069] The test domain is limited to testers. Testers build the environment according to the requirements document and systematically verify the final product. After the test, the results are archived in the test domain.

[0070] Limit the production domain to be used by users;

[0071] The CI pipeline script and the CD pipeline script are executed based on the cloud computing nodes of the cloud computing platform.

[0072] In this embodiment, the development library, the test library, and the operation and maintenance library are all provided with different branches, and different branches correspond to different projects.

[0073] In this embodiment, the specific process of the development library executing the CI pipeline is as follows:

[0074] S4.1 Environment Pull: Pull the compilation environment compressed package from the artifact library and build the compilation environment locally;

[0075] S4.2 CI code pull: pull the latest version of the CI script from the operation and maintenance configuration library to the local specified directory;

[0076] S4.3 Code Pull: Pull the latest version of the code to the local specified directory;

[0077] S4.4 Compile: Execute the compilation script and compile the code into binary;

[0078] S4.5 Static Check: Call the scanning tool API to scan the code and return the result of whether the scan passes;

[0079] S4.6 Unit testing: Execute unit test cases and return test results;

[0080] S4.7 Upload products: Upload the compiled products to the corresponding path of the product library.

[0081] In this embodiment, the specific process of the operation and maintenance library executing the CD pipeline is as follows:

[0082] S5.1 Pull artifacts: Pull the project artifacts that need to be tested from the artifact library;

[0083] S5.2 Deploy the system: Deploy components to each node and build the system according to deployment requirements;

[0084] S5.3 Pull test code: Pull the corresponding test code from the test code library according to the project model and version;

[0085] S5.4 System Test: Initialize the test code and execute system test. The pipeline user can skip some test cases by configuring keywords.

[0086] S5.5 release: After all test processes are passed, the product will be uploaded to the product library delivery installation package directory, and the product usage document will be written and attached with the test result report.

[0087] In this embodiment, continuous integration (Continuois Integration) and continuous delivery (Continuous Delivery) are referred to as CI / CD. Continuous integration builds and integrates different parts of the software into a repository for unified verification and testing. Continuous delivery is to deploy the tested code to the production environment on the basis of continuous integration to ensure that the final product is released on time and reliably. Through the automated pipeline built by CI / CD, project-related personnel can sustainably perform construction, integration, deployment, testing and verification, timely discover and fix defects in the software, improve the quality and stability of the software, thereby significantly improving the speed of software iteration and reducing manual intervention and waiting time. At the same time, the present invention makes use of the elastic computing resources provided by the cloud computing platform, and can automatically adjust the number of execution pipeline nodes according to demand to meet the daily development and operation and maintenance needs of large-scale projects.

[0088] The structure of this embodiment is as follows Figure 1 As shown, the project management system is divided into five modules: project information table, operation and maintenance cloud platform management, development library, operation and maintenance library, and test library. The artifact library is divided into four modules: environment and tool installation package, development domain artifact, test domain artifact, and production domain artifact. The specific responsibilities of each module are as follows:

[0089] The project information table is used to maintain all project information of the entire team, mainly including: project name, information of members involved in the project, project application model or Party A information, project version information, product information included in the project, development library path corresponding to each product, product requirements list and problem list.

[0090] The operation and maintenance cloud platform management is used to manage the cluster of the execution pipeline, mainly recording the information of the execution nodes and the configuration information of the cluster. The operation and maintenance personnel can dynamically adjust the capacity parameters of the elastic scaling resources of the cloud platform, and monitor the operating status of the cloud platform in real time, so as to promptly detect faults and problems and handle them.

[0091] The development library is used to store the versions and branch information corresponding to the code written by developers and the products. Each development library contains a CI pipeline. When the developer makes changes to the code based on the requirements or problem tickets and submits them to the development library, the pipeline will be automatically triggered to perform continuous integration operations.

[0092] The operations library is used to maintain the CI and CD pipeline scripts written by operations personnel, which are stored in the CI library and CD library respectively. Each product corresponds to a CI pipeline, and each project corresponds to a CD pipeline.

[0093] The test library is used to maintain the automated test code, use cases, and test documents written by testers. When the code is submitted to the development library or the CD pipeline is started, the tester's code will be pulled into the environment, deployed, and run.

[0094] The environment and tool installation library is used to store the environment and tool installation packages required for all projects. Project-related personnel can manually download and install them from the library, and the CI / CD pipeline can also automatically download and install them to the execution node through the network interface.

[0095] There are three product control domains: development, testing, and production. The development domain is used by developers, who can flexibly build new environments based on requirements to verify development artifacts. The testing domain is used by testers, who strictly build environments according to requirements documents and systematically verify the final product. After testing, the results must be archived in the testing domain. The production domain is used by users, and each environment deployment and product release requires strict approval.

[0096] The execution process of the present invention is as follows Figure 2 The specific usage is as follows:

[0097] S1: The project manager performs routine maintenance on the project information table, breaks down software requirements and issues, and distributes them to developers via requirement tickets and issue tickets on the project management system.

[0098] S2: Operations personnel configure the operation and maintenance cluster, and cloud computing nodes are used to execute CI and CD scripts;

[0099] S3: Developers iteratively develop the code based on the requirements or issues, and submit the code to the corresponding branch of the development library after development.

[0100] S4: The development library automatically executes the CI pipeline. The specific process is as follows:

[0101] Environment pull: Pull the compilation environment compressed package from the artifact library and build the compilation environment locally;

[0102] CI code pull: pull the latest version of the CI script from the operation and maintenance configuration library to the local specified directory;

[0103] Code pull: pull the latest version of the code to the local specified directory;

[0104] Compile: execute the compilation script and compile the code into binary;

[0105] Static check: Call the scanning tool API to scan the code and return the result of whether the scan passes;

[0106] Unit testing: execute unit test cases and return test results;

[0107] Upload artifacts: Upload the compiled artifacts to the corresponding path of the artifact library.

[0108] S5: After the code passes the CI pipeline, the operation and maintenance library executes the CD pipeline. The specific process is as follows:

[0109] Pull artifacts: Pull the project artifacts that need to be tested from the artifact library;

[0110] Deploy the system: deploy components to each node and build the system according to deployment requirements;

[0111] Pull test code: Pull the corresponding test code from the test code library according to the project model and version;

[0112] System testing: Initialize the test code and execute system testing (pipeline users can skip certain test cases by configuring keywords);

[0113] Release: After all test processes are passed, the product will be uploaded to the product library delivery installation package directory, and the product usage document will be written and attached with the test result report.

[0114] S6: After the project completes an iteration, testers conduct detailed testing of the system, and the artifacts and environment are transferred from the development domain to the test domain.

[0115] S7: After the tester completes comprehensive testing, the artifact can be transferred from the test domain to the production domain, the release record can be saved, and the deployment can be completed in the production domain.

[0116] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A DevOps continuous integration delivery system based on a cloud platform, characterized by: Includes project management module and product library module; The project management module is used to plan, execute, and monitor all projects, including project information tables, operation and maintenance cloud platform management, development libraries, operation and maintenance libraries, and test libraries; The artifact library module serves as a centralized storage platform for storing and managing components and documents related to software delivery, including environment and tool installation packages, development domain artifacts, test domain artifacts, and production domain artifacts. The project management module interacts with the artifact library module based on pipeline scripts, which implement the distribution of environment packages and intermediate artifacts as well as the continuous integration and delivery of codes; The environment package is delivered based on the CI pipeline, and the intermediate products are delivered based on the CD pipeline; The operation process of the continuous integration delivery system includes the following steps: S1: Break down the software requirements and issues of the project, and distribute the tasks through requirement sheets or issue sheets in the project management module; S2: Configure the cloud computing platform as the operation support of the DevOps system; S3: Iteratively develop project code based on requirements or issues; S4: Execute the CI pipeline to compile the submitted code, perform code static checking, perform unit testing, and package the image; S5: Execute the CD pipeline, pull intermediate artifacts, deploy environment packages, perform system testing, and release artifacts; S6: Conduct detailed testing on the project system and transfer the artifacts from the development domain environment to the test domain environment; S7: After the product passes the test, it is transferred from the test domain to the production domain, the release record is saved, and the deployment is completed in the production domain.

2. The DevOps continuous integration delivery system based on a cloud platform according to claim 1, characterized in that: The development library is used to store the code written by developers, the corresponding version of the product, and the corresponding branch information of the product. Each development library contains a CI pipeline; when the developer makes changes to the code based on the requirement or problem ticket, the code is submitted to the development library, which automatically triggers the pipeline to perform continuous integration operations.

3. The cloud platform-based DevOps continuous integration delivery system according to claim 2, characterized in that: The operation and maintenance library is used to maintain the CI pipeline scripts and CD pipeline scripts written by the operation and maintenance personnel. The CI pipeline scripts and CD pipeline scripts are stored in the CI library and CD library respectively; each product of the project corresponds to a CI pipeline, and each project corresponds to a CD pipeline.

4. The cloud platform-based DevOps continuous integration delivery system according to claim 3, characterized in that: The test library is used to maintain the automated test code, use cases, and test documents written by testers. When the code is submitted to the development library or the CD pipeline is started, the test code is pulled into the environment, deployed, and run.

5. The cloud platform-based DevOps continuous integration delivery system according to claim 4, characterized in that: The environment and tool installation packages are used to store the environment and tool installation packages required for all projects. Project-related personnel manually download and install the environment and tools from the artifact library module. The CI pipeline scripts and CD pipeline scripts can be automatically downloaded to the execution node through the network interface.

6. The cloud platform-based DevOps continuous integration delivery system according to claim 5, characterized in that: Limit the permissions for computing nodes and products to development, testing, and production; The development domain is limited to developers, who build new environments based on their needs to verify their development artifacts. The test domain is limited to testers. Testers build the environment according to the requirements document and systematically verify the final product. After the test, the results are archived in the test domain. Limit the production domain to be used by users; The CI pipeline script and the CD pipeline script are executed based on the cloud computing nodes of the cloud computing platform.

7. The cloud platform-based DevOps continuous integration delivery system according to claim 6, characterized in that: The development library, test library, and operation and maintenance library all have different branches, and different branches correspond to different projects.

8. The cloud platform-based DevOps continuous integration delivery system according to claim 7, characterized in that: The specific process of executing the CI pipeline in the development library is as follows: S4.1 Environment Pull: Pull the compilation environment compressed package from the artifact library and build the compilation environment locally; S4.2 CI code pull: pull the latest version of the CI script from the operation and maintenance configuration library to the local specified directory; S4.3 Code Pull: Pull the latest version of the code to the local specified directory; S4.4 Compile: Execute the compilation script and compile the code into binary; S4.5 Static Check: Call the scanning tool API to scan the code and return the result of whether the scan passes; S4.6 Unit testing: Execute unit test cases and return test results; S4.7 Upload products: Upload the compiled products to the corresponding path of the product library.

9. The cloud platform-based DevOps continuous integration delivery system according to claim 8, characterized in that: The specific process of the operation and maintenance library executing the CD pipeline is as follows: S5.1 Pull artifacts: Pull the project artifacts that need to be tested from the artifact library; S5.2 Deploy the system: Deploy components to each node and build the system according to deployment requirements; S5.3 Pull test code: Pull the corresponding test code from the test code library according to the project model and version; S5.4 System Test: Initialize the test code and execute system test, where the pipeline user skips certain test cases through configuration keywords; S5.5 release: After all test processes are passed, the product will be uploaded to the product library delivery installation package directory, and the product usage document will be written and attached with the test result report.

Images