TWI892857B - Microservice version control system and method thereof - Google Patents

Abstract

A microservice version control system and method thereof is provided, the method includes updating a system version number and an updated microservice version number under the system version number according to a microservice update program to obtain and store an updated version information, obtaining the updated version information and performing a roadblock through a roadblock module to obtain and store a version definition file after the roadblock, and downloading the version definition file to deploy microservices according to the version definition file, facilitating the system final version testing.

Description

Azure DevOps Repos-based microservice version control system and method

The present invention relates to the field of microservice version control technology, and in particular to a microservice version control system and method based on Azure DevOps Repos.

In modern software development, after developers complete writing and testing code, they upload it to a version control system like Azure Repository. This code then automatically compiles, tests, and packages the code through a continuous integration (CI) pipeline, ultimately producing a deployable container image.

However, the current problem is that after compiling and uploading container images to Azure Repos, there's no effective management mechanism to record the microservice version number. This makes microservice version management cumbersome and inconvenient for development teams, requiring additional manual operations and management, making the version control process relatively complex and prone to errors.

Therefore, it is very necessary to have a system that can automatically record microservice version numbers during the CI pipeline and provide convenient management and query functions.

This invention provides a microservice version control system and method based on Azure DevOps Repos, which can eliminate the need for data backup, improve the convenience and reliability of operations, and perform the above operations and modification queries under the one-stop Azure DevOps system.

The present invention discloses a microservice version control system based on Azure DevOps Repos, comprising a pipeline module, an update component version module, a roadmap module, and an output version definition file module. The pipeline module provides an interface for users to manage system versions. The update component version module is electrically connected to the pipeline module and the Azure Repos storage module, respectively, to update the system version number and the updated microservice version number under the system version number according to the microservice update program to obtain updated version information and store the updated version information in the Azure Repos storage module. The roadblock module is electronically connected to the pipeline module and the Azure Repos storage module. It retrieves updated version information from the Azure Repos storage module for roadblocking, obtaining the roadblocked version definition file and storing it in the Azure Repos storage module. The version definition file includes the mapping between the roadblocked system version number and the microservice version number under the system version number. The output version definition file module is electronically connected to the pipeline module and the Azure Repos storage module. It downloads the version definition file from the Azure Repos storage module and deploys microservices based on the version definition file for subsequent testing of system stability and availability.

The present invention provides a microservice version control method based on Azure DevOps Repos, including updating the system version number and the updated microservice version number under the system version number according to the microservice update program through the update component version module to obtain updated version information, and storing the updated version information in the Azure repos storage module; obtaining the updated version information from the Azure repos storage module, and performing a roadblock module to obtain a roadblock version definition file, and storing the version definition file in the Azure repos storage module, wherein the version definition file includes the corresponding information between the roadblock system version number and the microservice version number under the system version number; and downloading the version definition file from the Azure repos storage module to deploy the microservice according to the version definition file.

Based on the above, the present invention provides a microservice version control system and method based on Azure DevOps Repos, which can not only automatically record the microservice version number, but also provide a package version function, so that during regular system package version testing, a corresponding version definition file of (system version number) and (microservice version number) can be automatically defined, which facilitates system version testing, management and query of different versions of microservices, and can provide users with operation and management of system versions. The above version information and version definition files are stored together in the Azure repos storage module, eliminating the need for data backup and improving the convenience and reliability of operation. Moreover, the above operations and modification queries are all performed under the one-stop Azure devops system.

In order to make the above features and advantages of the present invention more clearly understood, embodiments are given below and described in detail with reference to the accompanying drawings.

Some embodiments of the present invention will be described in detail below with reference to the accompanying drawings. When the same reference numerals appear in different drawings, they are considered to represent the same or similar elements. These embodiments are only part of the present invention and do not disclose all possible implementations of the present invention.

FIG1 is a schematic diagram of a microservice version control system based on Azure DevOps Repos according to an embodiment of the present invention.

Referring to FIG. 1 , an Azure DevOps Repos-based microservice version control system according to an embodiment of the present invention may include a pipeline module 101, an interface module 102, an update component version module 103, a roadmap module 104, an output version definition file module 105, an Azure Repos storage module 106, and a labeling module 107.

The pipeline module 101 can provide an interface for users to operate system version management. The pipeline module 101 can modify the version number of the version definition file and store the modified version definition file in the Azure repos storage module 106.

In one embodiment, pipeline module 101 may be an Azure Pipeline module, providing a web UI visual interface for users to manage system versions. Users can use the Azure Pipeline module to execute pipeline operations, such as entering the version year and month, version branch parameters, the corresponding system version number, and the version number of the microservice (component) to be updated, and then executing operations such as updating the component version within the system version. The present invention is not limited to this.

Interface module 102 is electrically connected to pipeline module 101, component update module 103, package release module 104, and output version definition file module 105, respectively, to transmit various commands, such as update commands, package release commands, and data storage commands, to pipeline module 101, component update module 103, package release module 104, and output version definition file module 105.

In one embodiment, the interface module 102 may be a RESTFUL application programming interface (RESTFUL API).

In one embodiment, the microservice update program may trigger a continuous integration pipeline (CI pipeline) to generate a container image when the user updates the microservice.

The update component version module 103 is electrically connected to the pipeline module 101 and the Azure repos storage module 106 , respectively. It can update the system version number and the updated microservice version number under the system version number according to the microservice update program and the update instruction transmitted via the interface module 102 to obtain the updated version information and store the updated version information in the Azure repos storage module 106 .

In one embodiment, the component version update module 103 can be integrated into the CI pipeline through an interface provided by a RESTFUL API. When a user pushes a microservice update program to the Azure pipeline module to trigger CI, the JSON-formatted version information associated with the component version number (i.e., the microservice version number) under the specific system version (git branch) can be updated and stored in the Azure repos storage module 106.

In one embodiment, the Azure repos storage module 106 can store data such as microservice version numbers, OpenStack version numbers, DB version numbers, and deployment script version numbers. The present invention is not limited to this.

When the CI pipeline triggers the compilation completion, the microservice version number (component version number) and Branch (system version number) are recorded through the RESTful API, which can automatically record the microservice version number.

The roadblock module 104 is electronically connected to the pipeline module 101 and the Azure repos storage module 106 . It can obtain updated version information from the Azure repos storage module 106 for roadblocking, thereby obtaining a roadblocked version definition file and storing it in the Azure repos storage module 106 . The version definition file may include the mapping between the roadblocked system version number and the microservice version numbers under the system version number.

The package version module 104 provides a package version function, so that during regular system package version testing, a corresponding version definition file of a system version number and a microservice version number can be automatically defined, which facilitates system version testing and facilitates the management and query of different versions of microservices.

The output version definition file module 105 is electrically connected to the pipeline module 101 and the Azure repos storage module 106 , respectively. The version definition file can be downloaded from the Azure repos storage module 106 , so that microservices can be deployed based on the version definition file for subsequent testing of system stability and availability.

The tagging module 107 is electronically connected to the Azure repos storage module 106. The tagging module 107 performs a Git tagging on the version definition file, assigning the system version number to each microservice version under the roadblocked system version number. The tagging module then stores the labeled version definition file in the Azure repos storage module 106. For example, in the version definition file 50 shown in Figure 2, each microservice version under the system version number is assigned the system version number (v22.10.0-develop), making it easier for users to identify the service versions in subsequent operations and deploy and test them.

The pipeline module 101 allows users to operate and manage system versions, and stores the version information, such as microservice version numbers, OpenStack version numbers, DB version numbers, deployment script version numbers, and version definition files, in the Azure repos storage module 106. This eliminates the need for data backup and improves operational convenience and reliability. Furthermore, all operations and modification queries are performed within the one-stop Azure DevOps system, achieving a one-stop CI/CD service and realizing integrated operations across the entire development, testing, deployment, and version management process.

In one embodiment of the present invention, the pipeline module 101, interface module 102, update component version module 103, roadblock module 104, output version definition file module 105, Azure repos storage module 106, and labeling module 107 are each implemented using a central processing unit (CPU) or other programmable general-purpose or special-purpose microprocessor. In another embodiment of the present invention, the pipeline module 101, interface module 102, update component version module 103, roadblock module 104, output version definition file module 105, Azure repos storage module 106, and labeling module 107 may also be implemented using the same processor with different modules loaded into it, but the present invention is not limited thereto.

The pipeline module 101, the interface module 102, the update component version module 103, the roadblock module 104, the output version definition file module 105, the Azure repos storage module 106, and the labeling module 107 can be implemented using software, firmware, or hardware circuits, or any combination thereof. This disclosure does not limit the implementation of the pipeline module 101, the interface module 102, the update component version module 103, the roadblock module 104, the output version definition file module 105, the Azure repos storage module 106, and the labeling module 107.

Below, the microservice version control mechanism described in the first embodiment of the present invention in FIG2 will be described in conjunction with the various devices, components, and modules in FIG1. Each process can be adjusted according to the implementation situation and is not limited to this.

FIG2 is a schematic diagram of microservice version control according to a first embodiment of the present invention.

Referring to Figure 2, in a first embodiment, a microservice version control system based on Azure DevOps Repos can be used for the continuous integration (CI)/continuous deployment (CD) process in a microservice architecture.

When developers 20 update microservices 30 and push the updates to the Azure repos where each microservice 30 is stored, these updates directly trigger pipeline modules 101, such as the CI pipeline, to compile container images.

In one embodiment, the CI pipeline integrates a tag-engine API. Once a container image is compiled, the tag for the corresponding container image version is automatically updated to the tag-engine 40 (i.e., a microservice version control system based on Azure DevOps Repos). This updated data is actually stored in the Azure Repos storage module 106.

Subsequently, users can download the version definition file 50 through the roadblock application program interface and deploy the environment 60 based on the downloaded version definition file 50, thereby implementing the deployment of the microservice system update.

In the first embodiment, the system version number (i.e., productionname) in the version definition file 50 is v22.10.0-develop, and the microservice version numbers (i.e., microservices_a, microservices_b, microservices_c) corresponding to this system version number are 2.0.develop.20220722.xxxxyyyy, 2.0.develop.20221014.xxxxyyyy, and 2.0.develop.20221102.xxxxyyyy, respectively.

Hereinafter, the method described in the embodiment of the present invention will be described with reference to the various devices, components, and modules in Figure 1. The various processes of the method can be adjusted according to the implementation situation, but are not limited thereto.

FIG3 is a flowchart of a microservice version control method based on Azure DevOps Repos according to an embodiment of the present invention.

Please refer to FIG. 1 to FIG. 3 , in step S301 , the microservice 30 is updated.

In step S302, the CI pipeline is triggered to compile a container image. In one embodiment, the container image that triggers the CI pipeline to compile can be a microservice update program.

In step S303, the component version update module 103 updates the system version number and the updated microservice version number under the system version number according to the microservice update program to obtain updated version information.

In step S304 , the updated version information is stored in the Azure repos storage module 106 .

In step S305, a version definition file is generated and obtained.

In one embodiment, the roadblock module 104 may obtain updated version information from the Azure repos storage module 106 to perform a roadblock, thereby obtaining a roadblocked version definition file and storing the version definition file in the Azure repos storage module 106. The version definition file may include the mapping information between the roadblocked system version number and the microservice version number under the system version number.

In step S306 , the version definition file is downloaded from the Azure repos storage module 106 , so that the microservice system is deployed according to the version definition file to facilitate system version testing.

Based on the above, the present invention provides a microservice version control system and method based on Azure DevOps Repos, which can not only automatically record the microservice version number, but also provide a package version function, so that during regular system package version testing, a corresponding version definition file of (system version number) and (microservice version number) can be automatically defined, which facilitates system version testing, management and query of different versions of microservices, and can provide users with operation and management of system versions. The above version information and version definition files are stored together in the Azure repos storage module, eliminating the need for data backup and improving the convenience and reliability of operation. Moreover, the above operations and modification queries are all performed under the one-stop Azure devops system.

Although the present invention has been disclosed above by way of embodiments, they are not intended to limit the present invention. Any person having ordinary skill in the art may make slight modifications and improvements without departing from the spirit and scope of the present invention. Therefore, the scope of protection of the present invention shall be determined by the scope of the attached patent application.

101: Pipeline Module 102: Interface Module 103: Component Version Update Module 104: Roadblock Module 105: Version Definition Output Module 106: Azure Repository Storage Module 107: Labeling Module 20: Developers 30: Microservices 40: Labeling Engine 50: Version Definition File 60: Environment S301, S302, S303, S304, S305, S306: Steps

Figure 1 is a schematic diagram of a microservice version control system based on Azure DevOps Repos according to an embodiment of the present invention. Figure 2 is a schematic diagram of microservice version control according to a first embodiment of the present invention. Figure 3 is a flow chart of a microservice version control method based on Azure DevOps Repos according to an embodiment of the present invention.

101: Pipeline Module

102: Interface Module

103: Update component version module

104: Roadblock Module

105: Output version definition file module

106: Azure repos storage module

107: Labeling module

Claims (6)

A microservice version control system based on Azure DevOps Repos includes: a pipeline module for providing an interface for users to manage operating system versions; an update component version module, which is electrically connected to the pipeline module and the Azure repos storage module, and is used to update the system version number and the updated microservice version number under the system version number according to the microservice update program to obtain updated version information and store the updated version information in the Azure repos storage module; a roadmap module, which is electrically connected to the pipeline module and the Azure repos storage module, and is used to obtain the updated version information from the Azure repos storage module for roadmap, to obtain the roadmap version definition file, and store the version definition file in the Azure A repos storage module, wherein the version definition file includes correspondence information between the system version number after the package is published and the microservice version number under the system version number; a labeling module, electrically connected to the Azure repos storage module, which labels the version definition file to label each microservice version number under the system version number after the package is published with the system version number, and stores the labeled version definition file in the Azure repos storage module; and an output version definition file module, electrically connected to the pipeline module and the Azure repos storage module, respectively, for downloading the version definition file from the Azure repos storage module to deploy microservices based on the version definition file. The microservice version control system of claim 1, wherein the microservice update program triggers a continuous integration (CI) pipeline to generate a container image when the user updates the microservice. The microservice version control system as described in claim 2, wherein the pipeline module is further configured to modify the version number of the version definition file and store the modified version definition file in the Azure repos storage module. A microservice version control method based on Azure DevOps Repos, comprising: updating the system version number and the updated microservice version number under the system version number according to the microservice update program through the update component version module to obtain updated version information, and storing the updated version information in the Azure repos storage module; obtaining the updated version information from the Azure repos storage module, and performing a roadblock through the roadblock module to obtain a roadblocked version definition file, and storing the version definition file in Azure repos storage module, wherein the version definition file includes correspondence information between the system version number after the roadblock and the microservice version number under the system version number; labeling the version definition file by the labeling module to label each microservice version number under the system version number after the roadblock with the system version number, and storing the labeled version definition file in the Azure repos storage module; and downloading the version definition file from the Azure repos storage module to deploy the microservice according to the version definition file. The microservice version control method as described in claim 4, wherein the microservice update program is a container image generated by a continuous integration pipeline (CI pipeline) when the user updates the microservice. The microservice version control method as described in claim 4, wherein the method further includes: modifying the version number of the version definition file through the pipeline module, and storing the version definition file with the modified version number in the Azure repos storage module.