Application Batch Release Method, Device, Electronic Device and Storage Medium

Abstract

The present application provides a method, apparatus, electronic device, and computer-readable storage medium for batch publishing of applications. The method for batch publishing of applications includes: obtaining the application orchestration relationship in the management system; obtaining the test deployment environment and test deployment cluster of the applications to be published in the management system, where the applications to be published include multiple applications in the management system; performing test deployment on the applications to be published according to the application orchestration relationship, the test deployment environment, and the test deployment cluster; and if the test deployment of the applications to be published is passed, publishing the applications to be published according to the application orchestration relationship. In the present application, the workload of publishing and deploying a large number of applications can be effectively reduced, and the publishing efficiency when a large number of applications need to be published is improved.

Description

Technical Field

[0001] The present application relates to the field of operation and maintenance technology, and specifically to a method, device, electronic device and computer-readable storage medium for batch publishing of applications. Background Art

[0002] With the rapid development of technology, application updates and iterations are also very fast. When an application is released, it usually needs to be tested before it is released. This means that the entire process of application release includes multiple steps: application construction, test deployment, testing, release deployment, etc.

[0003] In the prior art, each built application that needs to be released is first tested and deployed, tested, and then released and deployed.

[0004] However, when a large number of applications need to be released, the existing application release method of testing and deploying a single application separately will reduce the efficiency of application release due to the huge workload of testing and deploying the application. Summary of the invention

[0005] The present application provides a method, device, electronic device and computer-readable storage medium for batch publishing of applications, which can effectively reduce the workload of publishing and deploying large quantities of applications and improve the publishing efficiency when large quantities of applications need to be published.

[0006] In a first aspect, the present application provides a method for batch publishing applications, the method comprising:

[0007] Acquire an application orchestration relationship in the management system, wherein the application orchestration relationship is used to indicate a dependency relationship between subsystems in the management system and a dependency relationship between applications under the subsystems;

[0008] Acquire a test deployment environment and a test deployment cluster of the application to be released in the management system, wherein the application to be released includes multiple applications in the management system, the test deployment environment includes at least one environment to be released for the application to be released, and the test deployment cluster includes at least one cluster to be released for the application to be released;

[0009] Performing test deployment on the application to be released according to the application orchestration relationship, the test deployment environment and the test deployment cluster;

[0010] If the test deployment of the application to be released passes, the application to be released is released according to the application orchestration relationship.

[0011] In some embodiments of the present application, the application orchestration relationship includes an intra-application orchestration relationship and an inter-application orchestration relationship of the management system, and obtaining the application orchestration relationship in the management system includes:

[0012] Based on the dependency relationship between the subsystems in the management system and the dependency relationship between the applications under the subsystems, obtaining the orchestration relationship between the applications of the management system;

[0013] Based on the inter-object dependency relationship of the application in the management system, an intra-application orchestration relationship of the management system is obtained.

[0014] In some embodiments of the present application, the method further includes:

[0015] Configuring a target deployment tool for the application to be released;

[0016] The test deployment of the to-be-released application according to the application orchestration relationship, the test deployment environment, and the test deployment cluster includes:

[0017] By means of the target deployment tool, the application to be released is tested and deployed according to the application orchestration relationship, the test deployment environment and the test deployment cluster;

[0018] If the to-be-released application passes the test deployment, releasing the to-be-released application according to the application orchestration relationship includes:

[0019] If the test deployment of the application to be released passes, the application to be released is released according to the application orchestration relationship through the target deployment tool.

[0020] In some embodiments of the present application, the target deployment tool is provided with at least one of a pause control, a continue control, a cancel control, and a log download control, and the method further includes:

[0021] In response to a trigger instruction of the pause control, pausing the test deployment or release deployment of the to-be-released application;

[0022] Alternatively, in response to a trigger instruction of the continue control, continuing the test deployment or release deployment of the to-be-released application;

[0023] Alternatively, in response to the trigger instruction of the cancel control, cancel the test deployment or release deployment of the to-be-released application;

[0024] Alternatively, in response to a trigger instruction of the log download control, a test deployment log or a release deployment log of the application to be released is downloaded.

[0025] In some embodiments of the present application, if the to-be-released application passes the test deployment, releasing the to-be-released application according to the application orchestration relationship includes:

[0026] If the test deployment of the application to be released passes, obtaining the release deployment environment and release deployment cluster of the application to be released;

[0027] The application to be released is released and deployed according to the application orchestration relationship, the release and deployment environment and the release and deployment cluster.

[0028] In some embodiments of the present application, the test deployment environment includes at least one test deployment environment, the test deployment cluster includes at least one test deployment cluster, and after acquiring the test deployment environment and test deployment cluster of the application to be released in the management system, the method further includes:

[0029] Determining target clusters of each of the test deployment environments from the test deployment clusters;

[0030] A test environment cluster diagram of the to-be-released application is generated according to each target cluster of each test deployment environment, wherein a next level of each test deployment environment in the test environment cluster diagram is each target cluster of each test deployment environment.

[0031] In some embodiments of the present application, after testing and deploying the application to be released according to the application orchestration relationship, the test deployment environment and the test deployment cluster, the process further includes:

[0032] Performing anomaly detection on the test deployment of the application to be released;

[0033] If there is a test deployment anomaly in the application to be released, detecting the cause of the test anomaly of the application to be released through a preset anomaly detection program;

[0034] If the test exception reason is a reason in the preset online processing reason list, call the processing interface corresponding to the test exception reason;

[0035] The test deployment exception existing in the to-be-released application is processed online through the processing interface corresponding to the test exception cause.

[0036] In a second aspect, the present application provides an application batch publishing device, the application batch publishing device comprising:

[0037] A first acquisition unit is used to acquire an application orchestration relationship in the management system, wherein the application orchestration relationship is used to indicate a dependency relationship between subsystems in the management system and a dependency relationship between applications under the subsystems;

[0038] A second acquisition unit is used to acquire a test deployment environment and a test deployment cluster of the application to be released in the management system, wherein the application to be released includes multiple applications in the management system, the test deployment environment includes at least one environment to be released for the application to be released, and the test deployment cluster includes at least one cluster to be released for the application to be released;

[0039] A test deployment unit, configured to test and deploy the application to be released according to the application orchestration relationship, the test deployment environment and the test deployment cluster;

[0040] The publishing and deployment unit is used to publish the application to be published according to the application arrangement relationship if the application to be published passes the test deployment.

[0041] In some embodiments of the present application, the first acquisition unit is specifically used to:

[0042] Based on the dependency relationship between the subsystems in the management system and the dependency relationship between the applications under the subsystems, obtaining the orchestration relationship between the applications of the management system;

[0043] Based on the inter-object dependency relationship of the application in the management system, an intra-application orchestration relationship of the management system is obtained.

[0044] In some embodiments of the present application, the second acquisition unit is specifically used to:

[0045] Configuring a target deployment tool for the application to be released;

[0046] In some embodiments of the present application, the test deployment unit is specifically used to:

[0047] By means of the target deployment tool, the application to be released is tested and deployed according to the application orchestration relationship, the test deployment environment and the test deployment cluster;

[0048] In some embodiments of the present application, the publishing and deployment unit is specifically used to:

[0049] If the test deployment of the application to be released passes, the application to be released is released according to the application orchestration relationship through the target deployment tool.

[0050] In some embodiments of the present application, the target deployment tool is provided with at least one of a pause control, a continue control, a cancel control, and a log download control, and the application batch publishing device further includes a response unit, which is specifically used to:

[0051] In response to a trigger instruction of the pause control, pausing the test deployment or release deployment of the to-be-released application;

[0052] Alternatively, in response to a trigger instruction of the continue control, continuing the test deployment or release deployment of the to-be-released application;

[0053] Alternatively, in response to the trigger instruction of the cancel control, cancel the test deployment or release deployment of the to-be-released application;

[0054] Alternatively, in response to a trigger instruction of the log download control, a test deployment log or a release deployment log of the application to be released is downloaded.

[0055] In some embodiments of the present application, the publishing and deployment unit is specifically used to:

[0056] If the test deployment of the application to be released passes, obtaining the release deployment environment and release deployment cluster of the application to be released;

[0057] The application to be released is released and deployed according to the application orchestration relationship, the release and deployment environment and the release and deployment cluster.

[0058] In some embodiments of the present application, the application batch publishing device further includes a generating unit, the test deployment environment includes at least one test deployment environment, the test deployment cluster includes at least one test deployment cluster, and after acquiring the test deployment environment and test deployment cluster of the application to be published in the management system, the generating unit is specifically used to:

[0059] Determining target clusters of each of the test deployment environments from the test deployment clusters;

[0060] A test environment cluster diagram of the to-be-released application is generated according to each target cluster of each test deployment environment, wherein a next level of each test deployment environment in the test environment cluster diagram is each target cluster of each test deployment environment.

[0061] In some embodiments of the present application, the application batch publishing device further includes an exception handling unit, and after the application to be published is tested and deployed according to the application orchestration relationship, the test deployment environment and the test deployment cluster, the exception handling unit is specifically used to:

[0062] Performing anomaly detection on the test deployment of the application to be released;

[0063] If there is a test deployment anomaly in the application to be released, detecting the cause of the test anomaly of the application to be released through a preset anomaly detection program;

[0064] If the test exception reason is a reason in the preset online processing reason list, call the processing interface corresponding to the test exception reason;

[0065] The test deployment exception existing in the to-be-released application is processed online through the processing interface corresponding to the test exception cause.

[0066] In a third aspect, the present application further provides an electronic device, comprising a processor and a memory, wherein the memory stores a computer program, and when the processor calls the computer program in the memory, it executes the steps in any one of the application batch publishing methods provided in the present application.

[0067] In a fourth aspect, the present application also provides a computer-readable storage medium on which a computer program is stored, and the computer program is loaded by a processor to execute the steps in the application batch publishing method.

[0068] This application tests and deploys the application to be released according to the application orchestration relationship, test deployment environment and test deployment cluster of the application to be released; if the application to be released passes the test deployment, the application to be released is released according to the application orchestration relationship of the application to be released; because the test deployment and release deployment are performed after merging multiple applications, there is no need to repeat the repeated deployment work such as selecting clusters and environments, application orchestration relationships, etc. On the one hand, the test deployment work of multiple applications can be merged without the need to perform test deployment for each application one by one, thereby greatly reducing the test deployment workload when a large number of applications need to be released; on the other hand, the release deployment work of multiple applications can be merged without the need to perform release deployment for each application one by one, thereby greatly reducing the release deployment workload when a large number of applications need to be released. It can be seen that by testing and deploying the application to be released and releasing it according to the application orchestration relationship, test deployment environment and test deployment cluster of the application to be released, the release deployment workload of a large number of applications can be effectively reduced, and the release efficiency of a large number of applications when they need to be released can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0070] Figure 1 1 is a schematic diagram comparing the deployment workload of the batch release method of applications and the sequential release method of single applications in this embodiment;

[0071] Figure 2 This is a flow chart of a method for batch publishing applications provided by an embodiment of the present application;

[0072] Figure 3It is a schematic diagram for explaining the application arrangement relationship provided in the embodiment of the present application;

[0073] Figure 4 It is a scenario schematic diagram of a test environment cluster diagram provided in an embodiment of the present application;

[0074] Figure 5 This is a schematic diagram of a scene of an environment cluster selection interface provided in an embodiment of the present application;

[0075] Figure 6 It is a scenario schematic diagram of a publishing environment cluster diagram provided in an embodiment of the present application;

[0076] Figure 7 It is a schematic diagram of the structure of an embodiment of the device for batch publishing of applications provided in the embodiments of the present application;

[0077] Figure 8 It is a schematic diagram of the structure of an embodiment of an electronic device provided in the embodiments of the present application. DETAILED DESCRIPTION

[0078] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0079] In the description of the embodiments of the present application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0080] In order to enable any person skilled in the art to implement and use the present application, the following description is provided. In the following description, details are listed for the purpose of explanation. It should be understood that those of ordinary skill in the art can recognize that the present application can also be implemented without using these specific details. In other examples, the known process will not be elaborated in detail to avoid unnecessary details that make the description of the present application embodiment obscure. Therefore, the present application is not intended to be limited to the embodiments shown, but is consistent with the widest range of principles and features disclosed in accordance with the embodiments of the present application.

[0081] Embodiments of the present application provide a method, device, electronic device, and computer-readable storage medium for batch publishing of applications.

[0082] The executor of the application batch publishing method of the embodiment of the present application can be the application batch publishing device provided in the embodiment of the present application, or different types of electronic devices such as a server device, a physical host or a user equipment (UE) that integrates the application batch publishing device, wherein the application batch publishing device can be implemented in hardware or software, and the UE can specifically be a terminal device such as a smart phone, a tablet computer, a laptop computer, a PDA, a desktop computer or a personal digital assistant (PDA).

[0083] The electronic device may work in a single operation mode or in a device cluster mode.

[0084] Next, we will begin to introduce the application batch publishing method provided in the embodiment of the present application. In the embodiment of the present application, an electronic device is used as the execution subject. For the sake of simplicity and ease of description, the execution subject will be omitted in the subsequent method embodiments.

[0085] Reference Figure 1 and Figure 2 , Figure 1 : is a schematic diagram comparing the deployment workload of the batch release method of the application in this embodiment and the sequential release method of a single application. Figure 2 is a flow chart of a method for batch publishing applications provided in an embodiment of the present application. Figure 2 The flowcharts shown in the figures or other figures show a logical order, but in some cases, the steps shown or described may be performed in a different order than here. The application batch publishing method includes steps 201 to 204, wherein:

[0086] 201. Obtain application orchestration relationships in the management system.

[0087] The application orchestration relationship is used to indicate the dependency relationship between the subsystems in the management system and the dependency relationship between the applications under the subsystems.

[0088] Among them, the management system is a management system that needs to issue applications, such as the technical middle platform of a bank. According to the business usage scenario requirements, the management system can be further divided into multiple subsystems according to the dependency relationship, and each subsystem can deploy one or more applications.

[0089] The application orchestration relationship may specifically include an intra-application orchestration relationship in the management system and an intra-application orchestration relationship in the management system.

[0090] The orchestration relationship between applications is the association relationship between applications constructed according to the dependency relationship between subsystems in the management system and the dependency relationship between multiple applications under each subsystem.

[0091] The intra-application orchestration relationship is an association relationship between objects in an application that is constructed according to the inter-object dependency relationship of applications in the management system.

[0092] In step 201, there are multiple ways to obtain the application orchestration relationship in the management system, illustratively including:

[0093] (1) Real-time generation. For example, the application orchestration relationship includes the intra-application orchestration relationship and the inter-application orchestration relationship in the management system. At this time, step 201 may specifically include the following steps 2011 to 2012, where:

[0094] 2011. Based on the dependency relationship between the subsystems in the management system and the dependency relationship between the applications under the subsystems, obtain the orchestration relationship between the applications of the management system.

[0095] For example, Figure 3 As shown, Figure 3 Schematic diagram of an application arrangement relationship provided in the embodiment of the present application. Figure 3 As shown in (a), the management system includes subsystem 1, subsystem 2 and subsystem 3, and there is a dependency relationship between subsystem 1 and subsystem 2; subsystem 1 includes application 1, subsystem 2 includes application 2, and subsystem 3 includes application 3, application 4 and application 5, among which application 3 has a dependency relationship with application 5. Then, the following can be constructed: Figure 3 The orchestration relationship between applications in the management system shown in (b).

[0096] 2012. Based on the inter-object dependency relationship of the application in the management system, obtain the intra-application orchestration relationship of the management system.

[0097] In step 2012, the intra-application orchestration relationship of the management system is obtained based on the inter-object dependency relationship of the application in the management system. This is similar to step 2011. For details, please refer to the relevant instructions of step 2011. The difference is that step 2011 determines the orchestration relationship based on the application as the dimension, and step 2012 determines the orchestration relationship based on the object in the application as the dimension.

[0098] (2) Generate the application orchestration relationship of the management system in advance according to the method of generating the orchestration relationship in real time in (1) above and store it in a preset database. In step 201, directly read the application orchestration relationship in the management system from the preset database.

[0099] 202. Obtain a test deployment environment and a test deployment cluster of the application to be released in the management system.

[0100] The application to be released includes multiple applications in the management system, the test deployment environment includes at least one environment where the application to be released is to be released, and the test deployment cluster includes at least one cluster where the application to be released is to be released.

[0101] The test deployment environment refers to the environment selected for test deployment of the application to be released, for example, the Dev environment, FAT environment, UAT environment, etc.

[0102] The test deployment cluster refers to the cluster selected for test deployment of the application to be released, for example, a server cluster of a bank.

[0103] There are many ways to obtain the test deployment environment and the test deployment cluster in step 202, illustratively including:

[0104] (1) Based on the environment and cluster manually selected in the deployment tool, the test deployment environment and test deployment cluster of the application to be released are determined in real time, such as Figure 4 shown.

[0105] (2) A one-click configuration control can be set in the deployment tool to automatically configure the deployment environment and deployment cluster of the application. When the user opens the deployment tool, the one-click configuration control can be triggered to trigger the automatic selection function of the deployment environment and deployment cluster. Therefore, based on the pre-selected default environment and default cluster, the default environment can be automatically obtained as the test deployment environment of the application to be released, and the default cluster can be automatically obtained as the test deployment cluster of the application to be released.

[0106] 203. Test deploy the application to be released according to the application orchestration relationship, the test deployment environment, and the test deployment cluster.

[0107] Exemplarily, in the test deployment phase, first, the application to be published will be automatically inherited according to the application orchestration relationship in the management system. For example, according to the orchestration relationship between applications in the management system, multiple applications of the application to be published will be automatically inherited; according to the orchestration relationship within the management system, different objects within the application to be published will be inherited; then, the application to be published will be sent to the corresponding test deployment environment and test deployment cluster to complete the execution of the test deployment of the application to be published.

[0108] like Figure 1As shown in (a), when there are multiple applications to be released and the number is the same, during the test deployment phase, if a single application is tested and deployed one by one, it is necessary to select a cluster and environment for each application. If batch applications are tested and deployed, the applications with the same test deployment work can be merged, thereby consolidating a large amount of repeated deployment work.

[0109] 204. If the test deployment of the application to be released passes, release the application to be released according to the application orchestration relationship.

[0110] like Figure 1 As shown in (b), when there are multiple applications that need to be released and the number is the same, during the release and deployment phase, if individual applications are released and deployed one by one, it is necessary to select a cluster and environment for each application; if batch applications are released and deployed, applications with the same release and deployment work can be merged, thereby consolidating a large amount of repeated deployment work.

[0111] In the publishing stage, there are multiple ways to publish the application to be published in step 204, illustratively including:

[0112] (1) The test deployment environment determined in step 202 is used as the release deployment environment, and the test deployment cluster determined in step 202 is used as the release deployment cluster, and the application to be released is released to the corresponding environment and cluster. At this time, step 204 may specifically include: if the test deployment of the application to be released passes, first, the application to be released will be automatically inherited according to the application orchestration relationship in the management system, for example, according to the orchestration relationship between applications in the management system, multiple applications of the application to be released will be automatically inherited; according to the intra-application orchestration relationship of the management system, different objects in the application to be released will be inherited; then, the application to be released is sent to the corresponding test deployment environment and test deployment cluster to complete the execution of the release deployment of the application to be released.

[0113] (2) Reselect a new deployment environment as the release deployment environment of the application to be released, select a new deployment cluster as the release deployment cluster of the application to be released, and release the application to be released to the corresponding environment and cluster. At this time, step 204 may specifically include: if the test deployment of the application to be released passes, obtain the release deployment environment and release deployment cluster of the application to be released; and release and deploy the application to be released according to the application orchestration relationship, the release deployment environment and the release deployment cluster.

[0114] Among them, the method of "obtaining the release deployment environment and release deployment cluster of the application to be released" is similar to the method of obtaining the test deployment environment and release deployment cluster in the above step 202. For details, please refer to the above related instructions. For the sake of simplicity, it will not be repeated here.

[0115] For example, if the test deployment of the application to be released passes, first, it will automatically inherit the application to be released according to the application orchestration relationship in the management system. For example, according to the orchestration relationship between applications in the management system, multiple applications of the application to be released will be automatically inherited; according to the orchestration relationship within the application of the management system, different objects within the application to be released will be inherited; then, the application to be released will be sent to the corresponding release deployment environment and release deployment cluster to complete the execution of the release deployment of the application to be released.

[0116] Furthermore, in order to ensure data consistency between test deployment and release deployment, the same deployment tool is used in test deployment and release deployment in the embodiment of the present application. At this time, before the application is released, for example, a unified configuration, namely, release configuration, will be performed in the research and development stage. Release configuration is to instruct different objects under an application, such as the backend program, DB (Data base, database) and configuration resources of the application to be released, to select a deployment tool. The same deployment tool is used in the test deployment stage and the release deployment stage to ensure information consistency, thereby including the consistency of intelligent test deployment and release deployment. That is, the application batch release method also includes: configuring the target deployment tool of the application to be released. Step 203 may specifically include: through the target deployment tool, according to the application orchestration relationship, the test deployment environment and the test deployment cluster, the application to be released is tested and deployed. Step 204 may specifically include: if the test deployment of the application to be released passes, the application to be released is released according to the application orchestration relationship through the target deployment tool.

[0117] Furthermore, in order to meet some business requirements when the application is released, some operation controls can be set on the deployment tool interface, such as a pause control, a continue control, a cancel control, and a log download control.

[0118] For example, you can set a test pause control, a test continue control, a test cancel control, and a test log download control on the test deployment interface of the target deployment tool. The following describes the use and functions of the test pause control, test continue control, test cancel control, and test log download control set on the test deployment interface.

[0119] ①Test the pause control.

[0120] Exemplarily, first, after the user opens the test deployment interface of the target deployment tool and starts the test deployment of the application to be released, the test deployment interface of the target deployment tool displays a test pause control; then, it detects whether there is a trigger operation on the test pause control through, for example, clicking or touching; when the trigger operation on the test pause control is detected, a trigger instruction of the test pause control will be generated to trigger the pause function of the test deployment and pause the test deployment of the application to be released; finally, in response to the trigger instruction of the test pause control, the test deployment of the application to be released will be paused.

[0121] It can be seen that by setting a test pause control on the test deployment interface of the target deployment tool, it can be used to trigger the pause function of the test deployment to pause the test deployment of the application to be released, thereby meeting certain scenario requirements of the test deployment.

[0122] ②Test the continue control.

[0123] Exemplarily, first, after the user opens the test deployment interface of the target deployment tool and starts the test deployment of the application to be released, the test deployment interface of the target deployment tool displays a test pause control; when the user triggers the test pause control by, for example, clicking or touching, the test deployment will be paused and a test continue control will be displayed; then, it is detected whether there is a trigger operation on the test continue control by, for example, clicking or touching; when the trigger operation on the test continue control is detected, a trigger instruction of the test continue control will be generated to trigger the continue function of the test deployment; finally, in response to the trigger instruction of the test continue control, the test deployment of the application to be released will continue.

[0124] It can be seen that by setting the test continuation control on the test deployment interface of the target deployment tool, it can be used to trigger the continuation function of the test deployment to continue the test deployment of the application to be released, thereby meeting certain scenario requirements of the test deployment.

[0125] ③Test the cancel control.

[0126] Exemplarily, first, after the user opens the test deployment interface of the target deployment tool and starts the test deployment of the application to be released, the test deployment interface of the target deployment tool displays a test cancel control; then, it is detected whether there is a trigger operation on the test cancel control by, for example, clicking or touching; when the trigger operation on the test cancel control is detected, a trigger instruction of the test cancel control will be generated to trigger the cancel function of the test deployment and cancel the test deployment of the application to be released; finally, in response to the trigger instruction of the test cancel control, the test deployment of the application to be released will be canceled;

[0127] It can be seen that by setting a test cancel control on the test deployment interface of the target deployment tool, it can be used to trigger the cancel function of the test deployment to cancel the test deployment of the application to be released, thereby meeting certain scenario requirements of the test deployment.

[0128] ④Test log download control.

[0129] Exemplarily, first, after the user opens the test deployment interface of the target deployment tool, the test deployment interface of the target deployment tool can display a test log download control; then, it detects whether there is a trigger operation on the test log download control through, for example, clicking, touching, etc.; when the trigger operation on the test log download control is detected, a trigger instruction of the test log download control will be generated to trigger the log download function of the test deployment; finally, in response to the trigger instruction of the test log download control, the test deployment log of the application to be released will be downloaded.

[0130] It can be seen that by setting the test log download control on the test deployment interface of the target deployment tool, it can be used to trigger the log download function of the test deployment to download the test deployment log of the application to be released, thereby meeting certain scenario requirements of the test deployment.

[0131] For another example, you can set a publish pause control, publish continue control, publish cancel control, and publish log download control on the publish deployment interface of the target deployment tool. The following describes the use and functions of the publish pause control, publish continue control, publish cancel control, and publish log download control set on the publish deployment interface.

[0132] ⑤Release the pause control.

[0133] Exemplarily, first, after the user opens the publishing and deployment interface of the target deployment tool and starts publishing and deployment of the application to be published, the publishing and deployment interface of the target deployment tool displays a publishing pause control; then, it is detected whether there is a triggering operation on the publishing pause control by, for example, clicking or touching; when the triggering operation on the publishing pause control is detected, a triggering instruction of the publishing pause control will be generated to trigger the pause function of publishing and deployment and pause the publishing and deployment of the application to be published; finally, in response to the triggering instruction of the pause control, the publishing and deployment of the application to be published will be paused;

[0134] It can be seen that by setting the release pause control on the release deployment interface of the target deployment tool, it can be used to trigger the release deployment pause function to pause the release deployment of the application to be released, thereby meeting certain scenario requirements of release deployment.

[0135] ⑥Release the continue control.

[0136] Exemplarily, first, after the user opens the publishing and deployment interface of the target deployment tool and starts publishing and deployment of the application to be published, the publishing and deployment interface of the target deployment tool displays a publishing pause control; when the user triggers the publishing pause control by, for example, clicking or touching, the publishing and deployment will be paused, and a publishing continue control will be displayed; then, it is detected whether there is a triggering operation on the publishing continue control by, for example, clicking or touching; when the triggering operation on the publishing continue control is detected, a triggering instruction of the publishing continue control will be generated to trigger the continuing function of publishing and deployment; finally, in response to the triggering instruction of the continue control, the publishing and deployment of the application to be published will be continued;

[0137] It can be seen that by setting the release continuation control on the release and deployment interface of the target deployment tool, it can be used to trigger the release and deployment continuation function to continue the release and deployment of the application to be released, thereby meeting certain scenario requirements of the release and deployment.

[0138] ⑦ Release the cancel control.

[0139] Exemplarily, first, after the user opens the publishing and deployment interface of the target deployment tool and starts publishing and deployment of the application to be published, the publishing and deployment interface of the target deployment tool displays a publishing cancel control; then, it is detected whether there is a triggering operation on the publishing cancel control by, for example, clicking or touching; when the triggering operation on the publishing cancel control is detected, a triggering instruction of the publishing cancel control will be generated to trigger the canceling function of the publishing and deployment and cancel the publishing and deployment of the application to be published; finally, in response to the triggering instruction of the canceling control, the publishing and deployment of the application to be published will be canceled;

[0140] It can be seen that by setting a release cancel control on the release deployment interface of the target deployment tool, it can be used to trigger the release deployment cancel function to cancel the release deployment of the application to be released, thereby meeting certain scenario requirements of release deployment.

[0141] ⑧Publish log download control.

[0142] Exemplarily, first, after the user opens the release and deployment interface of the target deployment tool, the release and deployment interface of the target deployment tool can display a release log download control; then, it is detected whether there is a trigger operation on the release log download control through, for example, clicking, touching, etc.; when the trigger operation on the release log download control is detected, a trigger instruction of the release log download control will be generated to trigger the log download function of the release deployment; finally, in response to the trigger instruction of the log download control, the release and deployment log of the application to be released will be downloaded.

[0143] It can be seen that by setting the release log download control on the release and deployment interface of the target deployment tool, it can be used to trigger the log download function of the release and deployment to download the release and deployment log of the application to be released, thereby meeting certain scenario requirements of the release and deployment.

[0144] The test deployment environment includes at least one test deployment environment, and the test deployment cluster includes at least one test deployment cluster. Furthermore, in order to improve the intuitiveness of the test deployment environment and the test deployment cluster and improve the test deployment efficiency, when constructing the test deployment environment and the test deployment cluster of the application to be released, the test deployment environment and each test deployment cluster under each test deployment environment can be displayed in a hierarchical manner, such as Figure 4 Please refer to Figure 4 and Figure 5 The application batch publishing method may further include the following steps c1 to c2, wherein:

[0145] c1. Determine, from the test deployment clusters, target clusters of each of the test deployment environments.

[0146] For example, Figure 5 As shown, first, the user selects the test deployment environment required for the application to be released on the test deployment interface of the target deployment tool (such as Figure 5 As shown in the figure, the test deployment environment selected by the user is: Dev, FAT, UAT), and the test deployment cluster required for each test deployment environment (such as Figure 5 As shown in FIG. 1 , the test deployment clusters selected by the user for the test deployment environment Dev are: IDC1, IDC2, IDC3; the test deployment cluster selected by the user for the test deployment environment FAT is: IDC4; the test deployment cluster selected by the user for the test deployment environment UAT is: IDC5, IDC6. ); Thus, the target clusters of each test deployment environment (such as Figure 5 As shown, the target clusters of the test deployment environment Dev are: IDC1, IDC2, IDC3, the target clusters of the test deployment environment FAT are: IDC4, and the target clusters of the test deployment environment UAT are: IDC5, IDC6).

[0147] c2. Generate a test environment cluster diagram of the to-be-released application according to each target cluster of the test deployment environment.

[0148] The next level of each test deployment environment in the test environment cluster diagram is the target clusters of each test deployment environment. For example, the first level of the test environment cluster diagram displays the test deployment environment, and the second level of the test environment cluster diagram displays the target clusters of each test environment through topological relationships.

[0149] The test environment cluster diagram is a topological relationship diagram between the deployment environment and deployment clusters of the test deployment.

[0150] For example, Figure 4 and Figure 5 As shown, for Figure 5 The target clusters of each test deployment environment shown are: the target clusters of the test deployment environment Dev are: IDC1, IDC2, IDC3, the target clusters of the test deployment environment FAT are: IDC4, the target clusters of the test deployment environment UAT are: IDC5, IDC6, and the following can be generated: Figure 4 The test environment cluster diagram is shown.

[0151] Furthermore, in order to improve the intuitiveness of the release and deployment environment and release and deployment cluster and improve the release and deployment efficiency, when building the release and deployment environment and release and deployment cluster of the application to be released, the release and deployment environment and each release and deployment cluster under each release and deployment environment can be displayed hierarchically, such as Figure 6 Please refer to Figure 6 The application batch publishing method may further include the following steps d1 to d2, wherein:

[0152] d1. Determine the target clusters of each of the release and deployment environments from the release and deployment clusters.

[0153] For example, Figure 6 As shown, first, the user selects the release and deployment environment required for the application to be released on the release and deployment interface of the target deployment tool (for example, the release and deployment environment selected by the user is: PRD), and the release and deployment cluster required by the release and deployment environment (for example, the release and deployment clusters selected by the user for the release and deployment environment PRD are: IDC1, IDC2, IDC3); thereby, the target clusters of the release and deployment environment can be determined (for example, the target clusters of the release and deployment environment PRD are: IDC1, IDC2, IDC3).

[0154] d2. Generate a publishing environment cluster diagram of the application to be published according to each target cluster of the publishing and deployment environment.

[0155] The next level of each release deployment environment in the release environment cluster diagram is the target clusters of each release deployment environment. For example, the first level of the release environment cluster diagram displays the release deployment environment, and the second level of the release environment cluster diagram displays the target clusters of each release environment through topological relationships.

[0156] The release environment cluster diagram is a topological relationship diagram between the deployment environment and deployment clusters for release deployment.

[0157] For example, Figure 6As shown, for each target cluster of the release deployment environment: the target clusters of the release deployment environment PRD are: IDC1, IDC2, IDC3, and the following can be generated: Figure 6 The release environment cluster diagram is shown.

[0158] Furthermore, in order to improve the efficiency of test deployment, an exception check program can be added to check the test deployment exceptions of the application to be released, and an exception handling program can be added to handle the test exceptions online. That is, the application batch method can further include the following steps a1 to a4:

[0159] a1. Perform anomaly detection on the test deployment of the application to be released.

[0160] a2. If there is a test deployment anomaly in the application to be released, the cause of the test anomaly of the application to be released is detected through a preset anomaly detection program.

[0161] The preset anomaly check program is a pre-written program used to detect whether the test deployment of the application to be released is abnormal.

[0162] The test exception reason refers to the reason why the test deployment of the application to be released is abnormal, for example, network failure, abnormal test environment, etc.

[0163] a3. If the test exception reason is a reason in the preset online processing reason list, call the processing interface corresponding to the test exception reason.

[0164] The processing interface corresponding to the test exception cause refers to a program interface used to resolve the test exception cause of the application to be released.

[0165] The online processing reason list refers to a list of abnormal reasons that can be processed online among various abnormal reasons.

[0166] a4. Perform online processing on the test deployment exception of the application to be released through the processing interface corresponding to the test exception cause.

[0167] Exemplarily, in step a1, during or after the test process of the application to be released, the test deployment of the application to be released can be detected for anomalies; to detect whether the test deployment of the application to be released is abnormal. When it is detected that the application to be released has a test deployment anomaly, in step a2, the test anomaly cause of the application to be released is detected through a preset anomaly check program. Then, the test anomaly cause is compared with each cause in the online processing cause list to determine whether the test anomaly cause is a cause in the preset online processing cause list. When the test anomaly cause is a cause in the preset online processing cause list, in step a3, the processing interface corresponding to the test anomaly cause is called; in step a4, the test deployment anomaly existing in the application to be released is processed online through the processing interface corresponding to the test anomaly cause; for example, for test anomaly causes such as network failures that can be processed online, the processing interface corresponding to the network failure can be directly called to process the network existing in the application to be released online. Thereby, the test anomaly cause can be solved in a timely and automatic manner, and the test deployment process can be automatically continued, thereby improving the test deployment efficiency of the application to be released to a certain extent, and then improving the release and deployment efficiency of the application to be released.

[0168] When the test exception cause is not in the preset online processing cause list, it can be considered that the test exception cause is not a cause that can be processed online, and the test exception cause is output so that relevant managers can promptly understand the test exception cause and handle it in a timely manner, thereby improving the test deployment efficiency of the application to be released to a certain extent, and then improving the release and deployment efficiency of the application to be released.

[0169] Furthermore, in order to improve the efficiency of publishing and deployment, an exception check program can be added to check the publishing and deployment exceptions of the application to be published, and an exception handling program can be added to handle the publishing exceptions online. That is, the application batch method can further include the following steps b1 to b4:

[0170] b1. Perform anomaly detection on the release deployment of the application to be released.

[0171] b2. If there is a release and deployment exception in the application to be released, the cause of the release exception of the application to be released is detected through a preset exception determination program.

[0172] The preset abnormality determination program is a pre-written program used to detect whether the release deployment of the application to be released is abnormal.

[0173] The release exception reason refers to the reason why the release deployment of the application to be released is abnormal, for example, network failure, abnormal release environment, etc.

[0174] b3. If the publishing exception reason is a reason in the preset online processing reason list, call the processing interface corresponding to the publishing exception reason.

[0175] The processing interface corresponding to the release exception reason refers to a program interface used to resolve the release exception reason of the application to be released.

[0176] The online processing reason list refers to a list of abnormal reasons that can be processed online among various abnormal reasons.

[0177] b4. Perform online processing on the publishing and deployment exception of the application to be published through the processing interface corresponding to the publishing exception reason.

[0178] Exemplarily, in step b1, during or after the release of the application to be released, an abnormality detection can be performed on the release deployment of the application to be released to detect whether an abnormality occurs in the release deployment of the application to be released. When it is detected that the release deployment of the application to be released is abnormal, in step b2, the release abnormality cause of the application to be released is detected through a preset abnormality determination program. Then, the release abnormality cause is compared with each cause in the online processing cause list to determine whether the release abnormality cause is a cause in the preset online processing cause list. When the release abnormality cause is a cause in the preset online processing cause list, in step b3, the processing interface corresponding to the release abnormality cause is called; in step b4, the release deployment abnormality existing in the application to be released is processed online through the processing interface corresponding to the release abnormality cause; for example, for release abnormality causes such as network failures that can be processed online, the processing interface corresponding to the network failure can be directly called to process the network where the application to be released exists online. Thereby, the release abnormality cause can be solved in a timely and automatic manner, and the release deployment process can be automatically continued, thereby improving the release deployment efficiency of the application to be released to a certain extent.

[0179] When the release exception reason is not in the preset online processing reason list, it can be considered that the release exception reason is not a reason that can be processed online, and the release exception reason is output so that relevant managers can promptly understand the release exception reason and handle it in time, thereby improving the release and deployment efficiency of the application to be released to a certain extent.

[0180] From the above content, it can be seen that in the embodiment of the present application, the application to be released is tested and deployed according to the application orchestration relationship, test deployment environment and test deployment cluster of the application to be released; if the test deployment of the application to be released passes, the application to be released is released according to the application orchestration relationship of the application to be released; because the test deployment and release deployment are performed after merging multiple applications, there is no need to repeat the repeated deployment work such as selecting clusters and environments, application orchestration relationships, etc. On the one hand, the test deployment work of multiple applications can be merged without the need to perform test deployment for each application one by one, thereby greatly reducing the test deployment workload when a large number of applications need to be released; on the other hand, the release deployment work of multiple applications can be merged without the need to perform release deployment for each application one by one, thereby greatly reducing the release deployment workload when a large number of applications need to be released. It can be seen that by testing and deploying the application to be released and releasing it according to the application orchestration relationship, test deployment environment and test deployment cluster of the application to be released, the release deployment workload of a large number of applications can be effectively reduced, and the release efficiency of a large number of applications when they need to be released can be improved.

[0181] In order to better implement the application batch publishing method in the embodiment of the present application, based on the application batch publishing method, the embodiment of the present application also provides an application batch publishing device, such as Figure 7 As shown in FIG. 1 , it is a schematic diagram of the structure of an embodiment of a device for batch publishing of applications in an embodiment of the present application. The device for batch publishing of applications 700 includes:

[0182] The first acquisition unit 701 is used to acquire an application orchestration relationship in the management system, wherein the application orchestration relationship is used to indicate a dependency relationship between subsystems in the management system and a dependency relationship between applications under the subsystems;

[0183] A second acquisition unit 702 is used to acquire a test deployment environment and a test deployment cluster of the application to be released in the management system, wherein the application to be released includes multiple applications in the management system, the test deployment environment includes at least one environment to be released for the application to be released, and the test deployment cluster includes at least one cluster to be released for the application to be released;

[0184] A test deployment unit 703, configured to test and deploy the application to be released according to the application orchestration relationship, the test deployment environment and the test deployment cluster;

[0185] The publishing and deployment unit 704 is configured to publish the application to be published according to the application arrangement relationship if the application to be published passes the test deployment.

[0186] In some embodiments of the present application, the first acquiring unit 701 is specifically used to:

[0187] Based on the dependency relationship between the subsystems in the management system and the dependency relationship between the applications under the subsystems, obtaining the orchestration relationship between the applications of the management system;

[0188] Based on the inter-object dependency relationship of the application in the management system, an intra-application orchestration relationship of the management system is obtained.

[0189] In some embodiments of the present application, the second obtaining unit 702 is specifically configured to:

[0190] Configuring a target deployment tool for the application to be released;

[0191] In some embodiments of the present application, the test deployment unit 703 is specifically used to:

[0192] By means of the target deployment tool, the application to be released is tested and deployed according to the application orchestration relationship, the test deployment environment and the test deployment cluster;

[0193] In some embodiments of the present application, the publishing and deployment unit 704 is specifically used to:

[0194] If the test deployment of the application to be released passes, the application to be released is released according to the application orchestration relationship through the target deployment tool.

[0195] In some embodiments of the present application, the target deployment tool is provided with at least one of a pause control, a continue control, a cancel control, and a log download control, and the application batch publishing device 700 further includes a response unit (not shown in the figure), and the response unit is specifically used to:

[0196] In response to a trigger instruction of the pause control, pausing the test deployment or release deployment of the to-be-released application;

[0197] Alternatively, in response to a trigger instruction of the continue control, continuing the test deployment or release deployment of the to-be-released application;

[0198] Alternatively, in response to the trigger instruction of the cancel control, cancel the test deployment or release deployment of the to-be-released application;

[0199] Alternatively, in response to a trigger instruction of the log download control, a test deployment log or a release deployment log of the application to be released is downloaded.

[0200] In some embodiments of the present application, the publishing and deployment unit 704 is specifically used to:

[0201] If the test deployment of the application to be released passes, obtaining the release deployment environment and release deployment cluster of the application to be released;

[0202] The application to be released is released and deployed according to the application orchestration relationship, the release and deployment environment and the release and deployment cluster.

[0203] In some embodiments of the present application, the application batch publishing device 700 further includes a generation unit (not shown in the figure), the test deployment environment includes at least one test deployment environment, and the test deployment cluster includes at least one test deployment cluster. After obtaining the test deployment environment and test deployment cluster of the application to be released in the management system, the generation unit is specifically used to:

[0204] Determining target clusters of each of the test deployment environments from the test deployment clusters;

[0205] A test environment cluster diagram of the to-be-released application is generated according to each target cluster of each test deployment environment, wherein a next level of each test deployment environment in the test environment cluster diagram is each target cluster of each test deployment environment.

[0206] In some embodiments of the present application, the application batch publishing device 700 further includes an exception handling unit (not shown in the figure), and after the application to be released is tested and deployed according to the application orchestration relationship, the test deployment environment and the test deployment cluster, the exception handling unit is specifically used to:

[0207] Performing anomaly detection on the test deployment of the application to be released;

[0208] If there is a test deployment anomaly in the application to be released, detecting the cause of the test anomaly of the application to be released through a preset anomaly detection program;

[0209] If the test exception reason is a reason in the preset online processing reason list, call the processing interface corresponding to the test exception reason;

[0210] The test deployment exception existing in the to-be-released application is processed online through the processing interface corresponding to the test exception cause.

[0211] In specific implementation, the above units can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The specific implementation of the above units can refer to the previous method embodiments, which will not be repeated here.

[0212] Since the application batch release device can execute the application as Figures 1 to 6 Corresponding to the steps in the batch publishing method in any embodiment, the present application can be implemented as follows Figures 1 to 6The beneficial effects that can be achieved by applying the batch publishing method in any embodiment are detailed in the previous description and will not be repeated here.

[0213] In addition, in order to better implement the batch publishing method in the embodiment of the present application, on the basis of the batch publishing method, the embodiment of the present application also provides an electronic device, referring to Figure 8 , Figure 8 A schematic diagram of the structure of an electronic device according to an embodiment of the present application is shown. Specifically, the electronic device provided by the embodiment of the present application includes a processor 801, and the processor 801 is used to execute a computer program stored in a memory 802 to implement the following Figures 1 to 6 Corresponding to each step of applying the batch publishing method in any embodiment; or, the processor 801 is used to execute the computer program stored in the memory 802 to implement the following Figure 7 The functions of each unit in the corresponding embodiment.

[0214] Exemplarily, the computer program may be divided into one or more modules / units, one or more modules / units are stored in the memory 802, and executed by the processor 801 to complete the embodiment of the present application. One or more modules / units may be a series of computer program instruction segments that can complete specific functions, and the instruction segments are used to describe the execution process of the computer program in the computer device.

[0215] The electronic device may include, but is not limited to, a processor 801 and a memory 802. Those skilled in the art will appreciate that the illustration is merely an example of an electronic device and does not constitute a limitation on the electronic device, and may include more or fewer components than those shown in the illustration, or may combine certain components, or different components, for example, the electronic device may also include input and output devices, network access devices, buses, etc., and the processor 801, memory 802, input and output devices, and network access devices, etc., are connected via a bus.

[0216] The processor 801 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the electronic device, and uses various interfaces and lines to connect various parts of the entire electronic device.

[0217] The memory 802 can be used to store computer programs and / or modules. The processor 801 implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory 802 and calling the data stored in the memory 802. The memory 802 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the electronic device (such as audio data, video data, etc.), etc. In addition, the memory can include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0218] Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the application batch publishing device, electronic device and its corresponding units described above can refer to the following Figures 1 to 6 The description of the batch publishing method applied in any embodiment will not be repeated here.

[0219] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0220] To this end, an embodiment of the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to execute the present application as follows: Figures 1 to 6 For the steps in the batch publishing method of any embodiment, the specific operations can be referred to as follows Figures 1 to 6 The description of the batch publishing method applied in any embodiment will not be repeated here.

[0221] The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0222] Due to the instructions stored in the computer-readable storage medium, the present application can be executed. Figures 1 to 6 Corresponding to the steps in the batch publishing method in any embodiment, the present application can be implemented as follows Figures 1 to 6The beneficial effects that can be achieved by applying the batch publishing method in any embodiment are detailed in the previous description and will not be repeated here.

[0223] The above is a detailed introduction to an application batch publishing method, device, electronic device and computer-readable storage medium provided in an embodiment of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for batch publishing applications. It is characterized in that The method comprises: Acquire an application orchestration relationship in the management system, wherein the application orchestration relationship is used to indicate a dependency relationship between subsystems in the management system and a dependency relationship between applications under the subsystems; Acquire a test deployment environment and a test deployment cluster of the application to be released in the management system, wherein the application to be released includes multiple applications in the management system, the test deployment environment includes at least one environment to be released for the application to be released, and the test deployment cluster includes at least one cluster to be released for the application to be released; Performing test deployment on the application to be released according to the application orchestration relationship, the test deployment environment and the test deployment cluster; If the test deployment of the application to be released passes, releasing the application to be released according to the application arrangement relationship; The application orchestration relationship includes the intra-application orchestration relationship and the inter-application orchestration relationship of the management system, and obtaining the application orchestration relationship in the management system includes: Based on the dependency relationship between the subsystems in the management system and the dependency relationship between the applications under the subsystems, obtaining the orchestration relationship between the applications of the management system; Based on the inter-object dependency relationship of the application in the management system, obtaining the intra-application orchestration relationship of the management system; The method further comprises: Configuring a target deployment tool for the application to be released; The test deployment of the to-be-released application according to the application orchestration relationship, the test deployment environment, and the test deployment cluster includes: By means of the target deployment tool, the application to be released is tested and deployed according to the application orchestration relationship, the test deployment environment and the test deployment cluster; If the to-be-released application passes the test deployment, releasing the to-be-released application according to the application orchestration relationship includes: If the test deployment of the application to be released passes, the application to be released is released according to the application orchestration relationship through the target deployment tool.

2. The method for batch publishing of applications according to claim 1, It is characterized in that The target deployment tool is provided with at least one of a pause control, a continue control, a cancel control, and a log download control, and the method further includes: In response to a trigger instruction of the pause control, pausing the test deployment or release deployment of the to-be-released application; Alternatively, in response to a trigger instruction of the continue control, continuing the test deployment or release deployment of the to-be-released application; Alternatively, in response to the trigger instruction of the cancel control, cancel the test deployment or release deployment of the to-be-released application; Alternatively, in response to a trigger instruction of the log download control, a test deployment log or a release deployment log of the application to be released is downloaded.

3. The method for batch publishing of applications according to claim 1, It is characterized in that If the to-be-released application passes the test deployment, releasing the to-be-released application according to the application orchestration relationship includes: If the test deployment of the application to be released passes, obtaining the release deployment environment and release deployment cluster of the application to be released; The application to be released is released and deployed according to the application orchestration relationship, the release and deployment environment and the release and deployment cluster.

4. The method for batch publishing of applications according to claim 1, It is characterized in that The test deployment environment includes at least one test deployment environment, the test deployment cluster includes at least one test deployment cluster, and the method further includes: Determining target clusters of each of the test deployment environments from the test deployment clusters; A test environment cluster diagram of the to-be-released application is generated according to each target cluster of each test deployment environment, wherein a next level of each test deployment environment in the test environment cluster diagram is each target cluster of each test deployment environment.

5. The method for batch publishing applications according to any one of claims 1 to 4, It is characterized in that After testing and deploying the application to be released according to the application orchestration relationship, the test deployment environment and the test deployment cluster, the method further includes: Performing anomaly detection on the test deployment of the application to be released; If there is a test deployment anomaly in the application to be released, detecting the cause of the test anomaly of the application to be released through a preset anomaly detection program; If the test exception reason is a reason in the preset online processing reason list, call the processing interface corresponding to the test exception reason; The test deployment exception existing in the to-be-released application is processed online through the processing interface corresponding to the test exception cause.

6. A device for batch publishing applications, It is characterized in that The application batch publishing device comprises: A first acquisition unit is used to acquire an application orchestration relationship in the management system, wherein the application orchestration relationship is used to indicate a dependency relationship between subsystems in the management system and a dependency relationship between applications under the subsystems; A second acquisition unit is used to acquire a test deployment environment and a test deployment cluster of the application to be released in the management system, wherein the application to be released includes multiple applications in the management system, the test deployment environment includes at least one environment to be released for the application to be released, and the test deployment cluster includes at least one cluster to be released for the application to be released; A test deployment unit, configured to test and deploy the application to be released according to the application orchestration relationship, the test deployment environment and the test deployment cluster; A publishing and deployment unit, configured to publish the application to be published according to the application arrangement relationship if the application to be published passes the test deployment; The application orchestration relationship includes an intra-application orchestration relationship and an inter-application orchestration relationship of the management system, and the first acquisition unit is further used to: Based on the dependency relationship between the subsystems in the management system and the dependency relationship between the applications under the subsystems, obtaining the orchestration relationship between the applications of the management system; Based on the inter-object dependency relationship of the application in the management system, obtaining the intra-application orchestration relationship of the management system; The application batch publishing device is also used for: Configuring a target deployment tool for the application to be released; The test deployment of the to-be-released application according to the application orchestration relationship, the test deployment environment, and the test deployment cluster includes: By means of the target deployment tool, the application to be released is tested and deployed according to the application orchestration relationship, the test deployment environment and the test deployment cluster; If the to-be-released application passes the test deployment, releasing the to-be-released application according to the application orchestration relationship includes: If the test deployment of the application to be released passes, the application to be released is released according to the application orchestration relationship through the target deployment tool.

7. An electronic device, It is characterized in that The method comprises a processor and a memory, wherein a computer program is stored in the memory, and when the processor calls the computer program in the memory, the method for batch publishing of applications as claimed in any one of claims 1 to 5 is executed.

8. A computer-readable storage medium, It is characterized in that A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in the application batch publishing method described in any one of claims 1 to 5.

Images