Batch automatic online method and device for application versions

Abstract

The invention provides a batch automatic online method for application versions. The method comprises the following steps: acquiring a plurality of version numbers corresponding to applications; and obtaining a version package and a configuration file corresponding to each version number from a version library based on the version number. And splitting each version package to obtain a version package set corresponding to the version package, wherein the version package set comprises a software component, a function module and a version number. And sending the software component and the version number in each version package set to a software component verification host. And sending the function module and the version number in each version package set to a function module verification host. And obtaining a first verification result sent by the software component verification host and a second verification result sent by the function module verification host. And the version package corresponding to the version number which is indicated to pass verification in the first verification result and the second verification result is online. According to the method provided by the invention, batch automatic online of the application versions can be efficiently carried out.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method and device for automatically launching batches of application versions. Background Art

[0002] With the continuous development of science and technology, software versions are constantly being updated. A software may have dozens or even hundreds of different versions. Due to different operating systems, an application may have multiple different versions, and different versions of applications cannot be launched on unmatched devices. For example, the first mobile phone uses the first system, the second mobile phone uses the second system, the application has developed a first version for the first system, and a second version for the second system. The first version of the application cannot run on the second mobile phone. This is particularly prominent on the public cloud platform. The business environment of the public cloud platform is relatively complex, and there are many products involved. Often a public cloud platform consists of several or even dozens of nodes, and each node involves dozens or even hundreds of CVK hosts. In addition, since the cloud platform involves a wide range of businesses and many products, it also supports many services and clusters. For large-scale cluster services such as cloud platforms, how to ensure the rapid and stable launch of versions is particularly important. Relevant technologies need to be verified before the version is launched, but the relevant technologies cannot batch verify the version package, so the batch automatic launch of application versions is low.

[0003] Therefore, how to improve the efficiency of batch automatic launch of application versions has become a technical problem that technical personnel in this field urgently need to solve. Summary of the invention

[0004] Based on the above problems, the present application provides a method and device for batch automatic launch of application versions to improve the efficiency of batch automatic launch of application versions.

[0005] The present application provides a method for automatically launching a batch of application versions, the method comprising the following steps:

[0006] Get multiple version numbers corresponding to the application;

[0007] Based on the version number, obtain the version package and configuration file corresponding to each version number from the version library;

[0008] Splitting each version package to obtain a version package set corresponding to the version package, the version package set including software components, functional modules and version numbers;

[0009] Sending the software components and version numbers in each of the version package sets to a software component verification host;

[0010] Based on the software component verification host, verify the plurality of software components according to the version number to obtain a first verification result;

[0011] Sending the function modules and version numbers in each version package set to a function module verification host;

[0012] Based on the function module verification host verifies the plurality of function modules according to the version number to obtain a second verification result;

[0013] Obtaining a first verification result sent by the software component verification host and a second verification result sent by the function module verification host;

[0014] The version package corresponding to the version number indicated as having passed the verification in both the first verification result and the second verification result is put online.

[0015] In a possible implementation, the method further includes:

[0016] Sending the first verification result and the second verification result to a version database, wherein the version database stores each version number, version package, and configuration file of the application;

[0017] A version repair result is generated based on the first verification result and the second verification result, where the version repair result is used to indicate a repair of a version number corresponding to the application.

[0018] In a possible implementation, the method further includes:

[0019] Obtain the version repair result;

[0020] If the first verification result corresponding to the target version number indicated in the version repair result fails, repairing the software component corresponding to the target version number;

[0021] If the version repair result indicates that the second verification result corresponding to the target version number fails, the functional module corresponding to the target version number is repaired.

[0022] In a possible implementation, the method further includes:

[0023] Receive the version package after the repair is completed;

[0024] The repaired version package is put online for the second time.

[0025] The present application also provides a device for automatically launching application versions in batches, the device comprising:

[0026] A first acquisition module, used to acquire multiple version numbers corresponding to the application;

[0027] A second acquisition module is used to acquire the version package and configuration file corresponding to each version number from the version library based on the version number;

[0028] A splitting module, used to split each version package to obtain a version package set corresponding to the version package, wherein the version package set includes software components, functional modules and version numbers;

[0029] A first sending module, used for sending the software components and version numbers in each version package set to a software component verification host;

[0030] A first verification module, configured to verify the plurality of software components according to version numbers based on the software component verification host to obtain a first verification result;

[0031] A second sending module, used for sending the function modules and version numbers in each version package set to a function module verification host;

[0032] A second verification module, configured to verify the function modules according to the version numbers of the function modules based on the function module verification host to obtain a second verification result;

[0033] A receiving module, used for obtaining a first verification result sent by the software component verification host and a second verification result sent by the function module verification host;

[0034] The online module is used to bring online the version package corresponding to the version number indicated as having passed the verification in both the first verification result and the second verification result.

[0035] In a possible implementation manner, the device further includes a repair determination module, and the repair determination module is specifically configured to:

[0036] Sending the first verification result and the second verification result to a version database, wherein the version database stores each version number, version package, and configuration file of the application;

[0037] A version repair result is generated based on the first verification result and the second verification result, where the version repair result is used to indicate a repair of a version number corresponding to the application.

[0038] In a possible implementation manner, the device further includes a repair module, and the repair module is specifically configured to:

[0039] Obtain the version repair result;

[0040] If the first verification result corresponding to the target version number indicated in the version repair result fails, repairing the software component corresponding to the target version number;

[0041] If the version repair result indicates that the second verification result corresponding to the target version number fails, the functional module corresponding to the target version number is repaired.

[0042] In a possible implementation, the device further includes a secondary online module, and the secondary online module is specifically configured to:

[0043] Receive the version package after the repair is completed;

[0044] The repaired version package is put online for the second time.

[0045] The present application also provides an electronic device, the electronic device comprising a processor and a memory:

[0046] The memory is used to store a computer program and transmit the computer program to the processor;

[0047] The processor is used to execute the steps of the above-mentioned method for automatically launching batches of application versions according to the instructions in the computer program.

[0048] The present application also provides a computer-readable storage medium, which is used to store a computer program. When the computer program is executed by an electronic device, it implements the steps of the above-mentioned method for automatically launching batches of application versions.

[0049] Compared with the prior art, this application has the following beneficial effects:

[0050] The method provided in the present application significantly improves the efficiency of version launch by obtaining multiple version numbers and automatically processing the classification, verification and launch of version packages. The traditional manual verification and launch process is often time-consuming, while the automated method of the present application can quickly complete the batch processing of version packages, reducing the need for manual intervention and shortening the launch cycle. The present application adopts a double verification mechanism to verify software components and functional modules respectively to ensure that all launched version packages can operate normally in different environments. This strict verification process greatly reduces the risk of launch failure due to version incompatibility and improves the stability and reliability of the version. In complex environments such as public cloud platforms, the collaborative work of multiple nodes and dozens of CVK hosts makes version management particularly important. The present application can effectively match each version with the corresponding hardware and operating system, ensure compatibility between different versions, and meet the cloud platform's demand for fast and stable version launch. The method provided in the present application can improve the efficiency of batch automatic launch of application versions. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0052] Figure 1 A flowchart of a method for automatically launching a batch of application versions provided in an embodiment of the present application;

[0053] Figure 2 A schematic diagram of the structure of a device for automatically launching a batch of application versions provided in an embodiment of the present application. DETAILED DESCRIPTION

[0054] As described above, the relevant technology needs to be verified before the version is launched, but the relevant technology cannot verify the version packages in batches, so the automatic batch launch of application versions is low.

[0055] In the process of batch automatic launch of application versions, it takes a lot of time to verify multiple different application versions. However, after research, it was found that some content in the version packages of different application versions is similar, such as software components and functional modules. The relevant technology verifies in units of version packages. When using this verification method for batch launch, the number of devices corresponding to the number of version packages needs to be verified, which seriously slows down the efficiency of batch automatic launch of application versions.

[0056] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings 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 ordinary technicians in this field without creative work are within the scope of protection of this application.

[0057] It is understandable that the method provided by the present application can be applied to a processing device, which is a processing device that can obtain multiple version numbers corresponding to an application, for example, a terminal device or server that can obtain a version package and a configuration file corresponding to each version number from a version library based on the version number. The method provided by the present application can be executed independently by a terminal device or a server, or it can be applied to a network scenario in which a terminal device and a server communicate, and is executed by the cooperation of a terminal device and a server. Among them, the terminal device can be a computer, a mobile phone or other device. The server can be understood as an application server or a Web server. In actual deployment, the server can be a stand-alone server or a cluster server.

[0058] Figure 1 A flowchart of a method for automatically launching a batch of application versions provided in an embodiment of the present application, the method comprising the following steps:

[0059] S101: Obtain multiple version numbers corresponding to the application.

[0060] The processing device obtains multiple version numbers corresponding to the application. The version numbers may correspond to different operating systems, for example, UCO version, UCA version, and UCS version.

[0061] S102: Obtain the version package and configuration file corresponding to each version number from the version library based on the version number.

[0062] The processing device obtains the version package and configuration file corresponding to each version number from the version library based on the version number. It can be understood that the version package has a corresponding configuration file, which can include the configuration of the version package when applied, such as the installation path and whether to automatically delete the version package after installation.

[0063] S103: Split each version package to obtain a version package set corresponding to the version package.

[0064] The processing device splits each version package to obtain a version package set corresponding to the version package, which includes software components, functional modules and version numbers. Software components are the software parts corresponding to the application, mostly program codes. Functional modules are the parts corresponding to the functions that can be implemented by the application, which may include UI, code and reference functions, etc.

[0065] S104: Send the software components and version numbers in each version package set to a software component verification host.

[0066] The processing device sends the software components and version numbers in each version package set to the software component verification host. The software component verification host can verify the software components under different operating systems.

[0067] S105: Based on the software component verification, the host verifies the multiple software components according to the version numbers to obtain a first verification result.

[0068] The processing device verifies the plurality of software components according to the version numbers based on the software component verification host to obtain a first verification result.

[0069] Even if they are different operating systems, the running logic of the software components of the same application is the same. Therefore, the software component verification host can perform logical verification on the software components under different operating systems.

[0070] S106: Send the function modules and version numbers in each version package set to a function module verification host.

[0071] The processing device sends the function modules and version numbers in each version package set to the function module verification host. The function module verification host can verify the function modules under different operating systems.

[0072] S107: Based on the function module verification, the host verifies the multiple function modules according to the version numbers to obtain a second verification result.

[0073] The processing device may verify the plurality of function modules according to the version numbers based on the function module verification host to obtain a second verification result.

[0074] Even if they are different operating systems, the functions to be implemented by the same application are the same. Therefore, the software component verification host can verify the functional implementation of the functional modules under different operating systems.

[0075] S108: Obtain a first verification result sent by a software component verification host and a second verification result sent by a function module verification host.

[0076] The processing device obtains a first verification result sent by a software component verification host and a second verification result sent by a function module verification host, so as to perform subsequent operations based on the first verification result and the second verification result.

[0077] S109: Put online the version package corresponding to the version number indicated as having passed the verification in both the first verification result and the second verification result.

[0078] The processing device may bring online a version package corresponding to a version number indicated as having passed verification in both the first verification result and the second verification result.

[0079] If the first verification result indicates that there is no problem with the running logic of the software component corresponding to the application version number, and the second verification result indicates that there is no problem with the function implemented by the function module corresponding to the application version number, then the version package corresponding to the version number can be put online. The processing device batches all the version packages that can be put online.

[0080] For the sake of sustainability and scalability of the application, in a possible implementation, the processing device may send the first verification result and the second verification result to a version database, which stores each version number, version package, and configuration file of the application. A version repair result is generated based on the first verification result and the second verification result, and the version repair result is used to indicate the repair of the corresponding version number of the application.

[0081] For version packages that have problems and cannot be put online in batches temporarily, in a possible implementation, the processing device can obtain a version repair result. If the first verification result corresponding to the target version number indicated in the repair result fails, the software component corresponding to the target version number is repaired.

[0082] If the first verification result corresponding to the version number indicates that there is a problem in the running logic of the software component corresponding to the application version number, the processing device may repair the software component in the version package corresponding to the version number.

[0083] If the version repair result indicates that the second verification result corresponding to the target version number fails, the functional module corresponding to the target version number is repaired.

[0084] If the second verification result corresponding to the version number indicates that there is a problem in the function implementation of the function module corresponding to the application version number, the processing device may repair the function module in the version package corresponding to the version number.

[0085] After the repair is performed, the repaired version package can be put online. In a possible implementation, the processing device can receive the repaired version package and put the repaired version package online again.

[0086] The method provided in the present application significantly improves the efficiency of version launch by obtaining multiple version numbers and automatically processing the classification, verification and launch of version packages. The traditional manual verification and launch process is often time-consuming, while the automated method of the present application can quickly complete the batch processing of version packages, reducing the need for manual intervention and shortening the launch cycle. The present application adopts a double verification mechanism to verify software components and functional modules respectively to ensure that all launched version packages can operate normally in different environments. This strict verification process greatly reduces the risk of launch failure due to version incompatibility and improves the stability and reliability of the version. In complex environments such as public cloud platforms, the collaborative work of multiple nodes and dozens of CVK hosts makes version management particularly important. The present application can effectively match each version with the corresponding hardware and operating system, ensure compatibility between different versions, and meet the cloud platform's demand for fast and stable version launch. The method provided in the present application can improve the efficiency of batch automatic launch of application versions.

[0087] The present application also provides a Figure 2 The schematic diagram of the structure of the batch automatic online device of the application version shown in the figure, the batch automatic online device 200 of the application version includes the following modules:

[0088] A first acquisition module 201 is used to acquire multiple version numbers corresponding to the application;

[0089] A second acquisition module 202 is used to acquire a version package and a configuration file corresponding to each version number from a version library based on the version number;

[0090] A splitting module 203 is used to split each version package to obtain a version package set corresponding to the version package, wherein the version package set includes software components, function modules and version numbers;

[0091] A first sending module 2042, configured to send the software components and version numbers in each of the version package sets to a software component verification host;

[0092] A first verification module 205, configured to verify the plurality of software components according to the version numbers based on the software component verification host to obtain a first verification result;

[0093] A second sending module 206, configured to send the function modules and version numbers in each version package set to a function module verification host;

[0094] A second verification module 207, configured to verify the function modules according to the version numbers of the function modules based on the function module verification host to obtain a second verification result;

[0095] A receiving module 208, configured to obtain a first verification result sent by the software component verification host and a second verification result sent by the function module verification host;

[0096] The online module 209 is used to bring online the version package corresponding to the version number indicated as having passed the verification in both the first verification result and the second verification result.

[0097] In a possible implementation manner, the device further includes a repair determination module, and the repair determination module is specifically configured to:

[0098] Sending the first verification result and the second verification result to a version database, wherein the version database stores each version number, version package, and configuration file of the application;

[0099] A version repair result is generated based on the first verification result and the second verification result, where the version repair result is used to indicate a repair of a version number corresponding to the application.

[0100] In a possible implementation manner, the device further includes a repair module, and the repair module is specifically configured to:

[0101] Obtain the version repair result;

[0102] If the first verification result corresponding to the target version number indicated in the version repair result fails, repairing the software component corresponding to the target version number;

[0103] If the version repair result indicates that the second verification result corresponding to the target version number fails, the functional module corresponding to the target version number is repaired.

[0104] In a possible implementation manner, it is characterized in that the device further includes a secondary online module, and the secondary online module is specifically used to:

[0105] Receive the version package after the repair is completed;

[0106] The repaired version package is put online for the second time.

[0107] The device provided by the present application significantly improves the efficiency of version launch by obtaining multiple version numbers and automatically processing the classification, verification and launch of version packages. The traditional manual verification and launch process is often time-consuming, while the automated method of the present application can quickly complete the batch processing of version packages, reducing the need for manual intervention and shortening the launch cycle. The present application adopts a double verification mechanism to verify software components and functional modules respectively to ensure that all launched version packages can operate normally in different environments. This strict verification process greatly reduces the risk of launch failure due to version incompatibility and improves the stability and reliability of the version. In complex environments such as public cloud platforms, the collaborative work of multiple nodes and dozens of CVK hosts makes version management particularly important. The present application can effectively match each version with the corresponding hardware and operating system, ensure compatibility between different versions, and meet the cloud platform's demand for fast and stable version launch. The method provided by the present application can improve the efficiency of batch automatic launch of application versions.

[0108] An embodiment of the present application also provides a device for automatically launching application versions in batches, wherein the device includes a memory and a processor, the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the steps of the method for automatically launching application versions in batches described in any embodiment of the present application.

[0109] In practical applications, the computer-readable storage medium may be any combination of one or more computer-readable media, which may be a computer-readable signal medium or a computer-readable storage medium.

[0110] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device, or device.

[0111] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0112] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0113] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0114] It should be noted that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely schematic, in which the unit described as a separate component may or may not be physically separated, and the component prompted as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.

[0115] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for automatically launching a batch of application versions, characterized in that: include: Get multiple version numbers corresponding to the application; Based on the version number, obtain the version package and configuration file corresponding to each version number from the version library; Splitting each version package to obtain a version package set corresponding to the version package, the version package set including software components, functional modules and version numbers; Sending the software components and version numbers in each of the version package sets to a software component verification host; Based on the software component verification host, verify the plurality of software components according to the version number to obtain a first verification result; Sending the function modules and version numbers in each version package set to a function module verification host; Based on the function module verification host verifies the plurality of function modules according to the version number to obtain a second verification result; Obtaining a first verification result sent by the software component verification host and a second verification result sent by the function module verification host; The version package corresponding to the version number indicated as having passed the verification in both the first verification result and the second verification result is put online.

2. The method according to claim 1, characterized in that: The method further comprises: Sending the first verification result and the second verification result to a version database, wherein the version database stores each version number, version package, and configuration file of the application; A version repair result is generated based on the first verification result and the second verification result, where the version repair result is used to indicate a repair of a version number corresponding to the application.

3. The method according to claim 2, characterized in that The method further comprises: Obtain the version repair result; If the first verification result corresponding to the target version number indicated in the version repair result fails, repairing the software component corresponding to the target version number; If the version repair result indicates that the second verification result corresponding to the target version number fails, the functional module corresponding to the target version number is repaired.

4. The method according to claim 3, characterized in that: The method further comprises: Receive the version package after the repair is completed; The repaired version package is put online for the second time.

5. A device for automatically launching batches of application versions, characterized in that: include: A first acquisition module, used to acquire multiple version numbers corresponding to the application; A second acquisition module is used to acquire the version package and configuration file corresponding to each version number from the version library based on the version number; A splitting module, used to split each version package to obtain a version package set corresponding to the version package, wherein the version package set includes software components, functional modules and version numbers; A first sending module, configured to send the software components and version numbers in each of the version package sets to a software component verification host; A first verification module, configured to verify the plurality of software components according to version numbers based on the software component verification host to obtain a first verification result; A second sending module, used for sending the function modules and version numbers in each version package set to a function module verification host; A second verification module, configured to verify the function modules according to the version numbers of the function modules based on the function module verification host to obtain a second verification result; A receiving module, used for obtaining a first verification result sent by the software component verification host and a second verification result sent by the function module verification host; The online module is used to bring online the version package corresponding to the version number indicated as having passed the verification in both the first verification result and the second verification result.

6. The device according to claim 5, characterized in that The device further includes a repair determination module, and the repair determination module is specifically used to: Sending the first verification result and the second verification result to a version database, wherein the version database stores each version number, version package, and configuration file of the application; A version repair result is generated based on the first verification result and the second verification result, where the version repair result is used to indicate a repair of a version number corresponding to the application.

7. The device according to claim 6, characterized in that The device further comprises a repair module, wherein the repair module is specifically configured to: Obtain the version repair result; If the first verification result corresponding to the target version number indicated in the version repair result fails, repairing the software component corresponding to the target version number; If the version repair result indicates that the second verification result corresponding to the target version number fails, the functional module corresponding to the target version number is repaired.

8. The device according to claim 7, characterized in that The device further includes a secondary online module, which is specifically used for: Receive the version package after the repair is completed; The repaired version package is put online for the second time.

9. An electronic device, characterized in that: comprising a memory and a processor, wherein: The memory is used to store the computer program; The processor is used to execute the computer program to implement the method for automatically launching application versions in batches as described in any one of claims 1 to 4.

10. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein when the computer program is executed by a processor, the method for automatically launching application versions in batches as described in any one of claims 1 to 4 is implemented.

Images