Pipeline deployment method, device, equipment and storage medium
By adding code version information to the pipeline version control system and using target requests to trigger tasks, and executing pipeline tasks in combination with the plug-in interface, the problem of low pipeline deployment efficiency is solved, and more efficient task execution and parallel processing is achieved.
Patent Information
- Application Number
- CN202410073990.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-18
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2044-01-18
AI Technical Summary
In the prior art, pipeline deployment efficiency is low, resulting in low efficiency in performing tasks based on pipelines, especially efficiency bottlenecks caused by differences in writing automation scripts in tasks with complex requirements.
The version control system of the pipeline adds version information to the code, uses the target request to trigger the pipeline task, and executes it in an independent container, calls the plug-in interface to execute the task, and automatically triggers the execution of the next task, improving the parallelism and efficiency of the pipeline task .
It improves the efficiency of pipeline deployment and task execution efficiency, simplifies the execution process of pipeline tasks, and enhances the processing ability of complex tasks.
Smart Images

Figure CN117992077B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a pipeline deployment method, device, equipment and storage medium. Background Art
[0002] Automatic deployment of the pipeline means that all commands are automatically executed by the computer during deployment. The user only executes the start trigger of the command, and the decision-making operation is left to the computer to execute, rather than driving the manual execution of each command.
[0003] In the prior art, the automatic deployment process for the pipeline is mainly based on the pipeline, and the automatic deployment is achieved by writing an automated script. However, due to the differences in the writing ability of technicians who write automated scripts, for tasks with more complex requirements, the deployment efficiency of pipeline deployment by writing automated scripts is low, resulting in low efficiency in executing tasks based on the pipeline. Summary of the invention
[0004] The present invention provides a pipeline deployment method, device, equipment and storage medium to solve the defect of low pipeline deployment efficiency in the prior art, which leads to low efficiency of executing tasks based on the pipeline, and improves the efficiency of executing tasks based on the pipeline.
[0005] In a first aspect, the present invention provides a pipeline deployment method, the method comprising:
[0006] Using a version control system of a pipeline, adding code version information to a first code submitted to the version control system, to obtain the first code after the code version information is added; the pipeline is obtained according to at least one plug-in, and any of the plug-ins is obtained according to a pipeline task in the pipeline;
[0007] According to the first code after adding the code version information, at least one of the pipeline tasks in the pipeline is triggered by using a target request; the target request is triggered based on a tag push event containing the code version information; each of the pipeline tasks is executed in an independent container;
[0008] For any of the pipeline tasks, calling the plug-in interface corresponding to the pipeline task, and executing the pipeline task according to the target request; the plug-in interface is an interface pre-registered in the engine of the pipeline;
[0009] For any of the pipeline tasks, when the pipeline task is completed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0010] Optionally, the pipeline task includes at least one of the following: code compilation and construction, packaging of test environment images, generation of test deployment packages, deployment of the test deployment packages to the test environment, automated testing, manual testing, packaging of production environment images, generation of production deployment packages, and deployment of the production deployment packages to the pre-production environment.
[0011] Optionally, for any of the pipeline tasks, calling a plug-in interface corresponding to the pipeline task, and executing the pipeline task according to the target request includes:
[0012] For any of the pipeline tasks, determining a second code corresponding to the pipeline task according to the target request;
[0013] Determine the value of the input parameter of the pipeline task according to the second code corresponding to the pipeline task;
[0014] Utilizing the plug-in interface corresponding to the pipeline task, the output result corresponding to the pipeline task is obtained according to the value of the input parameter of the pipeline task; the plug-in interface corresponding to the pipeline task includes at least one input parameter corresponding to the pipeline task and the output result corresponding to the pipeline task.
[0015] Optionally, when the pipeline task is a packaged test environment image, the value of the input parameter of the pipeline task is the container image configuration code corresponding to the second code; the using the plug-in interface corresponding to the pipeline task, according to the value of the input parameter of the pipeline task, to obtain the output result corresponding to the pipeline task, includes:
[0016] Pulling the container image configuration code corresponding to the second code from the version control system using the plug-in interface corresponding to the pipeline task;
[0017] Determine the image version information corresponding to the container image configuration code corresponding to the second code by using the plug-in interface corresponding to the pipeline task;
[0018] Utilize the plug-in interface corresponding to the pipeline task, build the container image according to the container image configuration code corresponding to the second code, and obtain the test environment image corresponding to the second code.
[0019] Optionally, when the pipeline task is to generate a test deployment package, the value of the input parameter of the pipeline task is the container cluster configuration file corresponding to the second code in the version control system; the using of the plug-in interface corresponding to the pipeline task, according to the value of the input parameter of the pipeline task, to obtain the output result corresponding to the pipeline task, includes:
[0020] Using the plug-in interface corresponding to the pipeline task, pull the container cluster configuration file corresponding to the second code in the version control system;
[0021] Using the plug-in interface corresponding to the pipeline task, the image version information in the container cluster configuration file corresponding to the second code is updated, and the updated container cluster configuration file corresponding to the second code is pushed to the version control system;
[0022] The test deployment package is generated by utilizing the plug-in interface corresponding to the pipeline task and according to the container cluster configuration file corresponding to the updated second code.
[0023] Optionally, when the pipeline task is an automated test, the values of the input parameters of the pipeline task are the test data set and the test objects in the test deployment package; the using of the plug-in interface corresponding to the pipeline task, according to the values of the input parameters of the pipeline task, to obtain the output result corresponding to the pipeline task, includes:
[0024] Using the plug-in interface corresponding to the pipeline task, the machine learning model is trained according to the test data set and a preset fitness function to obtain a test case generation model;
[0025] The test case generation model is used to generate a test report according to the test objects in the test deployment package.
[0026] Optionally, the version control system includes a trigger, and the trigger is used to trigger the execution of the pipeline task.
[0027] In a second aspect, the present invention further provides a pipeline deployment device, the device comprising:
[0028] A version management module, used to use a version control system of a pipeline to add code version information to a first code submitted to the version control system, so as to obtain the first code after the code version information is added; the pipeline is obtained according to at least one plug-in, and any of the plug-ins is obtained according to a pipeline task in the pipeline;
[0029] A task triggering module, configured to trigger at least one of the pipeline tasks in the pipeline using a target request according to the first code after adding the code version information; the target request is triggered based on a tag push event containing the code version information; each of the pipeline tasks is executed in an independent container;
[0030] A task execution module, for calling a plug-in interface corresponding to any of the pipeline tasks, and executing the pipeline task according to the target request; the plug-in interface is an interface pre-registered in the engine of the pipeline;
[0031] For any of the pipeline tasks, when the pipeline task is completed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0032] In a third aspect, the present invention further provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the pipeline deployment method described above is implemented.
[0033] In a fourth aspect, the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements any of the above-described pipeline deployment methods.
[0034] In a fifth aspect, the present invention further provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the pipeline deployment method as described in any one of the above is implemented.
[0035] The present invention provides a pipeline deployment method, device, equipment and storage medium. By using the version control system of the pipeline, code version information is added to the first code submitted to the version control system to obtain the first code after the code version information is added, wherein the pipeline is obtained according to at least one plug-in, and any plug-in is obtained according to the pipeline task in the pipeline; then, according to the first code after the code version information is added, at least one pipeline task in the pipeline is triggered by a target request, wherein the target request is triggered based on a tag push event containing the code version information; each pipeline task is executed in an independent container; then, for any pipeline task, the plug-in interface corresponding to the pipeline task is called, and the pipeline task is executed according to the target request; the plug-in interface is an interface pre-registered in the pipeline engine; for any pipeline task, when the pipeline task is executed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0036] In the present invention, a plug-in is generated according to at least one pipeline task, and then each plug-in is deployed to the pipeline. When the pipeline task needs to be executed, the execution of the pipeline task is achieved by calling the plug-in interface corresponding to the pipeline task. The deployment efficiency of the pipeline based on the embodiment of the present invention is relatively high, thereby improving the efficiency of executing tasks based on the pipeline. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0038] Figure 1 It is one of the flow diagrams of the pipeline deployment method provided by the present invention;
[0039] Figure 2 It is a schematic diagram of the principle of the plug-in pipeline provided by the present invention;
[0040] Figure 3 This is the third flow chart of the pipeline deployment method provided by the present invention;
[0041] Figure 4 It is a structural schematic diagram of the assembly line deployment device provided by the present invention;
[0042] Figure 5 It is a structural schematic diagram of the electronic device provided by the present invention. DETAILED DESCRIPTION
[0043] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0044] Combine the following Figure 1-Figure 5 The present invention describes the pipeline deployment method, device, equipment and storage medium provided by the present invention.
[0045] Figure 1 This is one of the flow diagrams of the pipeline deployment method provided by the present invention. As shown in the figure, the method includes:
[0046] Step 101: using a pipeline version control system, adding code version information to a first code submitted to the version control system, to obtain the first code after the code version information is added; the pipeline is obtained according to at least one plug-in, and any plug-in is obtained according to a pipeline task in the pipeline;
[0047] Specifically, it should be noted that the execution subject of the present invention is any electronic device that can execute the pipeline deployment method.
[0048] In this embodiment, the version control system of the pipeline can be used to manage the code, i.e., version control, such as gitlab, github, etc. For example, the code version information is added to the first code submitted to the version control system to obtain the first code after the code version information is added.
[0049] Step 102: according to the first code after adding the code version information, at least one pipeline task in the pipeline is triggered by using a target request; the target request is triggered based on a tag push event containing the code version information; each pipeline task is executed in an independent container;
[0050] Specifically, when it is necessary to run the pipeline, the target request can be used to trigger at least one pipeline task in the pipeline, wherein the target request contains at least the first code after adding the code version information. It can be understood that the target request is triggered based on the tag push event containing the code version information, that is, the Tag push event can be pre-set to trigger the Webhook, and then the target request such as the Webhook request triggers at least one pipeline task in the pipeline. Optionally, in some embodiments, a specific identifier can be pre-added to the target request, and the specific identifier is used to distinguish the trigger request of the overall build pipeline task, such as build=all, indicating the request for the overall build. Next, add a logic to the continuous integration / continuous deployment continuous delivery CI / CD configuration file, and add a judgment condition to the CI / CD configuration file of the project. If a webhook request with a specific identifier is detected, the corresponding build task is triggered. At the same time, by using the Drone tool, the process is configured in the form of a YAML file (.drone.yml), and the Git event can be listened to to automatically trigger the build process, so that the build process configuration is convenient and easy to understand.
[0051] Each pipeline task is executed in an independent container, that is, each build step is executed in a temporary container Docker, which allows different pipeline build tasks to be executed in parallel without affecting each other, thus improving the build efficiency. For example, you can add the following steps in the configuration file of each sub-project:
[0052]
[0053] Step 103: for any pipeline task, call the plug-in interface corresponding to the pipeline task, and execute the pipeline task according to the target request; the plug-in interface is an interface pre-registered in the pipeline engine;
[0054] Specifically, it should be noted that the pipeline tasks included in the pipeline in the embodiment of the present invention can be made into a plug-in in advance according to the task requirements and registered in the pipeline engine. When the pipeline is running, that is, when the pipeline task needs to be executed, the pipeline task can be implemented by calling the plug-in interface of the pipeline task, that is, the plug-in interface of the pipeline task is an interface pre-registered in the pipeline engine. Among them, the process of making the pipeline task into a plug-in is as follows:
[0055] First, according to each pipeline task in the pipeline, the common functions corresponding to the pipeline task can be made into plug-ins, where the plug-ins can be customized to meet different business needs and scenario requirements. For example, first, define the plug-in interface of each pipeline task in the pipeline, including input parameters and output results, so as to ensure the compatibility and interchangeability between plug-ins;
[0056] Secondly, according to the defined pipeline task plug-in interface, develop specific plug-in implementations. Each plug-in is responsible for completing specific pipeline tasks, such as code compilation, testing, packaging, deployment, etc. Each plug-in can be independently developed and maintained, and can be implemented using different programming languages and technology stacks.
[0057] Finally, when the pipeline is running, the plug-in needs to be registered with the pipeline engine, which can be achieved through configuration files, annotations, or dynamic loading.
[0058] For example, Figure 2 It is a schematic diagram of the principle of the plug-in pipeline provided by the present invention, such as Figure 2 As shown, custom pipeline tasks such as code pulling are made into code pulling plug-ins, custom pipeline tasks such as code building are made into code building plug-ins, custom pipeline tasks such as code scanning are made into code scanning plug-ins, and custom pipeline tasks such as image generation are made into image generation plug-ins. Other pipeline tasks can also be made into plug-in form and registered in the pipeline engine.
[0059] Furthermore, when the pipeline is running, for any pipeline task, the pipeline task can be executed by calling the plug-in interface corresponding to the pipeline task and according to the target request of triggering the pipeline task. For example, in the case where the pipeline task is to package the test environment image, the pipeline task is executed by calling the plug-in interface corresponding to the package test environment image and according to the target request of triggering the package test environment image pipeline task; for another example, in the case where the pipeline task is to generate a test deployment package, the pipeline task is executed by calling the plug-in interface corresponding to the generated test deployment package and according to the target request of triggering the generated test deployment package pipeline task; for another example, in the case where the pipeline task is automated testing, the pipeline task is executed by calling the plug-in interface corresponding to the automated testing and according to the target request of triggering the automated testing pipeline task.
[0060] Step 104: for any pipeline task, when the pipeline task is completed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0061] Specifically, for the pipeline deployed in this implementation, the completion of each pipeline task in the pipeline triggers the execution of the next pipeline task, which can be operated by triggering. For example, the following is an example of a trigger written in Python script:
[0062] import jenkins
[0063] #Connect to the Jenkins server
[0064] server=jenkins.Jenkins('http: / / jenkins-server-url')
[0065] #Trigger the execution of the next pipeline
[0066] server.build_job('NextPipelineJob')
[0067] In the example above, the jenkins library is used to connect to the Jenkins server and the build_job method is used to trigger the execution of the next pipeline job named NextPipelineJob.
[0068] In the method provided in this embodiment, by utilizing the version control system of the pipeline, code version information is added to the first code submitted to the version control system to obtain the first code after the code version information is added, wherein the pipeline is obtained according to at least one plug-in, and any plug-in is obtained according to the pipeline task in the pipeline; then, according to the first code after the code version information is added, at least one pipeline task in the pipeline is triggered by using a target request, wherein the target request is triggered based on a tag push event containing the code version information; each pipeline task is executed in an independent container; further, for any pipeline task, the plug-in interface corresponding to the pipeline task is called, and the pipeline task is executed according to the target request; the plug-in interface is an interface pre-registered in the pipeline engine; for any pipeline task, when the pipeline task is executed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0069] In the present invention, a plug-in is generated according to at least one pipeline task, and then each plug-in is deployed to the pipeline. When the pipeline task needs to be executed, the execution of the pipeline task is achieved by calling the plug-in interface corresponding to the pipeline task. The deployment efficiency of the pipeline deployed based on the embodiment of the present invention is high, thereby improving the efficiency of software development based on the pipeline.
[0070] Optionally, the pipeline task includes at least one of the following: code compilation and construction, packaging of test environment images, generation of test deployment packages, deployment of test deployment packages to the test environment, automated testing, manual testing, packaging of production environment images, generation of production deployment packages, and deployment of production deployment packages to the pre-production environment.
[0071] Specifically, it can be understood that in some embodiments, pipeline tasks can be obtained based on software development tasks, for example, pipeline tasks include code compilation and construction, packaging of test environment images, generation of test deployment packages, deployment of test deployment packages to test environments, automated testing, manual testing, packaging of production environment images, generation of production deployment packages, and deployment of production deployment packages to pre-production environments.
[0072] Among them, code compilation and construction can be understood as the process of using a compiler to generate a target program from a source program written in a source language; packaging a test environment image refers to the process of generating a test image, which is used to test the program in a test environment; generating a test deployment refers to generating a chart package based on the test image; other pipeline tasks are not described here.
[0073] In the method provided in this embodiment, the pipeline tasks include, for example, code compilation and construction, packaging of test environment images, generation of test deployment packages, deployment of test deployment packages to the test environment, automated testing, manual testing, packaging of production environment images, generation of production deployment packages, deployment of production deployment packages to the pre-production environment, etc. A plug-in can be made for each pipeline task, and the execution efficiency of pipeline tasks based on the plug-in is higher.
[0074] Optionally, for any pipeline task, call the plug-in interface corresponding to the pipeline task, and execute the pipeline task according to the target request, including:
[0075] For any pipeline task, according to the target request, determine the second code corresponding to the pipeline task;
[0076] Determine the value of the input parameter of the pipeline task according to the second code corresponding to the pipeline task;
[0077] Using the plug-in interface corresponding to the pipeline task, the output result corresponding to the pipeline task is obtained according to the value of the input parameter of the pipeline task; the plug-in interface corresponding to the pipeline task includes at least one input parameter corresponding to the pipeline task and the output result corresponding to the pipeline task.
[0078] Specifically, it should be noted that before plug-inizing the pipeline task and implementing the execution of the pipeline task by calling the plug-in interface, the plug-in configuration of container management can be performed; for example, on the plug-in management page of the continuous integration tool Jenkins, search and install the "Kubernetes Plugin" container cluster plug-in; on the global configuration page of Jenkins, find the "Kubernetes" section; click the "Add Kubernetes Cloud" container cloud button; configure the name of the container cluster, API Server address, API Server login credentials, the namespace where the executor automatically creates, the maximum number of executors to start, the Pod selector label, the execution timeout of the Pod and other information; in the Kubernetes cluster, create a container Docker image for running the Jenkins agent, where this container image contains the necessary components and tools of the Jenkins agent. When running the Jenkins task, Jenkins will use the container cluster Kubernetes plug-in to create a Pod in the Kubernetes cluster and start the Jenkins agent container in the Pod to run the build. It is understandable that the executor will be automatically destroyed after the pipeline task is executed.
[0079] In some embodiments, step 103 may be implemented as follows:
[0080] First, for any pipeline task, the second code corresponding to the pipeline task is determined according to the target request; wherein the target request is, for example, a Webhook request, and the target request is triggered by a tag push event containing code version information, for example, a Webhook request is triggered by a tag push event in advance, and it can be understood that the Webhook request contains the corresponding version information of the code. For each pipeline task, the second code corresponding to the pipeline task can be first determined according to the code version information in the target request.
[0081] Furthermore, according to the second code corresponding to the pipeline task determined above, the value of the input parameter corresponding to the pipeline task can be determined; it can be understood that the plug-in interface corresponding to the pipeline task includes at least one input parameter corresponding to the pipeline task and the output result corresponding to the pipeline task.
[0082] Furthermore, the plug-in interface corresponding to the pipeline task can be utilized to obtain the output result corresponding to the pipeline task according to the value of the input parameter of the pipeline task. For example, the plug-in interface corresponding to the pipeline task can be called to obtain the output result corresponding to the pipeline task based on the value of the input parameter of the pipeline task. That is, the execution of the pipeline task is achieved by calling the plug-in interface corresponding to the pipeline task.
[0083] In the method provided in this embodiment, for any pipeline task, first, the second code corresponding to the pipeline task can be determined according to the target request that triggers the pipeline task; then, the value of the input parameter of the pipeline task is determined according to the second code corresponding to the pipeline task; and then, the output result corresponding to the pipeline task is obtained according to the value of the input parameter of the pipeline task by using the plug-in interface corresponding to the pipeline task, that is, the execution of the pipeline task is realized. In this embodiment, by calling the plug-in interface corresponding to the pipeline task, the execution efficiency of the pipeline task can be higher, and the execution method is relatively simple.
[0084] Optionally, when the pipeline task is to package the test environment image, the value of the input parameter of the pipeline task is the container image configuration code corresponding to the second code; using the plug-in interface corresponding to the pipeline task, according to the value of the input parameter of the pipeline task, the output result corresponding to the pipeline task is obtained, including:
[0085] Using the plug-in interface corresponding to the pipeline task, pull the container image configuration code corresponding to the second code from the version control system;
[0086] Determine the image version information corresponding to the container image configuration code corresponding to the second code by using the plug-in interface corresponding to the pipeline task;
[0087] By utilizing the plug-in interface corresponding to the pipeline task and according to the container image configuration code corresponding to the second code, the container image is constructed to obtain the test environment image corresponding to the second code.
[0088] Specifically, when the pipeline task is to package the test environment image, the value of the input parameter of the pipeline task is the container image configuration code corresponding to the second code. Correspondingly, in some embodiments, step 103 can be implemented as follows:
[0089] First, the plug-in interface corresponding to the pipeline task, that is, the plug-in interface corresponding to the packaging test environment image pipeline task, is used to pull the container image configuration code corresponding to the second code from the version control system; further, the plug-in interface corresponding to the packaging test environment image pipeline task is used to determine the image version information corresponding to the container image configuration code corresponding to the second code; further, the plug-in interface corresponding to the packaging test environment image pipeline task is used to build the container image according to the container image configuration code corresponding to the second code, and obtain the test environment image corresponding to the second code. For example, the plug-in interface corresponding to the packaging test environment image pipeline task is used to pull the container Docker image construction configuration code in the version control system such as GitLab, and the python script "product release unique number" is used as the image tag Tag of the container Docker image. The container Docker image is built through the image building tool Kaniko, and the built container image can also be pushed to the local image Harbor warehouse. At the same time, the completion of the pipeline task triggers the next pipeline task to push the test image.
[0090] In the method provided by this embodiment, when the pipeline task is to package the test environment image, the plug-in interface corresponding to the pipeline task is used to pull the container image configuration code corresponding to the second code from the version control system, and then the plug-in interface corresponding to the pipeline task is used to determine the image version information corresponding to the container image configuration code corresponding to the second code; and then, the plug-in interface corresponding to the pipeline task is used to build the container image according to the container image configuration code corresponding to the second code, so as to obtain the test environment image corresponding to the second code. This embodiment realizes the execution of the pipeline task of packaging the test environment image by calling the plug-in interface, and the execution efficiency is relatively high.
[0091] Optionally, when the pipeline task is to generate a test deployment package, the value of the input parameter of the pipeline task is the container cluster configuration file corresponding to the second code in the version control system; using the plug-in interface corresponding to the pipeline task, according to the value of the input parameter of the pipeline task, the output result corresponding to the pipeline task is obtained, including:
[0092] Use the plug-in interface corresponding to the pipeline task to pull the container cluster configuration file corresponding to the second code in the version control system;
[0093] Using the plug-in interface corresponding to the pipeline task, the image version information in the container cluster configuration file corresponding to the second code is updated, and the updated container cluster configuration file corresponding to the second code is pushed to the version control system;
[0094] A test deployment package is generated by utilizing the plug-in interface corresponding to the pipeline task and according to the container cluster configuration file corresponding to the updated second code.
[0095] Specifically, in some embodiments, when the pipeline task is to generate a test deployment package, the value of the input parameter of the pipeline task is the container cluster configuration file corresponding to the second code in the version control system; correspondingly, step 103 can be implemented as follows:
[0096] First, using the plug-in interface corresponding to the pipeline task, that is, the plug-in interface corresponding to the generate test deployment package pipeline task, pull the container cluster configuration file corresponding to the second code in the version control system; further, using the plug-in interface corresponding to the generate test deployment package pipeline task, update the image version information in the container cluster configuration file corresponding to the second code, and push the updated container cluster configuration file corresponding to the second code to the version control system; further, using the plug-in interface corresponding to the generate test deployment package pipeline task, generate a test deployment package according to the updated container cluster configuration file corresponding to the second code.
[0097] For example, when the pipeline task is to generate a test deployment package, the plug-in interface corresponding to the pipeline task of generating a test deployment package is used to pull the configuration file of the container cluster Manifest or Helm Chart in the version control system GitLab, and then the trigger triggers the python script to modify the Docker image Tag in the configuration file to the latest Tag of the image built this time, and push it back to the fixed branch of the version control system GitLab warehouse to generate a test deployment chart package. At the same time, the completion of the pipeline task triggers the next pipeline task to deploy the test environment.
[0098] In the method provided by this embodiment, when the pipeline task is to generate a test deployment package, first, the plug-in interface corresponding to the pipeline task is used to pull the container cluster configuration file corresponding to the second code in the version control system; then, the plug-in interface corresponding to the pipeline task is used to update the image version information in the container cluster configuration file corresponding to the second code, and the updated container cluster configuration file corresponding to the second code is pushed to the version control system; the plug-in interface corresponding to the pipeline task is used to generate a test deployment package according to the container cluster configuration file corresponding to the updated second code. This embodiment implements the execution of the pipeline task of generating a test deployment package by calling the plug-in interface of the pipeline task of generating a test deployment package, and the task execution efficiency is high.
[0099] Optionally, when the pipeline task is an automated test, the value of the input parameter of the pipeline task is the test object in the test data set and the test deployment package; using the plug-in interface corresponding to the pipeline task, according to the value of the input parameter of the pipeline task, the output result corresponding to the pipeline task is obtained, including:
[0100] Use the plug-in interface corresponding to the pipeline task to train the machine learning model according to the test data set and the preset fitness function to obtain the test case generation model;
[0101] The test case generation model is used to generate a test report based on the test objects in the test deployment package.
[0102] Specifically, in some embodiments, when the pipeline task is an automated test, the value of the input parameter of the pipeline task is the test object in the test data set and the test deployment package; the plug-in interface corresponding to the pipeline task is used to obtain the output result corresponding to the pipeline task according to the value of the input parameter of the pipeline task, which can be implemented in the following way:
[0103] First, the plug-in interface corresponding to the pipeline task is used to train the machine learning model according to the test data set and the preset fitness function to obtain a test case generation model; for example, in this embodiment, a preset fitness function is designed in combination with a genetic algorithm, and the fitness function calculates the fitness value of the test data according to the coverage of the structural elements by the data. This type of method first constructs a test program flow chart, and then uses the test data execution trajectory to calculate the corresponding fitness value. The construction of its fitness function F is:
[0104]
[0105] Among them, the value of F (test case, test object) is [0, 1].
[0106] In addition, the design of the fitness function can not only consider the coverage factor which is very important in the test process, but also consider the space and time factors in the test process, so the designed fitness value will be more universal.
[0107] The design idea of the fitness function can be designed as follows:
[0108]
[0109] Where F(T j , K j ) represents the fitness value of the Tth test case for the Kth test object, T j is the preset time parameter, J∈[0,1]; K j is the preset spatial parameter; cost(T j ,K j ) is related to both the space parameter and the time parameter, that is, it is inversely proportional to the memory consumption and directly proportional to the speed of the program; cov(T j ,K j ) depends on the value of the paths covered by the generated test cases. The newer the paths covered, the higher the value of cov(T j ,K j ) is higher.
[0110] Then, the plug-in interface corresponding to the pipeline task is called to train the machine learning model according to the test data set and the preset fitness function. For example, the preset fitness function is used as the objective function, and the value range of the preset objective function is preset. When the value range of the preset objective function is reached, the model parameters of the machine learning model at this time are used as the target model parameters, thereby determining the test case generation model.
[0111] Furthermore, the trained learning model, i.e., the test case generation model, is used to generate a test report according to the test object in the test deployment package. For example, after triggering the automated test, the test object is input into the test case generation model, and at least one test case is generated using the test case generation model; and a test report is obtained according to the at least one test case.
[0112] In the method provided in this embodiment, first, the plug-in interface corresponding to the pipeline task is used to train the machine learning model according to the test data set and the preset fitness function to obtain a test case generation model; then, the test case generation model is used to generate a test report according to the test object in the test deployment package. The test cases generated by the pipeline task of the automated test in the present invention have a high coverage.
[0113] Figure 3FIG. 3 is a flow chart of the pipeline deployment method provided by the present invention, which shows an example of a process of software development using the pipeline deployment method. Figure 3 As shown, the method includes:
[0114] First, the developer conducts self-test on the code, and then after manual approval, submits the code to the version control management system through the Git code submission tool, such as gitlab and gihub;
[0115] Then, call the corresponding plug-in interface of each pipeline task to perform the following tasks: pull the code from the version control system such as gitlab code repository for compilation and construction, perform unit testing and integration testing on the compiled and constructed code, etc.; package container images, push test images, generate test deployment chart packages, deploy test environments, perform automated testing, manual testing, package container images, push production images, generate production deployment packages, and deploy to pre-production environments, etc.;
[0116] Furthermore, the deployed application can be inspected and accepted (such as user acceptance), manually reviewed and approved, released to the outside world (such as online grayscale, full release), and finally accepted.
[0117] Optionally, in some embodiments, quality management QA and configuration management CMO links can be added to ensure the quality of the entire process and the consistency of process data and environment when the version is released, so as to facilitate rapid version iteration, online release and improvement of development, operation and maintenance, and testing efficiency.
[0118] Optionally, the version control system includes a trigger, and the trigger is used to trigger the execution of the pipeline task.
[0119] Specifically, in some embodiments, a trigger can be set in the version control system to trigger the execution of the deployed pipeline when the code or configuration file changes. The conditions of the trigger can be set as needed, such as submission to a specific branch, changes to a specific file, etc.
[0120] This method makes manual confirmation a plug-in, creates a specific confirmation file inside the plug-in to store manual confirmation information, and when manual confirmation is performed, the confirmation information is written into the file and the file is added to the version control system.
[0121] The following is a description of the pipeline deployment device provided by the present invention. The pipeline deployment device described below and the pipeline deployment method described above can be referenced to each other.
[0122] Figure 4 is a structural schematic diagram of the pipeline deployment device provided by the present invention, such as Figure 4 As shown, the device comprises:
[0123] A version management module 410 is used to use a version control system of a pipeline to add code version information to a first code submitted to the version control system, so as to obtain the first code after the code version information is added; the pipeline is obtained according to at least one plug-in, and any of the plug-ins is obtained according to a pipeline task in the pipeline;
[0124] A task triggering module 420 is used to trigger at least one of the pipeline tasks in the pipeline using a target request according to the first code after adding the code version information; the target request is triggered based on a tag push event containing the code version information; each of the pipeline tasks is executed in an independent container;
[0125] The task execution module 430 is used to call the plug-in interface corresponding to any of the pipeline tasks and execute the pipeline task according to the target request; the plug-in interface is an interface pre-registered in the engine of the pipeline;
[0126] For any of the pipeline tasks, when the pipeline task is completed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0127] In the device provided in this embodiment, the version management module 410 uses the version control system of the pipeline to add code version information to the first code submitted to the version control system to obtain the first code after the code version information is added, wherein the pipeline is obtained according to at least one plug-in, and any plug-in is obtained according to the pipeline task in the pipeline; then, the task triggering module 420 triggers at least one pipeline task in the pipeline according to the first code after the code version information is added using a target request, wherein the target request is triggered based on a tag push event containing the code version information; each pipeline task is executed in an independent container; then, for any pipeline task, the plug-in interface corresponding to the pipeline task is called, and the pipeline task is executed according to the target request; the plug-in interface is an interface pre-registered in the pipeline engine; for any pipeline task, when the pipeline task is executed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0128] In the present invention, a plug-in is generated according to at least one pipeline task, and then each plug-in is deployed to the pipeline. When the pipeline task needs to be executed, the execution of the pipeline task is achieved by calling the plug-in interface corresponding to the pipeline task. The deployment efficiency of the pipeline based on the embodiment of the present invention is relatively high, thereby improving the efficiency of executing tasks based on the pipeline.
[0129] Optionally, the pipeline task includes at least one of the following: code compilation and construction, packaging of test environment images, generation of test deployment packages, deployment of the test deployment packages to the test environment, automated testing, manual testing, packaging of production environment images, generation of production deployment packages, and deployment of the production deployment packages to the pre-production environment.
[0130] Optionally, the task execution module 430 is specifically used to:
[0131] For any of the pipeline tasks, determining a second code corresponding to the pipeline task according to the target request;
[0132] Determine the value of the input parameter of the pipeline task according to the second code corresponding to the pipeline task;
[0133] Utilizing the plug-in interface corresponding to the pipeline task, the output result corresponding to the pipeline task is obtained according to the value of the input parameter of the pipeline task; the plug-in interface corresponding to the pipeline task includes at least one input parameter corresponding to the pipeline task and the output result corresponding to the pipeline task.
[0134] Optionally, when the pipeline task is to package a test environment image, the value of the input parameter of the pipeline task is the container image configuration code corresponding to the second code; the task execution module 430 is further used to:
[0135] In the case where the pipeline task is to package the test environment image, using the plug-in interface corresponding to the pipeline task to pull the container image configuration code corresponding to the second code from the version control system;
[0136] Determine the image version information corresponding to the container image configuration code corresponding to the second code by using the plug-in interface corresponding to the pipeline task;
[0137] Utilize the plug-in interface corresponding to the pipeline task, build the container image according to the container image configuration code corresponding to the second code, and obtain the test environment image corresponding to the second code.
[0138] Optionally, when the pipeline task is to generate a test deployment package, the value of the input parameter of the pipeline task is a container cluster configuration file corresponding to the second code in the version control system; the task execution module 430 is further used to:
[0139] When the pipeline task is to generate a test deployment package, using a plug-in interface corresponding to the pipeline task to pull a container cluster configuration file corresponding to the second code in the version control system;
[0140] Using the plug-in interface corresponding to the pipeline task, the image version information in the container cluster configuration file corresponding to the second code is updated, and the updated container cluster configuration file corresponding to the second code is pushed to the version control system;
[0141] The test deployment package is generated by utilizing the plug-in interface corresponding to the pipeline task and according to the container cluster configuration file corresponding to the updated second code.
[0142] Optionally, when the pipeline task is an automated test, the values of the input parameters of the pipeline task are the test data set and the test object in the test deployment package; the task execution module 430 is further used to:
[0143] In the case where the pipeline task is an automated test, the plug-in interface corresponding to the pipeline task is used to train the machine learning model according to the test data set and a preset fitness function to obtain a test case generation model;
[0144] The test case generation model is used to generate a test report according to the test objects in the test deployment package.
[0145] Optionally, the version control system includes a trigger, and the trigger is used to trigger the execution of the pipeline task.
[0146] Figure 5 An example of a physical structure diagram of an electronic device is shown in FIG. Figure 5 As shown, the electronic device may include: a processor 510, a communication interface 520, a memory 530 and a communication bus 540, wherein the processor 510, the communication interface 520 and the memory 530 communicate with each other through the communication bus 540. The processor 510 may call the logic instructions in the memory 530 to execute the pipeline deployment method, which includes:
[0147] Using a version control system of a pipeline, adding code version information to a first code submitted to the version control system, to obtain the first code after the code version information is added; the pipeline is obtained according to at least one plug-in, and any of the plug-ins is obtained according to a pipeline task in the pipeline;
[0148] According to the first code after adding the code version information, at least one of the pipeline tasks in the pipeline is triggered by using a target request; the target request is triggered based on a tag push event containing the code version information; each of the pipeline tasks is executed in an independent container;
[0149] For any of the pipeline tasks, calling the plug-in interface corresponding to the pipeline task, and executing the pipeline task according to the target request; the plug-in interface is an interface pre-registered in the engine of the pipeline;
[0150] For any of the pipeline tasks, when the pipeline task is completed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0151] In addition, the logic instructions in the above-mentioned memory 530 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.
[0152] On the other hand, the present invention further provides a computer program product, the computer program product comprising a computer program, the computer program can be stored on a non-transitory computer-readable storage medium, when the computer program is executed by a processor, the computer can execute the pipeline deployment method provided by the above methods, the method comprising:
[0153] Using a version control system of a pipeline, adding code version information to a first code submitted to the version control system, to obtain the first code after the code version information is added; the pipeline is obtained according to at least one plug-in, and any of the plug-ins is obtained according to a pipeline task in the pipeline;
[0154] According to the first code after adding the code version information, at least one of the pipeline tasks in the pipeline is triggered by using a target request; the target request is triggered based on a tag push event containing the code version information; each of the pipeline tasks is executed in an independent container;
[0155] For any of the pipeline tasks, calling the plug-in interface corresponding to the pipeline task, and executing the pipeline task according to the target request; the plug-in interface is an interface pre-registered in the engine of the pipeline;
[0156] For any of the pipeline tasks, when the pipeline task is completed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0157] In another aspect, the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the pipeline deployment method provided by the above methods is implemented, and the method includes:
[0158] Using a version control system of a pipeline, adding code version information to a first code submitted to the version control system, to obtain the first code after the code version information is added; the pipeline is obtained according to at least one plug-in, and any of the plug-ins is obtained according to a pipeline task in the pipeline;
[0159] According to the first code after adding the code version information, at least one of the pipeline tasks in the pipeline is triggered by using a target request; the target request is triggered based on a tag push event containing the code version information; each of the pipeline tasks is executed in an independent container;
[0160] For any of the pipeline tasks, calling the plug-in interface corresponding to the pipeline task, and executing the pipeline task according to the target request; the plug-in interface is an interface pre-registered in the engine of the pipeline;
[0161] For any of the pipeline tasks, when the pipeline task is completed, the execution of the next pipeline task of the pipeline task is automatically triggered.
[0162] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.
[0163] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.
[0164] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A pipeline deployment method, characterized in that: include: Using the version control system of the pipeline, adding code version information to the first code submitted to the version control system to obtain the first code after the code version information is added; The pipeline is obtained according to at least one plug-in, and any of the plug-ins is obtained according to a pipeline task in the pipeline; The pipeline task includes at least one of the following: code compilation and construction, packaging of test environment images, generation of test deployment packages, deployment of the test deployment packages to the test environment, automated testing, manual testing, packaging of production environment images, generation of production deployment packages, and deployment of the production deployment packages to the pre-production environment; the version control system includes triggers, which are used to trigger the execution of the pipeline task; The pipeline is constructed through the following steps: According to each of the pipeline tasks in the pipeline, the functions corresponding to each of the pipeline tasks are made into each of the plug-ins, and each plug-in interface is defined; the plug-in is a customizable plug-in, and the plug-in is used to meet different business needs and scenario requirements; Develop configuration files for each of the plug-ins according to the plug-in interfaces; Registering the configuration files of each of the plug-ins into the engine of the pipeline, and determining the pipeline after the engine is configured as the pipeline; According to the first code after the code version information is added, triggering at least one of the pipeline tasks in the pipeline by using a target request; The target request is triggered based on a tag push event containing code version information; each of the pipeline tasks is executed in an independent container; For any of the pipeline tasks, calling the plug-in interface corresponding to the pipeline task, and executing the pipeline task according to the target request; the plug-in interface is an interface pre-registered in the engine of the pipeline; For any of the pipeline tasks, calling a plug-in interface corresponding to the pipeline task, and executing the pipeline task according to the target request, includes: For any of the pipeline tasks, determining a second code corresponding to the pipeline task according to the target request; Determine the value of the input parameter of the pipeline task according to the second code corresponding to the pipeline task; Using the plug-in interface corresponding to the pipeline task, according to the value of the input parameter of the pipeline task, the output result corresponding to the pipeline task is obtained; the plug-in interface corresponding to the pipeline task includes at least one input parameter corresponding to the pipeline task and the output result corresponding to the pipeline task; For any of the pipeline tasks, when the pipeline task is completed, a pre-written trigger is used to automatically trigger the execution of the next pipeline task of the pipeline task; the trigger is also used to trigger the execution of the deployed pipeline when the code or configuration file of any of the pipeline tasks is changed; the trigger condition of the trigger is pre-set, and the trigger condition of the trigger includes submission to a specific branch, or a specific file is changed; In the case where the pipeline task is a packaged test environment image, the value of the input parameter of the pipeline task is the container image configuration code corresponding to the second code; the plug-in interface corresponding to the pipeline task is used to obtain the output result corresponding to the pipeline task according to the value of the input parameter of the pipeline task, including: Pulling the container image configuration code corresponding to the second code from the version control system using the plug-in interface corresponding to the pipeline task; Determine the image version information corresponding to the container image configuration code corresponding to the second code by using the plug-in interface corresponding to the pipeline task; Using the plug-in interface corresponding to the pipeline task, and according to the container image configuration code corresponding to the second code, a container image is constructed to obtain a test environment image corresponding to the second code; In the case where the pipeline task is to generate a test deployment package, the value of the input parameter of the pipeline task is the container cluster configuration file corresponding to the second code in the version control system; the plug-in interface corresponding to the pipeline task is used to obtain the output result corresponding to the pipeline task according to the value of the input parameter of the pipeline task, including: Using the plug-in interface corresponding to the pipeline task, pull the container cluster configuration file corresponding to the second code in the version control system; Using the plug-in interface corresponding to the pipeline task, the image version information in the container cluster configuration file corresponding to the second code is updated, and the updated container cluster configuration file corresponding to the second code is pushed to the version control system; Generate the test deployment package by using the plug-in interface corresponding to the pipeline task and according to the container cluster configuration file corresponding to the updated second code; In the case where the pipeline task is an automated test, the values of the input parameters of the pipeline task are the test data set and the test objects in the test deployment package; the plug-in interface corresponding to the pipeline task is used to obtain the output result corresponding to the pipeline task according to the values of the input parameters of the pipeline task, including: Using the plug-in interface corresponding to the pipeline task, the machine learning model is trained according to the test data set and a preset fitness function to obtain a test case generation model; The test case generation model is used to generate a test report according to the test objects in the test deployment package.
2. A pipeline deployment device, characterized in that: include: A version management module, used to use the version control system of the pipeline to add code version information to the first code submitted to the version control system to obtain the first code after the code version information is added; The pipeline is obtained according to at least one plug-in, and any of the plug-ins is obtained according to a pipeline task in the pipeline; The pipeline task includes at least one of the following: code compilation and construction, packaging of test environment images, generation of test deployment packages, deployment of the test deployment packages to the test environment, automated testing, manual testing, packaging of production environment images, generation of production deployment packages, and deployment of the production deployment packages to the pre-production environment; the version control system includes triggers, which are used to trigger the execution of the pipeline task; The pipeline is constructed by the following steps: according to each pipeline task in the pipeline, the functions corresponding to each pipeline task are made into each plug-in, and each plug-in interface is defined; the plug-in is a customizable plug-in, and the plug-in is used to meet different business needs and scenario requirements; according to each plug-in interface, the configuration file of each plug-in is developed; the configuration file of each plug-in is registered in the engine of the pipeline, and the pipeline after the engine is configured is determined as the pipeline; A task triggering module, configured to trigger at least one of the pipeline tasks in the pipeline using a target request according to the first code after adding the code version information; the target request is triggered based on a tag push event containing the code version information; each of the pipeline tasks is executed in an independent container; A task execution module, for calling a plug-in interface corresponding to any of the pipeline tasks, and executing the pipeline task according to the target request; the plug-in interface is an interface pre-registered in the engine of the pipeline; The method of calling the plug-in interface corresponding to any of the pipeline tasks and executing the pipeline task according to the target request includes: determining the second code corresponding to the pipeline task according to the target request for any of the pipeline tasks; determining the value of the input parameter of the pipeline task according to the second code corresponding to the pipeline task; using the plug-in interface corresponding to the pipeline task, and obtaining the output result corresponding to the pipeline task according to the value of the input parameter of the pipeline task; the plug-in interface corresponding to the pipeline task contains at least one input parameter corresponding to the pipeline task and the output result corresponding to the pipeline task; when the pipeline task is a package test In the case of an environment image, the value of the input parameter of the pipeline task is the container image configuration code corresponding to the second code; the plug-in interface corresponding to the pipeline task is used to obtain the output result corresponding to the pipeline task according to the value of the input parameter of the pipeline task, including: using the plug-in interface corresponding to the pipeline task to pull the container image configuration code corresponding to the second code from the version control system; using the plug-in interface corresponding to the pipeline task to determine the image version information corresponding to the container image configuration code corresponding to the second code; using the plug-in interface corresponding to the pipeline task to build a container image according to the container image configuration code corresponding to the second code, and obtain The test environment image corresponding to the second code; when the pipeline task is to generate a test deployment package, the value of the input parameter of the pipeline task is the container cluster configuration file corresponding to the second code in the version control system; the use of the plug-in interface corresponding to the pipeline task, according to the value of the input parameter of the pipeline task, to obtain the output result corresponding to the pipeline task, including: using the plug-in interface corresponding to the pipeline task to pull the container cluster configuration file corresponding to the second code in the version control system; using the plug-in interface corresponding to the pipeline task to update the image version information in the container cluster configuration file corresponding to the second code, and updating the updated second code to the The corresponding container cluster configuration file is pushed to the version control system; the plug-in interface corresponding to the pipeline task is used to generate the test deployment package according to the container cluster configuration file corresponding to the updated second code; when the pipeline task is an automated test, the value of the input parameter of the pipeline task is the test data set and the test object in the test deployment package; the plug-in interface corresponding to the pipeline task is used to obtain the output result corresponding to the pipeline task according to the value of the input parameter of the pipeline task, including: using the plug-in interface corresponding to the pipeline task, according to the test data set and a preset fitness function, to train the machine learning model to obtain a test case generation model;Generate a test report based on the test objects in the test deployment package using the test case generation model; For any of the pipeline tasks, when the pipeline task is completed, a pre-written trigger is used to automatically trigger the execution of the next pipeline task of the pipeline task; the trigger is also used to trigger the execution of the deployed pipeline when the code or configuration file of any of the pipeline tasks changes; the trigger condition of the trigger is pre-set, and the trigger condition of the trigger includes submission to a specific branch, or a change in a specific file.
3. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the pipeline deployment method as claimed in claim 1 is implemented.
4. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the pipeline deployment method as claimed in claim 1 is implemented.
Citation Information
Patent Citations
Assembly line construction method and system based on parameter configuration
CN111506304A
DevOps-based free arrangement monitoring system and use method thereof
CN111930421A
Method for constructing cloud native application CICD assembly line in container cluster environment
CN115480868A
Orchestration of elastic value-streams
US20190317761A1
