Batch determination method and device for application version installation result

Abstract

The application provides a batch determination method and device for application version installation results, and relates to the technical field of version batch processing and the field of intelligent operation and maintenance. The method comprises the following steps: obtaining to-be-compared version information, wherein the to-be-compared version information comprises an application name and a service group name; determining a corresponding to-be-compared version number list, at least one installation environment and a corresponding installed version number list thereof according to the to-be-compared version information; comparing the to-be-compared version number list with the installed version number list to obtain the application version installation results. The application starts from the complex scene of version installation inspection of a large number of applications, generates rules for analyzing batch version packages, completes automatic comparison of installation results of batch version packages, realizes comprehensive coverage of inspection of ordinary versions and batch versions, and improves the efficiency and accuracy of version inspection.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of version batch processing and the field of intelligent operation and maintenance, and in particular to a batch determination method and device for application version installation results. BACKGROUND

[0002] From the delivery of the software version development to the start of testing to the final production environment production online, due to the discovery and modification of test problems, many test versions will be released. In the test environment and the production environment, in order to ensure the integrity of the version installation, the installation of these versions needs to be mastered, and the installation of all versions released is counted. The version of the application generally has a special version installation platform to implement installation, and the platform records the installation results of each version, so when the installation of a single application and a single version needs to be queried, whether through manual input of query conditions for viewing on the installation platform or through the query interface opened by the installation platform, it can be easily obtained. In large financial enterprises, due to the large number of business types, hundreds of applications will be divided, and many applications will also be divided into multiple service groups according to functional units. According to the different deployment situations of the application, the installation environment of these service groups is also different.

[0003] For the case that a service group of an application corresponds to one or more sets of installation environments, the existing checking scheme is to manually analyze the application deployment rules, find and record the version installation of each set of deployment environments in the installation system. For the case that multiple service groups of an application correspond to the same installation environment, the existing checking scheme also needs to manually analyze the deployment rules, and check the installation of the versions under the multiple service groups in the deployment environment in turn, and finally the checking results of all service groups are summarized. In addition, the versions of some applications will be packaged into one version through the integration of the installation strategy due to too many versions released, in order to improve the installation efficiency. For the installation checking of this case, the version packaging rules need to be understood, the multiple version numbers are manually combined into a new version number, and then the installation record is compared in the installation system according to the new version number.

[0004] As can be seen, the existing scheme relies on manual comparison, installation checking and result feedback. Since the application deployment rules need to be manually analyzed before each comparison, the efficiency is low, and the repeated waste of manpower is also easy to cause. The final checking result depends on manual judgment, and the accuracy and integrity of the checking cannot be guaranteed. SUMMARY

[0005] In order to solve the problems in the prior art, the present application provides a batch determination method and device for application version installation results, which relates to the technical field of version batch processing and the field of intelligent operation and maintenance. In a first aspect, the present application provides a batch determination method for application version installation results, comprising:

[0006] Obtaining to-be-compared version information, the to-be-compared version information including an application name and a service group name;

[0007] Determining a corresponding to-be-compared version number list, at least one installation environment and a corresponding installed version number list according to the to-be-compared version information;

[0008] Comparing the to-be-compared version number list with the installed version number list to obtain an application version installation result.

[0009] In an embodiment, the determining a corresponding to-be-compared version number list, at least one installation environment and a corresponding installed version number list according to the to-be-compared version information comprises:

[0010] Matching a corresponding to-be-compared version number list from a to-be-compared version list according to the application name and the service group name in the to-be-compared version information; the to-be-compared version list including an application name, a service group name and a version number;

[0011] Matching at least one installation environment from a version environment parameter table according to the application name and the service group name in the to-be-compared version information; the version environment parameter table including an application name, a service group name and a corresponding installation environment;

[0012] Respectively determining a corresponding installed version number list according to an identifier of each installation environment.

[0013] In an embodiment, the comparing the to-be-compared version number list with the installed version number list to obtain an application version installation result comprises:

[0014] Judging whether version numbers in the to-be-compared version number list all exist in the installed version number list;

[0015] If yes, determining that the application version installation result is that the application version is installed successfully in the installation environment;

[0016] If no, generating a batch version number according to the to-be-compared version number list and a preset batch version number rule;

[0017] Judging whether the batch version number exists in the installed version number list; if yes, determining that the application version installation result is that the application version is installed successfully in the installation environment; if no, determining that the application version installation result is that the application version is installed unsuccessfully in the installation environment.

[0018] In an embodiment, the generating a batch version number according to the to-be-compared version number list and a preset batch version number rule comprises:

[0019] Determine the largest version number in the list of version numbers to be compared;

[0020] The first group of numbers in the maximum version number is obtained by replacing the first group of numbers in the preset batch version number with the first group of values.

[0021] In one embodiment, determining whether the batch version number exists in the list of installed version numbers includes:

[0022] Determine whether there is a matching version number in the list of installed version numbers that matches the first and second sets of numbers in the batch version number;

[0023] If so, determine whether the third group of numbers of the version number to be matched is greater than or equal to the third group of numbers of the batch version number, and whether the fourth group of numbers of the version number to be matched is greater than the fourth group of numbers of the batch version number.

[0024] If so, then the application version installation result is confirmed as the application version being successfully installed in the installation environment.

[0025] If not, the application version installation result is determined to be an application version installation failure in the installation environment.

[0026] In one embodiment, the method for batch determining the application version installation results further includes:

[0027] The comparison status flag is determined based on the installation results of the application version corresponding to each installation environment.

[0028] When the application version is successfully installed in all installation environments, the comparison status flag is determined as the first flag;

[0029] When the application version is successfully installed only in some installation environments, the comparison status flag is determined to be the second flag;

[0030] When the application version fails to install in any of the installation environments, the comparison status flag is determined to be the third flag.

[0031] In one embodiment, the method for batch determining the application version installation results further includes:

[0032] A comparison result record table is established based on the comparison version information, including the application name and service group name, the application version installation result, and the comparison status flag.

[0033] Secondly, this application also provides a batch determination device for application version installation results, comprising:

[0034] The module for obtaining version information to be compared is used to obtain version information to be compared, which includes the application name and service group name.

[0035] The comparison information acquisition module is used to determine, based on the comparison version information, the corresponding list of comparison version numbers, at least one installation environment and its corresponding list of installed version numbers;

[0036] The comparison result determination module is used to compare the list of version numbers to be compared with the list of installed version numbers to obtain the application version installation result.

[0037] In one embodiment, the comparison information acquisition module includes:

[0038] The unit for obtaining the list of versions to be compared is used to match the corresponding list of versions to be compared from the list of versions to be compared based on the application name and service group name in the version information to be compared; the list of versions to be compared includes the application name, service group name, and version number.

[0039] The installation environment determination unit is used to match at least one installation environment from the version environment parameter table based on the application name and service group name in the version information to be compared; the version environment parameter table includes the application name, service group name and corresponding installation environment.

[0040] The installed version number list determination unit is used to determine the corresponding installed version number list based on the identifier of each installation environment.

[0041] In one embodiment, the comparison result determination module includes:

[0042] The first comparison unit is used to determine whether all the version numbers in the list of version numbers to be compared exist in the list of installed version numbers.

[0043] A batch version number generation unit is used to generate batch version numbers according to the list of version numbers to be compared and a preset batch version number rule when not all version numbers in the list of version numbers to be compared exist in the list of installed version numbers.

[0044] The second comparison unit is used to determine whether the batch version number exists in the list of installed version numbers;

[0045] The comparison result determination unit is used to determine that the application version installation result is successful in the installation environment when all version numbers in the list of version numbers to be compared exist in the list of installed version numbers or the batch version numbers exist in the list of installed version numbers; and to determine that the application version installation result is unsuccessful in the installation environment when the batch version numbers do not exist in the list of installed version numbers.

[0046] In one embodiment, the batch version number generation unit is specifically used for:

[0047] Determine the largest version number in the list of version numbers to be compared;

[0048] The first group of numbers in the maximum version number is obtained by replacing the first group of numbers in the preset batch version number with the first group of values.

[0049] In one embodiment, the second comparison unit is specifically used for:

[0050] Determine whether there is a matching version number in the list of installed version numbers that matches the first and second sets of numbers; and when the matching version number exists, determine whether the third set of numbers of the matching version number is greater than or equal to the third set of numbers of the batch version number, and whether the fourth set of numbers of the matching version number is greater than the fourth set of numbers of the batch version number.

[0051] The comparison result determination unit is also used for:

[0052] When the version number to be matched exists, and simultaneously satisfies the condition that "the third group of numbers of the version number to be matched is greater than or equal to the third group of numbers of the batch version number, and the fourth group of numbers of the version number to be matched is greater than the fourth group of numbers of the batch version number", the application version installation result is determined to be that the application version was successfully installed in the installation environment; and when the version number to be matched does not exist, or when the version number to be matched exists but does not satisfy the condition that "the third group of numbers of the version number to be matched is greater than or equal to the third group of numbers of the batch version number, and the fourth group of numbers of the version number to be matched is greater than the fourth group of numbers of the batch version number", the application version installation result is determined to be that the application version failed to install in the installation environment.

[0053] In one embodiment, the batch determination device for application version installation results further includes a comparison status flag determination module, used for:

[0054] The comparison status flag is determined based on the installation results of the application version corresponding to each installation environment.

[0055] When the application version is successfully installed in all installation environments, the comparison status flag is determined as the first flag;

[0056] When the application version is successfully installed only in some installation environments, the comparison status flag is determined to be the second flag;

[0057] When the application version fails to install in any of the installation environments, the comparison status flag is determined to be the third flag.

[0058] In one embodiment, the batch determination device for application version installation results further includes a comparison result record table generation module, used for:

[0059] A comparison result record table is established based on the comparison version information, including the application name and service group name, the application version installation result, and the comparison status flag.

[0060] Thirdly, embodiments of this application also provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement a batch determination method for the installation results of any application version provided in this application.

[0061] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements a batch determination method for the installation results of any application version provided in this application.

[0062] The application method and apparatus for batch determination of application version installation results, starting from the complex scenario of checking the version installation of a large number of applications, completes the automated comparison of the installation results of batch version packages by parsing the version generation rules of batch version packages, realizes comprehensive coverage of the inspection of ordinary versions and batch versions, solves the problem that the inspection of the version installation results of a large number of applications previously relied on manual feedback one by one, and improves the efficiency and accuracy of version inspection. Attached Figure Description

[0063] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0064] Figure 1 This is a schematic diagram of a method for batch determining the installation results of the application version provided in this application.

[0065] Figure 2A schematic diagram illustrating the steps for determining the comparison information provided in this application.

[0066] Figure 3 This is a schematic diagram illustrating the steps for obtaining the installation result of the application version provided in this application.

[0067] Figure 4 A schematic diagram illustrating the steps for generating batch version numbers provided in this application.

[0068] Figure 5 A schematic diagram illustrating the steps for batch version number comparison provided in this application.

[0069] Figure 6 Another schematic diagram illustrating the batch determination method for the application version installation results provided in this application.

[0070] Figure 7 A schematic diagram of a device for batch determining the installation results of the application version provided in this application.

[0071] Figure 8 Another schematic diagram of the device for batch determining the installation results of the application version provided in this application.

[0072] Figure 9 Another schematic diagram of the device for batch determining the installation results of the application version provided in this application.

[0073] Figure 10 Another schematic diagram of the device for batch determining the installation results of the application version provided in this application.

[0074] Figure 11 A schematic diagram of an electronic device provided in this application. Detailed Implementation

[0075] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0076] Firstly, this application provides a method for batch determining application version installation results, such as... Figure 1 As shown, the method includes steps S101 to S103:

[0077] Step S101: Obtain the version information to be compared, which includes the application name and service group name.

[0078] The version information to be compared is entered by technical personnel. There can be multiple versions to be compared, and each version to be compared must include at least the application name and service group name.

[0079] Step S102: Determine the corresponding list of version numbers to be compared, at least one installation environment and its corresponding list of installed version numbers based on the version information to be compared.

[0080] In this step, the list of version numbers to be compared, the installation environment, and the list of installed version numbers within the installation environment can all be referred to as comparison information. The list of version numbers to be compared contains all version numbers that the application needs to install under the service group. The application version corresponding to the version number to be compared may or may not be installed under the service group. This step determines multiple version numbers to be compared based on the application name and service group name in the version information to be compared, which together form the list of version numbers to be compared (see Table 1 below); it matches multiple installation environments based on the application name and service group name in the version information to be compared, and obtains multiple installed version numbers based on the identifier of the installation environment, which together form the list of installed version numbers (see Table 3 below). In step S103 of this step, the list of version numbers to be compared is compared with the list of installed version numbers to obtain the application version installation result.

[0081] Specifically, this step compares the version numbers to be compared from the list of version numbers to be compared and the installed version numbers from the list of installed version numbers. During the comparison, it is determined whether each version number in the list of version numbers to be compared exists in its corresponding installed version number. If all version numbers in the list of version numbers to be compared exist in the matched installed version numbers, it means that the version number to be compared was successfully installed in the installation environment. If at least one version number in the list of version numbers to be compared does not exist in the installed version numbers, it means that the version number to be compared failed to be installed in the installation environment.

[0082] In one embodiment, such as Figure 2 As shown, step S102, determining the corresponding list of versions to be compared, at least one installation environment and its corresponding list of installed versions based on the version information to be compared, includes the following steps S1021 to S1023:

[0083] Step S1021: Match the corresponding list of version numbers to be compared from the list of versions to be compared based on the application name and service group name in the version information to be compared; the list of versions to be compared includes the application name, service group name, and version number.

[0084] Specifically, an example of the version list to be compared is shown in Table 1. As can be seen from Table 1, an application can be installed in different service groups (for example, application A in Table 1 can be installed in service group 1 and service group 2), and an application can have multiple different versions installed within the same service group (for example, application A in Table 1 needs to be installed with different versions such as version 11A, version 12A, and version 13A in service group 1). Furthermore, multiple different applications can be installed within the same service group (for example, different versions of application A and application B can be installed in service group 1 in Table 1).

[0085] Table 1: List of Version Numbers to be Compared

[0086]

[0087]

[0088] Once the version information to be compared is obtained, the corresponding list of version numbers to be compared is obtained by querying Table 1 based on the application name and service group name in the version information. For example, assuming the application name in the version information to be compared is application A and the service group name is service group 1, the list of version numbers to be compared includes version number 11A, version number 12A, version number 13A, and so on.

[0089] Step S1022: Match at least one installation environment from the version environment parameter table based on the application name and service group name in the version information to be compared; the version environment parameter table includes the application name, service group name and corresponding installation environment.

[0090] Specifically, the installation environment refers to the environment in which the application is installed within a service group. See Table 2 below for an example of a version environment parameter table:

[0091] Table 2: Version Environment Parameters Table

[0092]

[0093]

[0094] As can be seen from Table 2, there can be multiple installation environments (for example, Table 2 includes two installation environments, Environment 1 and Environment 2), and the installation environments in different service groups can be the same (for example, in Table 2, service group 1 and service group 2 both correspond to Environment 1 and Environment 2).

[0095] When the version information to be compared is obtained, the corresponding installation environment can be obtained by querying Table 2 based on the application name and service group name in the version information. For example, assuming the application name in the version information to be compared is application A and the service group name is service group 1, the corresponding installation environments include environment 1 and environment 2. The installation environments obtained here refer to all installation environments filtered by application name and service group name.

[0096] Step S1023: Determine the corresponding list of installed version numbers based on the identifiers of each installation environment.

[0097] Specifically, the installation environment field records an identifier used in the version installation system to mark the installation environment of a specific application. This identifier allows the retrieval of the version numbers of applications already imported and installed within that environment. The version numbers of installed application versions can be obtained manually from the release system or through an interface provided by the release system. After determining the installation environment in step S1022, the corresponding installed version numbers can be obtained based on the installation environment, thus determining the list of installed version numbers as shown in Table 3 below:

[0098] Table 3: List of Installed Version Numbers

[0099]

[0100]

[0101] The installed version numbers in Table 3 can be any of the version numbers of all application versions installed in the installation environment, or they can be all the version numbers of all application versions installed in the installation environment. For example, when obtaining the installed version numbers in the installation system, a restriction condition for the comparison start date can be set simultaneously. In this way, the version numbers of application versions installed on or after the comparison start date will be obtained, which helps to improve the comparison efficiency.

[0102] It should be noted that Tables 1, 2, and 3 are examples provided by the applicant to better illustrate the list of comparison versions, installation environments, and corresponding installed versions of this application. In actual applications, the application, service group, installation environment under the service group, and application versions installed under different installation environments may differ from those shown in Tables 1, 2, and 3. Those skilled in the art should understand that the above examples are for illustrative purposes only and are not intended to limit this application.

[0103] In one embodiment, such as Figure 3 As shown, step S103 involves comparing the list of versions to be compared with the list of installed versions to obtain the application version installation result, including:

[0104] Step S1031: Obtain the installed version number of the i-th installation environment. The installation environment referred to in this step is all installation environments matched by the application name and service group name in the version information to be compared, with a total number of n, 1 ≤ i ≤ n, where i and n are positive integers. Here, n is chosen as a positive integer to indicate that this application is only applicable to scenarios where at least one installation environment can be matched by the application name and service group name in the version information to be compared. This application is not applicable to application scenarios where no installation environment is matched.

[0105] Step S1032: Determine whether all version numbers in the list of version numbers to be compared exist in the list of installed version numbers; if yes, proceed to step S1035; if no, proceed to step S1033.

[0106] Step S1033: Generate batch version numbers according to the list of version numbers to be compared and the preset batch version number rules;

[0107] Step S1034: Determine whether the batch version number exists in the list of installed version numbers; if yes, proceed to step S1035; if no, proceed to step S1036.

[0108] Step S1035: Determine that the application version installation result is that the application version has been successfully installed in the installation environment;

[0109] Step S1036: Determine that the application version installation result is that the application version failed to install in the installation environment.

[0110] Specifically, this step is a cyclical comparison step. Each cycle compares the version number to be compared with the installed version number in one installation environment, until all installation environments have been compared.

[0111] Taking application A as an example and service group 1 as an example, Table 1 shows that the corresponding version numbers to be compared include V1.2.1.0, V1.2.1.1, V1.2.1.2, and V1.2.1.3. Table 2 shows that the corresponding installation environments include Environment 1 and Environment 2. Table 3 shows that the installed version numbers in Environment 1 are V1.2.1.0, V1.2.1.1, V1.2.1.2, and V1.2.1.3, and the installed version numbers in Environment 2 are V1.2.1.0, V1.2.1.1, and V1.2.1.2.

[0112] At this point, each version number in the comparison list (V1.2.1.0, V1.2.1.1, V1.2.1.2, V1.2.1.3) is compared sequentially with the installed version numbers (V1.2.1.0, V1.2.1.1, V1.2.1.2, V1.2.1.3) corresponding to Environment 1. The comparison result shows that all the comparison version numbers exist in the installed version numbers corresponding to Environment 1. Then, according to step S1035, the application version installation result corresponding to the comparison version number is output as "Environment 1 installed successfully".

[0113] Then, each version number in the comparison (V1.2.1.0, V1.2.1.1, V1.2.1.2, V1.2.1.3) is compared with the installed version number (V1.2.1.0, V1.2.1.1, V1.2.1.2) of the next installation environment—Environment 2. The comparison result is that one of the comparison version numbers (V1.2.1.3) does not exist in the installed version number of Environment 2.

[0114] Considering the possibility of packaging multiple versions into a single batch version package during installation, step S1033 needs to be further executed to generate batch version numbers based on the version numbers to be compared (V1.2.1.0, V1.2.1.1, V1.2.1.2, V1.2.1.3). Then, it is determined whether the batch version number exists in the list of installed version numbers. If yes, then step S1035 outputs the application version installation result corresponding to the version number to be compared as "Environment 2 installed successfully"; otherwise, step S1036 outputs the application version installation result corresponding to the version number to be compared as "Environment 2 installation failed".

[0115] Once environment 1 is compared, return to step S1031 to obtain the installed version number under the next installation environment (environment 2) and repeat the above judgment steps.

[0116] In one embodiment, such as Figure 4 As shown, step S1033, generating batch version numbers according to the list of version numbers to be compared and the preset batch version number rules, includes:

[0117] Step S10331: Determine the largest version number in the list of version numbers to be compared;

[0118] Step S10332: Replace the first group of numbers in the maximum version number with the preset first group value of the batch version number to obtain the batch version number.

[0119] Specifically, taking application name A, service group name service group 1, and installation environment environment 2 as an example, if the version numbers to be compared are V1.2.1.0, V1.2.1.1, V1.2.1.2, and V1.2.1.3, then the maximum version number is determined to be V1.2.1.3 through step S10321. Assuming the preset first group value of the batch version number is 99, then "99" is used to replace the first group of digits "1" in the maximum version number V1.2.1.3, resulting in the batch version number V99.2.1.3.

[0120] Furthermore, such as Figure 5 As shown, step S1034, determining whether the batch version number exists in the list of installed version numbers, includes:

[0121] Step S10341: Determine whether there is a matching version number in the list of installed version numbers that matches the first group of numbers and the second group of numbers. If yes, proceed to step S10342; otherwise, proceed to step S1036.

[0122] Step S10342: Determine whether the third group of numbers of the version number to be matched is greater than or equal to the third group of numbers of the batch version number, and whether the fourth group of numbers of the version number to be matched is greater than the fourth group of numbers of the batch version number; if yes, proceed to step S1035; if no, proceed to step S1036.

[0123] Step S1035: Determine that the application version installation result is that the application version has been successfully installed in the installation environment;

[0124] Step S1036: Determine that the application version installation result is that the application version failed to install in the installation environment.

[0125] Specifically, taking application name A, service group name 1, installation environment 2, and batch version number V99.2.1.3 as an example, the first group of numbers "99" and the second group of numbers "2" in the batch version number are matched against the installed version number in environment 2. If the version number "V99.2.XY" is not matched, where "X" and "Y" can represent any value, then according to step S1036, the application version installation result corresponding to the version number to be compared is output as "Installation of environment 2 failed".

[0126] If the version number "V99.2.XY" is matched, where "X" and "Y" can represent any value, then it is further determined whether "X≤1" and "Y<3" are both true. If they are true, then the application version installation result is output as "Environment 2 installed successfully" according to step S1035. If they are not true, then the application version installation result corresponding to the version number to be compared is output as "Environment 2 installation failed" according to step S1036.

[0127] In one embodiment, such as Figure 6 As shown, the method for batch determining the application version installation results further includes:

[0128] Step S104: Determine the comparison status flag based on the application version installation results corresponding to each installation environment.

[0129] Specifically, the comparison status flag in this step corresponds one-to-one with each piece of information about the version to be compared. The determination of the comparison status flag is related to the installation results of the application version corresponding to the version number to be compared in multiple installation environments. When the application version is successfully installed in all installation environments, the comparison status flag is determined as the first flag; when the application version is successfully installed in only some installation environments, the comparison status flag is determined as the second flag; when the application version is not successfully installed in any installation environment, the comparison status flag is determined as the third flag. The values ​​of the first flag, second flag, and third flag can be, for example, "1", "2", and "3", or other numbers, letters, or combinations thereof.

[0130] Taking application A, service group 1, and installation environments 1 and 2 as an example, if the application version corresponding to the version number to be compared is successfully installed in both environment 1 and environment 2, then the comparison status flag corresponding to application A and service group 1 is determined as the first flag; if the application version corresponding to the version number to be compared is successfully installed in environment 1 but fails to install in environment 2, then the comparison status flag corresponding to application A and service group 1 is determined as the second flag; if the application version corresponding to the version number to be compared fails to install in both environment 1 and environment 2, then the comparison status flag corresponding to application A and service group 1 is determined as the third flag.

[0131] In addition, as mentioned above, this application is only applicable to scenarios where at least one installation environment can be matched through the application name and service group name in the version information to be compared. This application is not applicable to application scenarios where no installation environment is matched. In order to record the results, this application also assigns a fourth flag as the corresponding comparison status flag to the version information to be compared that does not match an installation environment. For example, the fourth flag can be set to a value of "0".

[0132] In one embodiment, please continue to see Figure 6 The method for batch determining the application version installation results further includes:

[0133] Step S105: Establish a comparison result record table based on the comparison version information, including the application name and service group name, the application version installation result, and the comparison status flag.

[0134] Specifically, an example of a comparison result record table is shown in Table 4. This table is intended to demonstrate the correspondence between comparison status flags and application version installation results, as well as the format of the comparison result record table. To distinguish it from the examples in the previous embodiments, this embodiment uses an application name of P-AAA, a service group name of normal service group, and an installation environment of one overseas partition and two overseas partitions as examples for illustration.

[0135] Table 4: Comparison Result Record Table

[0136]

[0137]

[0138] In fact, after establishing the comparison result record table in this embodiment, it can be further used for the analysis and display of the comparison results. The key points of interest after batch checking the application version installation results can all be filtered out in the comparison result record table. The key points of interest are mainly as follows:

[0139] First, identify which applications and their service groups have been installed, and which have not, specifying the deployment environment for those not yet installed. Then, filter the comparison results table to display a list of applications and service groups with a comparison status flag of 1 as those already installed, and a list of applications and service groups with a comparison status flag that is neither 0 nor 1 as those not yet installed. Finally, filter the comparison results field to identify and display the environments where installation is incomplete.

[0140] Second, which application and service groups have been included in the version check, and their proportion in the current version list. Filter and record the results and records with a comparison status flag of 0 in the comparison results record table, and divide the number of records by the total number of records in the comparison results record table to obtain the proportion. This result reflects the coverage of the version comparison.

[0141] Third, the percentage of applications and services included in the version check that have completed installation. The number of records with a comparison status flag of neither 0 nor 1 in the comparison result record table is filtered, and then divided by the number of records with a comparison status flag of non-0 in the record table to obtain the percentage. This result reflects the pass rate of the version comparison.

[0142] The above filtering can be performed by technicians who input the filtering criteria, and the computer will automatically complete the filtering based on the criteria, calculate and analyze the results, and present them intuitively to the technicians.

[0143] The batch determination method for application version installation results in this application starts from the complex scenario of checking the version installation of a large number of applications. By parsing the version generation rules of batch version packages, it completes the automated comparison of the installation results of batch version packages, realizes comprehensive coverage of the checks of ordinary versions and batch versions, solves the problem that the previous checks of the version installation results of a large number of applications relied on manual feedback one by one, and improves the efficiency and accuracy of version checks.

[0144] Based on the same inventive concept, this application also provides a batch determination device for application version installation results, which can be used to implement the method described in the above embodiments, as described in the following embodiments. Since the principle of the batch determination device for application version installation results is similar to that of the batch determination method for application version installation results, the implementation of the batch determination device for application version installation results can refer to the implementation of the batch determination method for application version installation results, and repeated details will not be elaborated further. As used below, the terms "unit" or "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the system described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0145] Secondly, this application also provides a device for batch determining application version installation results, such as... Figure 7 As shown, the device includes:

[0146] The comparison version information acquisition module 201 is used to acquire the comparison version information, which includes the application name and service group name;

[0147] The comparison information acquisition module 202 is used to determine, based on the comparison version information, a corresponding list of comparison version numbers, at least one installation environment and its corresponding list of installed version numbers;

[0148] The comparison result determination module 203 is used to compare the list of version numbers to be compared with the list of installed version numbers to obtain the application version installation result.

[0149] In one embodiment, such as Figure 8 As shown, the comparison information acquisition module 202 includes:

[0150] The version number acquisition unit 2021 is used to match the corresponding version number list to be compared from the version list to be compared based on the application name and service group name in the version information to be compared; the version list to be compared includes the application name, service group name and version number.

[0151] The installation environment determination unit 2022 is used to match at least one installation environment from the version environment parameter table based on the application name and service group name in the version information to be compared; the version environment parameter table includes the application name, service group name and corresponding installation environment.

[0152] The installed version number list determination unit 2023 is used to determine the corresponding installed version number list according to the identifier of each installation environment.

[0153] In one embodiment, such as Figure 9 As shown, the comparison result determination module 203 includes:

[0154] The first comparison unit 2031 is used to determine whether all the version numbers in the list of version numbers to be compared exist in the list of installed version numbers.

[0155] The batch version number generation unit 2032 is used to generate batch version numbers according to the list of version numbers to be compared and the preset batch version number rules when not all version numbers in the list of version numbers to be compared exist in the list of installed version numbers.

[0156] The second comparison unit 2033 is used to determine whether the batch version number exists in the list of installed version numbers;

[0157] The comparison result determination unit 2034 is used to determine that the application version installation result is that the application version is successfully installed in the installation environment when all version numbers in the list of version numbers to be compared exist in the list of installed version numbers or the batch version numbers exist in the list of installed version numbers; and to determine that the application version installation result is that the application version fails to install in the installation environment when the batch version numbers do not exist in the list of installed version numbers.

[0158] In one embodiment, the batch version number generation unit 2032 is specifically used for:

[0159] Determine the largest version number in the list of version numbers to be compared;

[0160] The first group of numbers in the maximum version number is obtained by replacing the first group of numbers in the preset batch version number with the first group of values.

[0161] In one embodiment, the second comparison unit 2033 is specifically used for:

[0162] Determine whether there is a matching version number in the list of installed version numbers that matches the first and second sets of numbers; and when a matching version number exists, determine whether the third set of numbers of the matching version number is greater than or equal to the third set of numbers of the batch version number, and whether the fourth set of numbers of the matching version number is greater than the fourth set of numbers of the batch version number.

[0163] The comparison result determination unit 2034 is further configured to:

[0164] When a version number to be matched exists, and the conditions are met that "the third group of numbers of the version number to be matched is greater than or equal to the third group of numbers of the batch version number, and the fourth group of numbers of the version number to be matched is greater than the fourth group of numbers of the batch version number", the application version installation result is determined to be that the application version is successfully installed in the installation environment.

[0165] If the version number to be matched does not exist, or if the version number to be matched exists but does not meet the condition that "the third group of numbers of the version number to be matched is greater than or equal to the third group of numbers of the batch version number, and the fourth group of numbers of the version number to be matched is greater than the fourth group of numbers of the batch version number", then the application version installation result is determined to be that the application version failed to install in the installation environment.

[0166] In one embodiment, such as Figure 10 As shown, the batch determination device for application version installation results further includes a comparison status flag determination module 204, used for:

[0167] The comparison status flag is determined based on the installation results of the application version corresponding to each installation environment.

[0168] When the application version is successfully installed in all installation environments, the comparison status flag is determined as the first flag;

[0169] When the application version is successfully installed only in some installation environments, the comparison status flag is determined to be the second flag;

[0170] When the application version fails to install in any of the installation environments, the comparison status flag is determined to be the third flag.

[0171] In one embodiment, please continue to see Figure 10 The batch determination device for application version installation results further includes a comparison result record table generation module 205, used for:

[0172] A comparison result record table is established based on the comparison version information, including the application name and service group name, the application version installation result, and the comparison status flag.

[0173] The batch determination device for application version installation results in this application starts from the complex scenario of checking the version installation of a large number of applications. By parsing the version generation rules of batch version packages, it completes the automated comparison of the installation results of batch version packages, realizes the comprehensive coverage of checking ordinary versions and batch versions, solves the problem that the previous checking of the version installation results of a large number of applications relied on manual feedback one by one, and improves the efficiency and accuracy of version checking.

[0174] Thirdly, this application also provides an electronic device, see [link to application]. Figure 11 The electronic device 100 specifically includes:

[0175] The system includes a central processing unit (CPU) 110, a memory 120, a communication module 130, an input unit 140, an output unit 150, and a power supply 160.

[0176] The memory 120, communication module 130, input unit 140, output unit 150, and power supply 160 are all connected to the central processing unit 110. The memory 120 stores a computer program, which the central processing unit 110 can call. When the central processing unit 110 executes the computer program, it implements all the steps in the batch determination method for application version installation results in the above embodiments.

[0177] Fourthly, embodiments of this application also provide a computer-readable storage medium for storing a computer program that can be executed by a processor. When executed by a processor, the computer program implements the batch determination method for the installation results of any application version provided in this application.

[0178] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The various embodiments in this specification are described in a progressive manner; similar or identical parts between embodiments can be referred to mutually, and each embodiment focuses on describing the differences from other embodiments. In particular, for hardware + program embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the description of the method embodiments. Although the embodiments of this specification provide the method operation steps as shown in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-inventive means. The order of steps listed in the embodiments is merely one of many possible execution orders and does not represent the only execution order. In actual device or terminal product execution, the methods can be executed sequentially according to the embodiments or drawings, or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even a distributed data processing environment). The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitations, the presence of other identical or equivalent elements in the process, method, product, or apparatus that includes said elements is not excluded. For ease of description, the above apparatus is described in terms of functional modules. Of course, in implementing the embodiments of this specification, the functions of each module can be implemented in one or more software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0179] In this specification, the illustrative expressions of the terms used do not necessarily refer to the same embodiments or examples. Furthermore, those skilled in the art can combine and integrate different embodiments or examples described in this specification, as well as features of different embodiments or examples, without contradiction. The above descriptions are merely embodiments of this specification and are not intended to limit the embodiments of this specification. Various modifications and variations can be made to the embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the embodiments of this specification should be included within the scope of the claims of the embodiments of this specification.

Claims

1. A method for batch determining application version installation results, characterized in that, include: Obtain the version information to be compared, which includes the application name and service group name; Based on the version information to be compared, determine the corresponding list of version numbers to be compared, at least one installation environment and its corresponding list of installed version numbers; The application version installation result is obtained by comparing the list of version numbers to be compared with the list of installed version numbers. The step of comparing the list of version numbers to be compared with the list of installed version numbers to obtain the application version installation result includes: determining whether all version numbers in the list of version numbers to be compared exist in the list of installed version numbers; if yes, then determining that the application version installation result is that the application version is successfully installed in the installation environment; if no, then generating batch version numbers according to the list of version numbers to be compared and preset batch version number rules; determining whether the batch version numbers exist in the list of installed version numbers; if yes, then determining that the application version installation result is that the application version is successfully installed in the installation environment; if no, then determining that the application version installation result is that the application version failed to install in the installation environment. The step of generating batch version numbers based on the list of version numbers to be compared and preset batch version number rules includes: determining the maximum version number in the list of version numbers to be compared; replacing the first group of numbers in the maximum version number with the preset first group value of the batch version number to obtain the batch version number.

2. The method for batch determination of application version installation results according to claim 1, characterized in that, The step of determining the corresponding list of versions to be compared, at least one installation environment and its corresponding list of installed versions based on the version information to be compared includes: The application name and service group name in the version information to be compared are used to match the corresponding version number list from the version list to be compared; the version list to be compared includes the application name, service group name, and version number; Based on the application name and service group name in the version information to be compared, at least one installation environment is matched from the version environment parameter table; the version environment parameter table includes the application name, service group name, and corresponding installation environment. The corresponding list of installed version numbers is determined based on the identifiers of each installation environment.

3. The method for batch determination of application version installation results according to claim 1, characterized in that, The step of determining whether the batch version number exists in the list of installed version numbers includes: Determine whether there is a matching version number in the list of installed version numbers that matches the first and second sets of numbers in the batch version number; If so, determine whether the third group of numbers of the version number to be matched is greater than or equal to the third group of numbers of the batch version number, and whether the fourth group of numbers of the version number to be matched is greater than the fourth group of numbers of the batch version number. If so, then the application version installation result is confirmed as the application version being successfully installed in the installation environment. If not, the application version installation result is determined to be an application version installation failure in the installation environment.

4. The method for batch determination of application version installation results according to claim 1, characterized in that, Also includes: The comparison status flag is determined based on the installation results of the application version corresponding to each installation environment. When the application version is successfully installed in all installation environments, the comparison status flag is determined as the first flag; When the application version is successfully installed only in some installation environments, the comparison status flag is determined to be the second flag; When the application version fails to install in any of the installation environments, the comparison status flag is determined to be the third flag.

5. The method for batch determination of application version installation results according to claim 4, characterized in that, Also includes: A comparison result record table is established based on the comparison version information, including the application name and service group name, the application version installation result, and the comparison status flag.

6. A device for batch determining application version installation results, characterized in that, include: The module for obtaining version information to be compared is used to obtain version information to be compared, which includes the application name and service group name. The comparison information acquisition module is used to determine, based on the comparison version information, the corresponding list of comparison version numbers, at least one installation environment and its corresponding list of installed version numbers; The comparison result determination module is used to compare the list of version numbers to be compared with the list of installed version numbers to obtain the application version installation result; The comparison result determination module includes: a first comparison unit, used to determine whether all version numbers in the list of version numbers to be compared exist in the list of installed version numbers; a batch version number generation unit, used to generate batch version numbers according to the list of version numbers to be compared and a preset batch version number rule when not all version numbers in the list of version numbers to be compared exist in the list of installed version numbers; a second comparison unit, used to determine whether the batch version numbers exist in the list of installed version numbers; and a comparison result determination unit, used to determine that the application version installation result is successful installation in the installation environment when all version numbers in the list of version numbers to be compared exist in the list of installed version numbers or the batch version numbers exist in the list of installed version numbers; and to determine that the application version installation result is unsuccessful installation in the installation environment when the batch version numbers do not exist in the list of installed version numbers. Specifically, the batch version number generation unit is used to: determine the largest version number in the list of version numbers to be compared; and replace the first group of numbers in the largest version number with a preset first group value of the batch version number to obtain the batch version number.

7. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the batch determination method for the application version installation results as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the batch determination method for application version installation results according to any one of claims 1 to 5.

9. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the batch determination method for the application version installation results as described in any one of claims 1 to 5.

Images