Update deployment method, system and storage medium

By calling the pipeline interface on the publishing system server to generate updated version information and distribute it to client deployment, the application deployment blockage and single point failure caused by excessive load on the Jenkins pipeline is solved, and higher scalability and security are achieved.

CN114281384BActive Publication Date: 2024-11-22HANYUN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111615150.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-27
Publication Date
2024-11-22
Estimated Expiration
2041-12-27

AI Technical Summary

Technical Problem

During continuous integration and microservice version updates, overload load causes blocking application deployment and possible single point of failure.

Method used

By calling the pipeline interface on the publishing system server to perform continuous integration, generating update version information, and distributing it to the client for deployment, reducing pipeline load, adopting whitelisting mechanism and role-based permission control to improve security and data isolation .

Benefits of technology

Effectively reduce pipeline load, avoid single point of failure and repeated deployment, improve the scalability and security of application deployment, and reduce network requirements for data centers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114281384B_ABST
    Figure CN114281384B_ABST
Patent Text Reader

Abstract

The present application provides an update deployment method, system and storage medium. The update deployment method performs continuous integration on the source code and generates updated version information by calling the pipeline interface through the publishing system server, obtains the version information to be updated in the first version information set according to the updated application name, updates the version information to be updated according to the updated version information, and obtains the second version information set; so that the client obtains the second version information set from the publishing system server, determines the name of the application to be deployed according to the second status information, and deploys the application to be deployed to the corresponding application server. The update deployment method distributes the work of continuous deployment to the client to reduce the load of the pipeline, and solves the technical problem that when the pipeline is overloaded, it may cause single point failure or block application deployment.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an update deployment method, system and storage medium. Background Art

[0002] At present, most microservices mainly use the pipeline Jenkins to complete continuous integration and continuous deployment, including: using the Jenkins pipeline to check out, compile, package, and deploy the application to the Kubernetes cluster by calling the API interface provided by Kubernetes to complete the version update of the microservice. However, if the Jenkins pipeline is responsible for continuous integration and microservice version updates, it is easy to cause the pipeline to be overloaded when the demand for continuous integration increases, which will block application deployment, and the overload of the pipeline is easy to cause a single point of failure in the pipeline. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide an update deployment method, system and storage medium to improve the above-mentioned Jenkins pipeline responsible for continuous integration and microservice version updates. When the demand for continuous integration increases, it is easy to cause the pipeline to be overloaded, which will block application deployment, and the pipeline overload is prone to cause single point failure of the pipeline.

[0004] To achieve the above objectives, this application provides the following technical solutions:

[0005] In a first aspect, an embodiment of the present application provides an update deployment method, which is applied to a publishing system server, and the method includes:

[0006] Performing continuous integration on the source code by calling the pipeline interface and generating update version information; wherein the update version information includes an update application name and update status information and update software package information corresponding to the update application name;

[0007] Obtaining the version information to be updated in the first version information set according to the updated application name; wherein the version information to be updated includes the name of the application to be updated and the to-be-updated state information and the to-be-updated software package information corresponding to the name of the application to be updated, and the name of the application to be updated is consistent with the name of the updated application;

[0008] The version information to be updated is updated according to the updated version information to obtain a second version information set, so that the client obtains the second version information set from the publishing system server, determines the name of the application to be deployed according to the second status information, and deploys the application to be deployed to the corresponding application server; wherein the first version information set includes multiple first application names and first status information and first software package information corresponding to each of the first application names, the second version information set includes multiple second application names and second status information and second software package information corresponding to each of the second application names, and the application to be deployed refers to the application corresponding to the name of the application to be deployed in the second version information set.

[0009] In the above scheme, the publishing system server updates the version information to be updated according to the updated version information to obtain the second version information set; so that the client obtains the second version information set from the publishing system server, determines the name of the application to be deployed according to the second status information, and deploys the application to be deployed to the corresponding application server. This update deployment method distributes the continuous deployment work to the client to reduce the load of the pipeline, and solves the technical problem that when the pipeline is overloaded, a single point failure or blocking application deployment may occur.

[0010] Optionally, the update status information includes an initial deployment status; the first status information includes a first deployment status, and the second status information includes a second deployment status; wherein the initial deployment status is an incomplete deployment; after updating the version information to be updated according to the updated version information and obtaining a second version information set, the method further includes: receiving application deployment information returned by the client; wherein the application deployment information includes the name of a deployed application that has completed deployment; and modifying the second deployment status corresponding to the second application name that is the same as the deployed application name in the second version information set to completed deployment.

[0011] In the above scheme, by receiving the application deployment information returned by the client, and modifying the second deployment status corresponding to the second application name of the completed application deployment in the second version information set to completed deployment according to the above application deployment information, the client is prevented from performing repeated deployment.

[0012] Optionally, after updating the version information to be updated according to the updated version information to obtain a second version information set, the method further includes: receiving an interface call request sent by the client; and sending the second version information set to the client according to the interface call request.

[0013] Optionally, the publishing system server adopts a whitelist mechanism; the interface call request includes a call credential; sending the second version information set to the client according to the interface call request includes: verifying the call credential; if the verification passes, sending the second version information set to the client.

[0014] In the above scheme, the publishing system server adopts a whitelist mechanism to verify the calling credentials provided by the client, and only allows designated clients in the whitelist to receive the above second version information set, which can avoid malicious pulling of the above second version information set and improve the security of information.

[0015] Optionally, the publishing system server controls the permissions of the client using a role-based permission control method; if the verification is successful, the second version information set is sent to the client, including: if the verification is successful, the third version information set of the data center to which the client belongs is sent to the client; wherein the second version information set includes the third version information set, and the third version information set includes multiple third application names and third status information and third software package information corresponding to each of the third application names.

[0016] In the above scheme, the publishing system server uses a role-based permission control method to control the client's permissions, so that the clients of each data center have independent application and version information. The client cannot pull version information sets other than the data center to which it belongs, ensuring the isolation of data between different data centers.

[0017] Optionally, the publishing system server deploys an SSL certificate.

[0018] In the above solution, deploying an SSL certificate on the publishing system server can establish an SSL channel between the publishing system server and the corresponding client, thereby improving the security of data transmission.

[0019] In a second aspect, an embodiment of the present application provides an update deployment method, which is applied to a client, and the method includes:

[0020] Acquire a second version information set from the publishing system server; wherein the second version information set includes a plurality of second application names and second status information and second software package information corresponding to each of the second application names;

[0021] Determine the name of the application to be deployed according to the second state information, and deploy the application to be deployed to the corresponding application server; wherein the application to be deployed refers to the application corresponding to the name of the application to be deployed in the second version information set;

[0022] The update version information is generated by the publishing system server by calling a pipeline interface to perform continuous integration on the source code, and the update version information includes an update application name and update status information and update software package information corresponding to the update application name.

[0023] In the above scheme, the client obtains the second version information set from the publishing system server, determines the name of the application to be deployed according to the second state information, and deploys the application to be deployed to the corresponding application server. The update deployment method distributes the work of continuous deployment to the client to reduce the load of the pipeline, and solves the technical problem that when the pipeline is overloaded, a single point failure or blocking application deployment may occur. In the update deployment method, by sinking the work of continuous deployment to the client, the client can complete the microservice update in a corresponding manner according to the type of data center to which it belongs, so that the deployment method has stronger scalability; for example, the type of data center to which the client belongs can be a physical machine, a virtual machine, a Docker or a Kubernetes cluster, etc. In addition, since the update deployment method distributes the work of continuous deployment to the client; each client pulls the second version information set from the publishing system server, the data center to which the client belongs only needs to be able to access the IP and port of the publishing system server, and no longer requires the data center to provide accessible IP and port, thereby reducing the network requirements of the data center to which the client belongs for continuous deployment.

[0024] Optionally, determining the name of the application to be deployed according to the second status information and deploying the application to be deployed to the corresponding application server includes: determining the name of the application to be deployed from multiple second application names according to the second status information; deploying the application to be deployed to the corresponding application server according to the software package information to be deployed; wherein the software package information to be deployed refers to the software package information corresponding to the name of the application to be deployed.

[0025] In the above solution, the name of the application to be deployed is determined by the second state information, and the deployment of the application program to be deployed is completed according to the software package information to be deployed.

[0026] Optionally, after determining the name of the application to be deployed according to the second status information and deploying the application to be deployed to the corresponding application server, the method further includes: returning application deployment information to the publishing system server; wherein the application deployment information includes the name of the deployed application that has completed deployment.

[0027] In the above scheme, by returning application deployment information to the publishing system server, the publishing system server modifies the second deployment status corresponding to the second application name that has completed application deployment in the second version information set to completed deployment according to the above application deployment information, thereby avoiding repeated deployment by the client.

[0028] In a third aspect, an embodiment of the present application provides an update deployment system, the system comprising: a publishing system server and a client;

[0029] The publishing system server is used to: perform continuous integration on the source code by calling the pipeline interface and generate update version information; wherein the update version information includes the update application name and the update status information and update software package information corresponding to the update application name;

[0030] Obtaining the version information to be updated in the first version information set according to the updated application name; wherein the version information to be updated includes the name of the application to be updated and the to-be-updated state information and the to-be-updated software package information corresponding to the name of the application to be updated, and the name of the application to be updated is consistent with the name of the updated application;

[0031] The version information to be updated is updated according to the updated version information to obtain a second version information set;

[0032] The client is used to: obtain the second version information set from the publishing system server, determine the name of the application to be deployed according to the second status information, and deploy the application to be deployed to the corresponding application server;

[0033] The first version information set includes multiple first application names and first status information and first software package information corresponding to each of the first application names; the second version information set includes multiple second application names and second status information and second software package information corresponding to each of the second application names; the application to be deployed refers to the application in the second version information set corresponding to the application name to be deployed.

[0034] In the above scheme, the update deployment system updates the version information to be updated according to the update version information through the publishing system server to obtain the second version information set; obtains the second version information set from the publishing system server through the client, determines the name of the application to be deployed according to the second state information, and deploys the application to be deployed to the corresponding application server. The update deployment system distributes the continuous deployment work to the client to reduce the load of the pipeline, solving the technical problem that when the pipeline is overloaded, a single point of failure or blocking of application deployment may occur.

[0035] Optionally, the publishing system server is also used to, after updating the version information to be updated according to the updated version information to obtain a second version information set: receive application deployment information returned by the client; wherein the application deployment information includes the name of a deployed application that has completed deployment; and modify the second deployment status corresponding to the second application name that is the same as the deployed application name in the second version information set to completed deployment.

[0036] Optionally, the publishing system server is also used to, after updating the version information to be updated according to the updated version information to obtain a second version information set: receive an interface call request sent by the client; and send the second version information set to the client according to the interface call request.

[0037] Optionally, the publishing system server controls the permissions of the client using a role-based permission control method; the publishing system server is also used to: if the verification is passed, send the third version information set of the data center to which the client belongs to the client; wherein the second version information set includes the third version information set, and the third version information set includes multiple third application names and third status information and third software package information corresponding to each of the third application names.

[0038] Optionally, the publishing system server deploys an SSL certificate.

[0039] Optionally, the client is specifically used to: determine the name of the application to be deployed among the multiple second application names according to the second status information; deploy the application to be deployed to the corresponding application server according to the software package information to be deployed; wherein the software package information to be deployed refers to the software package information corresponding to the name of the application to be deployed.

[0040] Optionally, the client is also used to, after deploying the application in the second version information set to the corresponding application server: return application deployment information to the publishing system server; wherein the application deployment information includes the name of the deployed application that has completed the deployment.

[0041] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: a memory and a processor, wherein the memory stores computer program instructions, and when the computer program instructions are read and run by the processor, the method provided by any possible implementation of the first aspect or the second aspect is executed.

[0042] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are read and executed by a processor, the method provided by any possible implementation of the first aspect or the second aspect is executed.

[0043] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or be understood by practicing the embodiments of the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1 A flowchart of an update deployment method applied to a publishing system server provided in an embodiment of the present application;

[0046] Figure 2 A schematic diagram of a flow chart of an update deployment method applied to a client provided in an embodiment of the present application;

[0047] Figure 3 A flowchart of another update deployment method applied to a client provided in an embodiment of the present application;

[0048] Figure 4 A schematic diagram of the structure of an update deployment system provided in an embodiment of the present application;

[0049] Figure 5 A schematic diagram of the structure of another update deployment system provided in an embodiment of the present application;

[0050] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0052] The terms "comprises," "comprising," or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0053] The terms "first", "second", etc. are only used to distinguish one entity or operation from another entity or operation, and should not be understood as indicating or implying relative importance, nor should they be understood as requiring or implying any such actual relationship or order between these entities or operations.

[0054] In view of the deficiencies in the prior art, an embodiment of the present application provides an update deployment method for reducing the pipeline load and avoiding technical problems such as blocking application deployment or causing single point failures in the pipeline due to excessive pipeline load.

[0055] Please refer to Figure 1 , Figure 1 A flow chart of an update deployment method applied to a publishing system server provided in an embodiment of the present application is provided. The update deployment method is applied to a publishing system server and includes:

[0056] Step 101: Perform continuous integration on the source code by calling the pipeline interface and generate update version information; wherein the update version information includes an update application name and update status information and update software package information corresponding to the update application name;

[0057] Step 102: acquiring the version information to be updated in the first version information set according to the updated application name; wherein the version information to be updated includes the name of the application to be updated and the to-be-updated state information and the to-be-updated software package information corresponding to the name of the application to be updated, and the name of the application to be updated is consistent with the name of the updated application;

[0058] Step 103: Update the version information to be updated according to the updated version information to obtain a second version information set, so that the client obtains the second version information set from the publishing system server, determines the name of the application to be deployed according to the second status information, and deploys the application to be deployed to the corresponding application server; wherein the first version information set includes multiple first application names and first status information and first software package information corresponding to each of the first application names, the second version information set includes multiple second application names and second status information and second software package information corresponding to each of the second application names, and the application to be deployed refers to the application corresponding to the application name to be deployed in the second version information set.

[0059] Among them, in step 101, continuous integration refers to monitoring whether there are changes in one or more source code repositories, and performing code checkout, compilation, packaging and other processes after the source code changes. Source code refers to the code in the source code repository. The update status information is used to determine whether the corresponding application needs to be deployed to the corresponding application server, which may include the update version number and update version time, and may also include the initial deployment status, etc.; the update package information can be used to complete the update of the corresponding application, which includes the update package or the update package download path, etc. Among them, if the update status information includes the initial deployment status, then the initial deployment status is an incomplete deployment.

[0060] Among them, in step 102, the name of the application to be updated that is consistent with the name of the updated application can be first determined according to the name of the updated application; the state information to be updated and the software package information to be updated corresponding to the name of the application to be updated in the first version information set can be determined according to the name of the application to be updated, and the version information to be updated can be determined according to the name of the application to be updated, the state information to be updated and the software package information to be updated.

[0061] In step 103, the first state information may include the first version number and the first version time, and may also include the first deployment state, etc.; the first software package information may include the first software package or the first software package download path, etc. The second state information may include the second version number and the second version time, and may also include the second deployment state, etc.; the second software package information may include the second software package or the second software package download path, etc. If the second state information includes the second version number and the second version time, it may be determined whether the second application name corresponding thereto is the application name to be deployed according to the second version number and the second version time; for example, if the second version number is 3.0, the current application version number is 2.0, and the corresponding second version time is after the client last obtains the second version information set, then the second application name corresponding to the second state information is the application name to be deployed. If the second state information includes the second deployment state, it may be determined whether the second application name corresponding thereto is the application name to be deployed according to the second deployment state; for example, if the second deployment state is unfinished deployment, then the second application name corresponding to the second state information is the application name to be deployed. Among them, if the client is deployed in Kubernetes, the second software package information can be the second Helm chart version information; if the client is deployed in a virtual machine, the second software package information can be the second software package or the second software package download path.

[0062] As can be seen from the above, the update deployment method provided by the present application is applied to the publishing system server, and the publishing system server updates the version information to be updated according to the update version information to obtain the second version information set; so that the client obtains the second version information set from the publishing system server, and determines the name of the application to be deployed according to the second status information, and deploys the application to be deployed to the corresponding application server. The update deployment method distributes the continuous deployment work to the client to reduce the load of the pipeline, and solves the technical problem that when the pipeline is overloaded, a single point failure or blocking of application deployment may occur.

[0063] In some optional embodiments, the update status information includes an initial deployment status; the first status information includes a first deployment status, and the second status information includes a second deployment status; wherein the initial deployment status is an incomplete deployment; in step 103, after the version information to be updated is updated according to the updated version information and a second version information set is obtained, the method further includes: receiving application deployment information returned by the client; wherein the application deployment information includes the name of a deployed application that has completed deployment; and in the second version information set, the second deployment status corresponding to the second application name that is the same as the deployed application name is modified to a completed deployment.

[0064] The application deployment information includes the name of the deployed application that has been deployed. For example, the application deployment information may include: application A and application B; and then the second deployment status corresponding to application A and application B in the second version information set is modified to have been deployed. By receiving the application deployment information returned by the client, and modifying the second deployment status corresponding to the second application name that has been deployed in the second version information set to have been deployed according to the above application deployment information, repeated deployment by the client is avoided.

[0065] In some optional embodiments, after the version information to be updated is updated according to the updated version information to obtain a second version information set in step 103, the method further includes: receiving an interface call request sent by the client; and sending the second version information set to the client according to the interface call request.

[0066] The interface call request is used by the client to call the interface of the publishing system server to obtain the second version information set of the publishing system server.

[0067] In some optional embodiments, the publishing system server adopts a whitelist mechanism; the interface call request includes a call credential; sending the second version information set to the client according to the interface call request includes: verifying the call credential; if the verification passes, sending the second version information set to the client.

[0068] Among them, the whitelist mechanism adopted by the publishing system server means that only clients in the designated data center are allowed to access the interface in the publishing system server that can obtain the second version information set. The publishing system server adopts a whitelist mechanism to verify the call credentials provided by the client, and judge whether the client belongs to the designated data center through the call credentials; by verifying the call credentials of the client, only the designated client belonging to the designated data center is allowed to receive the second version information set, which can avoid malicious pulling of the second version information set and improve the security of information.

[0069] In some optional embodiments, the publishing system server controls the permissions of the client using a role-based permission control method; if the verification is successful, the second version information set is sent to the client, including: if the verification is successful, the third version information set of the data center to which the client belongs is sent to the client; wherein the second version information set includes the third version information set, and the third version information set includes multiple third application names and third status information and third software package information corresponding to each of the third application names.

[0070] Among them, the role-based permission control method adopted by the publishing system server means that the client of each data center has an independent application and version list. The third version information set pulled by the clients of different data centers is independent, and the third application names included therein can be the same or different, and the third state information or third software package information corresponding to the same third application name pulled by the clients of different data centers can be the same or different. The third version information set pulled by each client can be the same as the second version information set, or it can be a part of the above-mentioned second version information set.

[0071] In some optional embodiments, the publishing system server deploys an SSL certificate.

[0072] Among them, SSL certificate is a kind of digital certificate. Through SSL certificate, an SSL secure channel can be established between the publishing system server and the client to ensure the security of data transmission between the publishing system server and the client.

[0073] Please refer to Figure 2 , Figure 2 A schematic diagram of a flow chart of an update deployment method applied to a client provided in an embodiment of the present application, the update deployment method, applied to the client, includes:

[0074] Step 201: Obtain a second version information set from a publishing system server; wherein the second version information set includes a plurality of second application names and second status information and second software package information corresponding to each second application name;

[0075] Step 202: determine the name of the application to be deployed according to the second state information, and deploy the application to be deployed to the corresponding application server; wherein the application to be deployed refers to the application corresponding to the name of the application to be deployed in the second version information set;

[0076] The update version information is generated by the publishing system server by calling a pipeline interface to perform continuous integration on the source code, and the update version information includes an update application name and update status information and update software package information corresponding to the update application name.

[0077] The second version information set is obtained by the publishing system server updating the version information to be updated in the first version information set according to the updated version information. The version information to be updated is obtained from the first version information set according to the updated application name; the version information to be updated includes the application name to be updated and the status information to be updated and the software package information to be updated corresponding to the application name to be updated, and the application name to be updated is consistent with the updated application name; the first version information set includes multiple first application names and the first status information and the first software package information corresponding to each of the first application names; the updated version information is generated by the publishing system server performing continuous integration on the source code by calling the pipeline interface.

[0078] The first status information may include the first version number and the first version time, and may also include the first deployment status, etc. The first software package information may include the first software package or the first software package download path, etc. If the client is deployed in Kubernetes, the first software package information may be the first Helm chart version information; if the client is deployed in a virtual machine, the first software package information may be the first software package or the first software package download path.

[0079] As can be seen from the above, the present application provides an update deployment method, which is applied to the client, and the client obtains the second version information set from the publishing system server, determines the name of the application to be deployed according to the second state information, and deploys the application to be deployed to the corresponding application server. The update deployment method distributes the work of continuous deployment to the client to reduce the load of the pipeline, and solves the technical problem that when the pipeline is overloaded, a single point of failure or blocking of application deployment may occur.

[0080] Please refer to Figure 3 , Figure 3 A flowchart of another update deployment method applied to a client provided in an embodiment of the present application.

[0081] In some optional embodiments, step 202, determining the name of the application to be deployed according to the second state information, and deploying the application to be deployed to the corresponding application server, includes: step 2021, determining the name of the application to be deployed among multiple second application names according to the second state information; step 2022, deploying the application to be deployed to the corresponding application server according to the software package information to be deployed; wherein the software package information to be deployed refers to the software package information corresponding to the name of the application to be deployed.

[0082] Among them, if the second state information includes the second version number and the second version time, it can be determined whether the corresponding second application name is the name of the application to be deployed based on the second version number and the second version time; for example, if the second version number is 3.0, the current application version number is 2.0, and the corresponding second version time is after the client last obtained the second version information set, then the second application name corresponding to the second state information is the name of the application to be deployed. If the second state information includes the second deployment status, it can be determined whether the corresponding second application name is the name of the application to be deployed based on the second deployment status; for example, if the second deployment status is incomplete deployment, then the second application name corresponding to the second state information is the name of the application to be deployed.

[0083] In some optional embodiments, after deploying the application to be deployed to the corresponding application server according to the software package information to be deployed in step 2022, the method further includes: returning application deployment information to the publishing system server; wherein the application deployment information includes the name of the deployed application that has completed the deployment.

[0084] Please refer to Figure 4 , Figure 4 A schematic diagram of the structure of an update deployment system provided in an embodiment of the present application, the update deployment system comprises: a publishing system server 301 and a client 302;

[0085] The release system server 301 is used to: perform continuous integration on the source code by calling the pipeline interface and generate update version information; wherein the update version information includes the update application name and the update status information and update software package information corresponding to the update application name;

[0086] Obtaining the version information to be updated in the first version information set according to the updated application name; wherein the version information to be updated includes the name of the application to be updated and the to-be-updated state information and the to-be-updated software package information corresponding to the name of the application to be updated, and the name of the application to be updated is consistent with the name of the updated application;

[0087] The version information to be updated is updated according to the updated version information to obtain a second version information set;

[0088] The client 302 is used to: obtain the second version information set from the publishing system server 301, determine the name of the application to be deployed according to the second state information, and deploy the application to be deployed to the corresponding application server;

[0089] The first version information set includes multiple first application names and first status information and first software package information corresponding to each of the first application names; the second version information set includes multiple second application names and second status information and second software package information corresponding to each of the second application names; the application to be deployed refers to the application in the second version information set corresponding to the application name to be deployed.

[0090] In some optional embodiments, the update deployment system further includes: a release system pipeline, wherein the release system pipeline is used to perform continuous integration on source code and generate update version information.

[0091] In some optional embodiments, the update deployment system includes at least two publishing system servers 301 .

[0092] In some optional embodiments, the update deployment system includes at least two of the release system pipelines.

[0093] In some optional embodiments, the update deployment system includes at least two clients 302 .

[0094] Among them, the publishing system server 301, the client 302 and the publishing system pipeline can all be deployed in a high-availability manner, and use a load balancing service (IPVS or IPTABLES) to complete the distribution of requests, which can be the client's HTTPS protocol request.

[0095] In some optional embodiments, the publishing system server 301 is also used to, after updating the version information to be updated according to the updated version information to obtain a second version information set: receive application deployment information returned by the client; wherein the application deployment information includes the name of a deployed application that has completed deployment; and modify the second deployment status corresponding to the second application name that is the same as the deployed application name in the second version information set to completed deployment.

[0096] In some optional embodiments, the publishing system server 301 is also used to, after updating the version information to be updated according to the updated version information to obtain a second version information set: receive an interface call request sent by the client; and send the second version information set to the client according to the interface call request.

[0097] In some optional embodiments, the publishing system server 301 uses a role-based permission control method to control the permissions of the client; the publishing system server is also used to: if the verification is passed, send the third version information set of the data center to which the client belongs to the client; wherein the second version information set includes the third version information set, and the third version information set includes multiple third application names and third status information and third software package information corresponding to each of the third application names.

[0098] In some optional embodiments, the publishing system server 301 deploys an SSL certificate.

[0099] In some optional embodiments, the client 302 is specifically used to: determine the name of the application to be deployed among the multiple second application names according to the second state information; deploy the application to be deployed to the corresponding application server according to the software package information to be deployed; wherein the software package information to be deployed refers to the software package information corresponding to the name of the application to be deployed.

[0100] In some optional embodiments, the client 302 is also used to, after deploying the application in the second version information set to the corresponding application server: return application deployment information to the publishing system server; wherein the application deployment information includes the name of the deployed application that has completed the deployment.

[0101] In some optional embodiments, when a deployment error occurs in the client 302, the client 302 provides a fault tolerance mechanism.

[0102] Among them, the client 302 sleeps and redeploys through the provided fault-tolerant mechanism to avoid the failure of application server updates due to abnormal factors such as network; and because the fault-tolerant mechanism is executed by the client, it will not increase the load on the publishing system server and the publishing system pipeline.

[0103] Please refer to Figure 5 , Figure 5A structural diagram of another update deployment system provided by an embodiment of the present application. Taking the application server as the application A server and the application B server as an example, the release system server 301 calls the pipeline interface to enable the release system pipeline to perform continuous integration on the source code, and the release system server 301 updates the first version information set of the release system server according to the updated version information generated by performing continuous integration, and generates a second version information set. The client of the application A server data center pulls the A version information list of the application A server data center in the generated second version information set, and deploys the update program of application A to the application A server according to the A version information list; wherein the A version information list includes the status information and software package information of application A, and the application A client then updates application A through the application A server. The client of the application B server data center pulls the B version information list of the application B server data center in the generated second version information set, and deploys the update program of application B to the application B server according to the B version information list; wherein the B version information list includes the status information and software package information of application B, and the application B client then updates application B through the application B server.

[0104] The update deployment system provided in the embodiment of the present application, its implementation principle and the technical effects produced have been introduced in the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference may be made to the corresponding content in the method embodiment.

[0105] The embodiment of the present application also provides an update deployment device, which is applied to a publishing system server, and the update deployment device includes: an update version information acquisition module, the update version information acquisition module is used to perform continuous integration on the source code by calling a pipeline interface and generate update version information; wherein the update version information includes an update application name and update status information and update software package information corresponding to the update application name; a to-be-updated version information acquisition module, the to-be-updated version information acquisition module is used to acquire the to-be-updated version information in the first version information set according to the update application name; wherein the to-be-updated version information includes the to-be-updated application name and the to-be-updated status information and the to-be-updated software package information corresponding to the to-be-updated application name, and the to-be-updated application name is consistent with the update application name; a second version information acquisition module An information set acquisition module, wherein the second version information set acquisition module is used to update the version information to be updated according to the updated version information, and obtain the second version information set, so that the client obtains the second version information set from the publishing system server, and determines the name of the application to be deployed according to the second status information, and deploys the application to be deployed to the corresponding application server; wherein the first version information set includes multiple first application names and the first status information and first software package information corresponding to each of the first application names, the second version information set includes multiple second application names and the second status information and second software package information corresponding to each of the second application names, and the application to be deployed refers to the application corresponding to the name of the application to be deployed in the second version information set.

[0106] In some optional embodiments, the update status information includes an initial deployment status; the first status information includes a first deployment status, and the second status information includes a second deployment status; wherein the initial deployment status is an incomplete deployment; the device also includes: an application deployment information receiving module, the application deployment information receiving module is used to receive the application deployment information returned by the client; wherein the application deployment information includes the name of a deployed application that has completed deployment; a deployment status modification module, the deployment status modification module is used to modify the second deployment status corresponding to the second application name that is the same as the deployed application name in the second version information set to a completed deployment.

[0107] In some optional embodiments, the device also includes: an interface call request receiving module, which is used to receive the interface call request sent by the client; and a second version information set sending module, which is used to send the second version information set to the client according to the interface call request.

[0108] In some optional embodiments, the publishing system server adopts a whitelist mechanism; the interface call request includes a call credential; the second version information set sending module is specifically used to: verify the call credential; if the verification passes, send the second version information set to the client.

[0109] In some optional embodiments, the publishing system server adopts a role-based permission control method to control the permissions of the client; the second version information set sending module is specifically used to: if the verification is passed, send the third version information set of the data center to which the client belongs to the client; wherein, the second version information set includes the third version information set, and the third version information set includes multiple third application names and third status information and third software package information corresponding to each of the third application names.

[0110] In some optional embodiments, the publishing system server deploys an SSL certificate.

[0111] An embodiment of the present application also provides an update deployment device, which is applied to a client, and the update deployment device includes: a version information set acquisition module, the version information set acquisition module is used to obtain a second version information set from a publishing system server; wherein the second version information set includes multiple second application names and second status information and second software package information corresponding to each second application name; an application deployment module, the application deployment module is used to determine the name of the application to be deployed according to the second status information, and deploy the application to be deployed to the corresponding application server; wherein the application to be deployed refers to the application corresponding to the name of the application to be deployed in the second version information set; wherein the update version information is generated by the publishing system server by calling a pipeline interface to perform continuous integration on the source code, and the update version information includes an update application name and update status information and update software package information corresponding to the update application name.

[0112] In some optional embodiments, the application deployment module is specifically used to: determine the name of the application to be deployed among the multiple second application names based on the second status information; deploy the application to be deployed to the corresponding application server based on the software package information to be deployed; wherein the software package information to be deployed refers to the software package information corresponding to the name of the application to be deployed.

[0113] In some optional embodiments, the device further includes: an application deployment information returning module, the application deployment information returning module is used to return application deployment information to the publishing system server; wherein the application deployment information includes the name of the deployed application that has completed deployment.

[0114] The update deployment device provided in the embodiment of the present application, its implementation principle and the technical effects produced have been introduced in the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference may be made to the corresponding content in the method embodiment.

[0115] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 6 The electronic device 4 includes: a processor 401 and a memory 402. These components are interconnected and communicate with each other through a communication bus 403 and / or other forms of connection mechanisms (not shown).

[0116] The memory 402 includes one or more (only one is shown in the figure), which may be, but not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc. The processor 401 and other possible components may access the memory 402 and read and / or write data therein.

[0117] The processor 401 includes one or more (only one is shown in the figure), which can be an integrated circuit chip with signal processing capabilities. The above-mentioned processor 401 can be a general-purpose processor, including a central processing unit (CPU), a micro control unit (MCU), a network processor (NP) or other conventional processors; it can also be a dedicated processor, including a neural network processor (NPU), a graphics processor (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. In addition, when there are multiple processors 401, some of them can be general-purpose processors and the other part can be dedicated processors.

[0118] One or more computer program instructions may be stored in the memory 402 , and the processor 401 may read and execute these computer program instructions to implement the speech quality inspection method provided in the embodiment of the present application.

[0119] Understandably, Figure 6 The structure shown is for illustration only. The electronic device 4 may also include Figure 6 More or fewer components as shown, or with Figure 6 Different structures are shown. Figure 6 The components shown in can be implemented by hardware, software or a combination thereof. The electronic device 4 may be a physical device, such as a PC, a laptop, a tablet computer, a mobile phone, a server, an embedded device, etc., or it may be a virtual device, such as a virtual machine, a virtualized container, etc. Moreover, the electronic device 4 is not limited to a single device, but may also be a combination of multiple devices or a cluster composed of a large number of devices. The embodiment of the present application also provides a computer-readable storage medium, on which computer program instructions are stored. When the computer program instructions are read and executed by a processor of a computer, the update deployment method of the first aspect or the second aspect provided in the embodiment of the present application is executed. For example, the computer-readable storage medium can be implemented as Figure 6 The memory 402 in the electronic device 4.

[0120] In the embodiments provided in the present application, it should be understood that the disclosed device or system can be implemented in other ways. The system embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interface, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0121] In addition, the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0122] Furthermore, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0123] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. An update deployment method, characterized in that: Applied to the publishing system server, the method includes: Performing continuous integration on the source code by calling the pipeline interface and generating update version information; wherein the update version information includes an update application name and update status information and update software package information corresponding to the update application name; Obtaining the version information to be updated in the first version information set according to the updated application name; wherein the version information to be updated includes the name of the application to be updated and the to-be-updated state information and the to-be-updated software package information corresponding to the name of the application to be updated, and the name of the application to be updated is consistent with the name of the updated application; The version information to be updated is updated according to the updated version information to obtain a second version information set, so that the client obtains the second version information set from the publishing system server, determines the name of the application to be deployed according to the second status information, and deploys the application to be deployed to the corresponding application server; The first version information set includes multiple first application names and first status information and first software package information corresponding to each of the first application names; the second version information set includes multiple second application names and second status information and second software package information corresponding to each of the second application names; the application to be deployed refers to the application in the second version information set corresponding to the application name to be deployed.

2. The method according to claim 1, characterized in that The update status information includes an initial deployment status; the first status information includes a first deployment status, and the second status information includes a second deployment status; wherein the initial deployment status is an unfinished deployment; After the to-be-updated version information is updated according to the updated version information to obtain a second version information set, the method further includes: Receiving application deployment information returned by the client; wherein the application deployment information includes the name of the deployed application that has completed deployment; The second deployment status corresponding to the second application name that is the same as the deployed application name in the second version information set is modified to deployment completed.

3. The method according to claim 1, characterized in that: After the to-be-updated version information is updated according to the updated version information to obtain a second version information set, the method further includes: Receiving an interface call request sent by the client; The second version information set is sent to the client according to the interface call request.

4. The method according to claim 3, characterized in that The publishing system server adopts a whitelist mechanism; the interface call request includes a call credential; The sending the second version information set to the client according to the interface call request includes: Verifying the calling credentials; If the verification is successful, the second version information set is sent to the client.

5. The method according to claim 4, characterized in that The publishing system server uses a role-based permission control method to control the permissions of the client; If the verification is successful, sending the second version information set to the client includes: If the verification passes, the third version information set of the data center to which the client belongs is sent to the client; wherein the second version information set includes the third version information set, and the third version information set includes multiple third application names and third status information and third software package information corresponding to each of the third application names.

6. The method according to claim 1, characterized in that The publishing system server deploys an SSL certificate.

7. An update deployment method, characterized in that: Applied to a client, the method comprises: Acquire a second version information set from the publishing system server; wherein the second version information set is obtained by the publishing system server updating the version information to be updated according to the updated version information; the second version information set includes a plurality of second application names and second status information and second software package information corresponding to each of the second application names; Determine the name of the application to be deployed according to the second state information, and deploy the application to be deployed to the corresponding application server; wherein the application to be deployed refers to the application corresponding to the name of the application to be deployed in the second version information set; The update version information is generated by the publishing system server by calling a pipeline interface to perform continuous integration on the source code, and the update version information includes an update application name and update status information and update software package information corresponding to the update application name.

8. The method according to claim 7, characterized in that The step of determining the name of the application to be deployed according to the second state information, and deploying the application to be deployed to the corresponding application server includes: Determine the name of the to-be-deployed application from the plurality of second application names according to the second state information; The application program to be deployed is deployed to the corresponding application server according to the software package information to be deployed; wherein the software package information to be deployed refers to the software package information corresponding to the name of the application to be deployed.

9. An update deployment system, characterized in that: The system comprises: a publishing system server and a client; The publishing system server is used to: perform continuous integration on the source code by calling the pipeline interface and generate update version information; wherein the update version information includes the update application name and the update status information and update software package information corresponding to the update application name; Obtaining the version information to be updated in the first version information set according to the updated application name; wherein the version information to be updated includes the name of the application to be updated and the to-be-updated state information and the to-be-updated software package information corresponding to the name of the application to be updated, and the name of the application to be updated is consistent with the name of the updated application; The version information to be updated is updated according to the updated version information to obtain a second version information set; The client is used to: obtain the second version information set from the publishing system server, determine the name of the application to be deployed according to the second status information, and deploy the application to be deployed to the corresponding application server; The first version information set includes multiple first application names and first status information and first software package information corresponding to each of the first application names; the second version information set includes multiple second application names and second status information and second software package information corresponding to each of the second application names; the application to be deployed refers to the application in the second version information set corresponding to the application name to be deployed.

10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, which, when executed by a processor, executes the method described in any one of claims 1-6 or 7-8.