Product component upgrade method and related equipment

Abstract

The embodiment of the present application discloses a product component upgrade method and related equipment for improving the upgrade efficiency of product components. The method of the embodiment of the present application includes: among the product components to be upgraded contained in multiple product code repositories, detecting multiple target product components to be upgraded that are associated with the same target compatible file, and determining the target version product component to which the target product component to be upgraded needs to be upgraded; obtaining the target version product component from a first preset server, and obtaining the target compatible file from a second preset server; running the target version product component based on the target compatible file to detect the operation status of the target version product component; if the operation status of the target version product component is normal, upgrading each of the target product components to be upgraded according to the target compatible file and the target version product component.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of software, and in particular to a product component upgrading method and related equipment. Background Art

[0002] In order to meet the front-end security requirements, developers need to upgrade components of different product lines or different forms of products in the same product line. If the upgraded components are incompatible with the rest of the product components, it is necessary to manually screen and detect the compatible files required for the upgrade, and add the compatible files to the product code repository to ensure the normal operation of the upgraded product components.

[0003] In actual applications, product components of different products may require compatible files of the same version. If the components of these different products need to be upgraded, the compatible files of the same version will be screened and tested repeatedly, resulting in low upgrade efficiency. Summary of the invention

[0004] A first aspect of an embodiment of the present application provides a product component upgrade method, comprising:

[0005] Detecting multiple target product components to be upgraded that are associated with the same target compatible file among the product components to be upgraded contained in the multiple product code repositories, and determining the target version product component to which the target product components to be upgraded need to be upgraded;

[0006] Acquire the target version product component from a first preset server, and acquire the target compatible file from a second preset server;

[0007] Running the target version product component based on the target compatible file to detect the running status of the target version product component;

[0008] If the target version product component operates normally, each of the target product components to be upgraded is upgraded according to the target compatible file and the target version product component.

[0009] In a specific implementation, the detecting of multiple target product components to be upgraded that are associated with the same target compatible file and determining the target version product component to which the target product component to be upgraded needs to be upgraded includes:

[0010] Determine a first version product component to which each of the to-be-upgraded product components needs to be upgraded;

[0011] Determine, according to each of the to-be-upgraded product components and the first version product component of the to-be-upgraded product component, a compatible file associated with the to-be-upgraded product component;

[0012] According to the compatible files associated with each of the product components to be upgraded, using the same compatible files as target compatible files;

[0013] A plurality of to-be-upgraded product components associated with the target compatible file are determined as target to-be-upgraded product components, and the first version product component corresponding to the target to-be-upgraded product component is determined as the target version product component.

[0014] In a specific implementation, the method further includes:

[0015] If the other product components to be upgraded contained in the product code repository are not associated with compatible files, the second version product components to which the other product components to be upgraded need to be upgraded are obtained from the first preset server, and the other product components to be upgraded are upgraded according to the second version product components; wherein the other product components to be upgraded are product components to be upgraded other than the target product components to be upgraded.

[0016] In a specific implementation, before detecting multiple target product components to be upgraded that are associated with the same target compatible file and determining the target version product component to which the target product component to be upgraded needs to be upgraded, the method further includes:

[0017] registering a target compatible file determined by a first user;

[0018] The target compatible file is uploaded to the second preset server.

[0019] In a specific implementation, after detecting the running status of the target version product component, the method further includes:

[0020] If the operation status of the target version product component is abnormal, displaying the target compatible file and the operation status of the target version product component to the second user, so that the second user can modify the target compatible file to obtain a standard compatible file;

[0021] Each of the target product components to be upgraded is upgraded based on the standard-compliant file and the target version product component.

[0022] In a specific implementation, before detecting multiple target product components to be upgraded that are associated with the same target compatible file and determining the target version product component to which the target product component to be upgraded needs to be upgraded, the method further includes:

[0023] Determine, according to a preset upgrade condition, a product component to be upgraded among the product components included in the multiple product code repositories.

[0024] A second aspect of an embodiment of the present application provides a product component upgrading device, including:

[0025] A detection unit, configured to detect, among the product components to be upgraded contained in the multiple product code repositories, multiple target product components to be upgraded that are associated with the same target compatible file, and determine a target version product component to which the target product components to be upgraded need to be upgraded;

[0026] An acquisition unit, configured to acquire the target version product component from a first preset server, and acquire the target compatible file from a second preset server;

[0027] The detection unit is further used to run the target version product component based on the target compatible file to detect the running status of the target version product component;

[0028] An upgrading unit is used for upgrading each of the target product components to be upgraded according to the target compatible file and the target product component if the operation of the target version product component is normal.

[0029] In a specific implementation, the detection unit is specifically used to determine the first version product component to which each of the to-be-upgraded product components needs to be upgraded;

[0030] Determine, according to each of the to-be-upgraded product components and the first version product component of the to-be-upgraded product component, a compatible file associated with the to-be-upgraded product component;

[0031] According to the compatible files associated with each of the product components to be upgraded, using the same compatible files as target compatible files;

[0032] A plurality of to-be-upgraded product components associated with the target compatible file are determined as target to-be-upgraded product components, and the first version product component corresponding to the target to-be-upgraded product component is determined as the target version product component.

[0033] In a specific implementation, the acquisition unit is also used to obtain the second version product components to which the other product components to be upgraded need to be upgraded from the first preset server if the other product components to be upgraded contained in the product code repository are not associated with compatible files, and upgrade the other product components to be upgraded according to the second version product components; wherein the other product components to be upgraded are product components to be upgraded other than the target product components to be upgraded.

[0034] In a specific implementation, the device further includes: a registration unit, configured to register a target compatible file determined by the first user;

[0035] An uploading unit is used to upload the target compatible file to the second preset server.

[0036] In a specific implementation, the device further includes: a display unit, configured to display the target compatible file and the operation status of the target version product component to a second user if the operation status of the target version product component is abnormal, so that the second user can modify the target compatible file to obtain a standard compatible file;

[0037] The upgrading unit is further configured to upgrade each of the target product components to be upgraded based on the standard compatible file and the target version product components.

[0038] In a specific implementation, the device further includes: a determination unit, configured to determine, according to a preset upgrade condition, a product component to be upgraded among the product components included in the multiple product code repositories.

[0039] A third aspect of an embodiment of the present application provides a computer device, including:

[0040] CPU, memory and input / output interface;

[0041] The memory is a short-term storage memory or a persistent storage memory;

[0042] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method described in the first aspect.

[0043] A fourth aspect of the embodiments of the present application provides a computer program product comprising instructions, and when the computer program product is run on a computer, the computer is caused to execute the method described in the first aspect.

[0044] A fifth aspect of an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores instructions, and when the instructions are executed on a computer, the computer executes the method described in the first aspect.

[0045] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages: when multiple target product components to be upgraded that are associated with the same target compatible file are detected, the target version product component is obtained from the first preset server, and the target compatible file is obtained from the second preset server, and each target product component to be upgraded is upgraded after detection. As long as the product components of different products are associated with the same target compatible file, only screening and detection are required once, and multiple target product components to be upgraded that are associated with the same target compatible file can be upgraded, thereby improving the upgrade efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] Figure 1 A schematic diagram of a process flow of a product component upgrade method disclosed in an embodiment of the present application;

[0047] Figure 2A system architecture diagram of the front-end scaffolding disclosed in the embodiment of the present application;

[0048] Figure 3 A schematic diagram of the structure of the product component upgrading device disclosed in the embodiment of the present application;

[0049] Figure 4 This is another structural schematic diagram of the product component upgrading device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

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

[0051] Considering the cost and market of the product, an enterprise usually has multiple product lines for different markets. In order to meet the front-end security requirements, developers are required to upgrade components of different product lines or different forms of products in the same product line. The upgrade process requires manual operation by developers, and different product lines cannot be upgraded uniformly. In addition, after the product component is upgraded, due to the difference between the version of the original product component and the version of the upgraded product component, the upgraded product component is incompatible with other product components of the corresponding product, which will cause the upgraded product component to be unable to be used normally. Now, generally, the required compatible files are manually searched in the open source compatible file library, and the compatible files usually selected also need a lot of adaptive modifications, and then the processed compatible files are added to the code repository of the product to ensure the normal operation of the upgraded product components.

[0052] In actual applications, product components of different products may require compatible files of the same version. If these components of different products need to be upgraded, the compatible files of the same version will be screened and tested repeatedly, which reduces the upgrade efficiency. At the same time, manual version screening is inefficient and has a high error rate.

[0053] Based on the above problems, the present application provides a product component upgrade method and related equipment to improve the efficiency of product component upgrades.

[0054] See also Figure 1 The first aspect of the embodiment of the present application provides a product component upgrade method, comprising:

[0055] 101. Among the product components to be upgraded contained in multiple product code repositories, detect multiple target product components to be upgraded that are associated with the same target compatible file, and determine the target version product component to which the target product component to be upgraded needs to be upgraded.

[0056] When it is necessary to upgrade the product components to be upgraded contained in the product code repositories of multiple products, first detect each product component to be upgraded that is associated with the same target compatible file and confirm it as the target product component to be upgraded. At the same time, it is also necessary to determine the target version to which each product component to be upgraded needs to be upgraded, and the target version product component.

[0057] In some specific embodiments, step 101 is implemented in the following manner: determine the first version product component to which each product component to be upgraded needs to be upgraded; determine the compatible files associated with the product component to be upgraded based on each product component to be upgraded and the first version product component of the product component to be upgraded; based on the compatible files associated with each product component to be upgraded, use the same compatible files as target compatible files; determine multiple product components to be upgraded associated with the target compatible files as target product components to be upgraded, and determine the first version product components corresponding to the target product components to be upgraded as the target version product components.

[0058] Each first-version product component and the corresponding to-be-upgraded product component are the same product components of different versions, such as third-party libraries of different versions.

[0059] It is known that in actual applications, there may be multiple groups of target product components to be upgraded, each group associated with different compatible files. This embodiment only describes one group of target product components to be upgraded and one target compatible file associated with it, and each other group of target product components to be upgraded can be upgraded by the method provided in this embodiment.

[0060] 102. Obtain a target version product component from a first preset server, and obtain a target compatible file from a second preset server.

[0061] After completing the detection of multiple target product components to be upgraded that are associated with the same target compatible files in step 101, the target version product components to which the multiple target product components to be upgraded need to be upgraded are obtained from the first preset server, and the target compatible files required for the normal operation of the target version product components after the upgrade are obtained from the second preset server.

[0062] The first preset server and the second preset server may be the same server or different servers. The first preset server may be an official server or a mirror server of a node package manager (NPM) for downloading target version product components, and the second preset server may be an NPM official server or other server for downloading target compatible files. In this embodiment, the first preset server and the second preset server are not specifically limited.

[0063] 103. Run the target version product component based on the target compatible file to detect the operation status of the target version product component.

[0064] After obtaining the target version product component and the target compatible file in step 102, the target version product component is run based on the target compatible file to detect the running status of the target version product component.

[0065] Specifically, if the operation status is normal, step 104 is executed; if the operation status is abnormal, the operation status of the target compatible file and the target version product component is displayed to the second user, so that the second user can modify the target compatible file according to the displayed operation status to obtain the standard compatible file. Then, each target product component to be upgraded is upgraded based on the modified standard compatible file and the target version product component.

[0066] The second user may be the user who initiated the upgrade detection in step 101 or the developer of the product corresponding to the target product component to be upgraded. Specifically, it may be a preset legitimate user or any user with upgrade authority, which is not limited here.

[0067] 104. If the target version product component operates normally, each target product component to be upgraded is upgraded according to the target compatible file and the target version product component.

[0068] If the target version product component is running normally according to the detection in step 103, each target product component to be upgraded can be upgraded according to the target compatible file and the target version product component.

[0069] Specifically, the target version product component and the target compatible file can be used to replace the target product component to be upgraded in the corresponding code repository of each target product component to be upgraded, so as to upgrade the target product component to be upgraded and ensure normal operation after the upgrade.

[0070] In the embodiment of the present application, when multiple target product components to be upgraded that are associated with the same target compatible file are detected, the target version product component is obtained from the first preset server, and the target compatible file is obtained from the second preset server, and each target product component to be upgraded is upgraded after detection. As long as the product components of different products are associated with the same target compatible file, only screening and detection are required once, and multiple target product components to be upgraded that are associated with the same target compatible file can be upgraded, thereby improving the upgrade efficiency.

[0071] In some specific embodiments, on the basis of the aforementioned steps 101 to 104, before the aforementioned step 101, the product components to be upgraded among the product components contained in the multiple product code repositories may be determined according to the preset upgrade conditions. Specifically, the preset conditions may be different conditions for determining whether each product component needs to be upgraded, such as whether the current version of each product component meets the minimum version requirement of the corresponding product component preset by the developer for this detection, whether the user initiating the upgrade detection is legal, and whether the second preset server has completed the preset, etc. It can be known that there will be other judgment conditions in actual applications, which are not limited in this embodiment.

[0072] In this embodiment, a specific method for determining components to be upgraded according to preset conditions is provided, thereby improving the feasibility of the solution.

[0073] In some other embodiments, based on the above embodiments, before the above step 101, the target compatible file determined by the first user may be registered; and the target compatible file may be uploaded to the second preset server.

[0074] In actual applications, the first user needs to complete the registration and upload of the target compatible file before performing the upgrade detection, and the registered compatible file can be used for the detection and comparison of compatible files in step 101. The compatible file is screened and modified by the first user according to the current version of the product component and the target version of the product component. A product component upgraded from version A to version B will only correspond to a unique compatible file.

[0075] In this embodiment, the unique corresponding target compatible file after registration can be determined based on the current version and target version of the product component, without the need for developers to screen and modify from a large number of compatible file libraries, thereby improving the upgrade efficiency of the product component and reducing the error rate of the upgraded product.

[0076] In actual application, after step 103, the operation status obtained by running the target version product component based on the target compatible file can also be sent to the first user in the form of an upgrade log, so that the first user can check the upgrade status.

[0077] In some embodiments, based on the foregoing embodiments, if other product components to be upgraded contained in the product code repository are not associated with compatible files, the second version product components to which the other product components to be upgraded need to be upgraded are obtained from the first preset server, and the other product components to be upgraded are upgraded according to the second version product components; wherein the other product components to be upgraded are product components to be upgraded other than the target product components to be upgraded.

[0078] It can be known that all version differences in the above-mentioned embodiment can be determined by the version identification of the product component. Specifically, the version identification can be a version number or a version name, which is not limited in this embodiment.

[0079] Furthermore, the embodiment of the present application provides a product component upgrade method, which is implemented through a front-end scaffold. First, the security upgrade department or developers of other product lines use the scaffold to publish and register compatible files that meet different versions, and then each product line can be upgraded to a version that meets security requirements through the scaffold, and includes compatible files. Automatic upgrades replace manual upgrades, and efficiently complete the upgrade of product component versions of multiple product lines.

[0080] The front-end scaffolding architecture provided in the embodiment of the present application is shown in FIG. Figure 2 As shown in the figure, it is mainly composed of four systems. They are the release system, which is responsible for releasing versions and being compatible with lower-version API files; the git operation system, which is responsible for completing some basic git operations; the cache system, which improves the efficiency of repeated upgrade verification through local file cache and variable cache; and the OPEN API, which allows business lines to set the first preset server and the second preset server, file directory and version configuration by themselves.

[0081] See also Figure 3 , the embodiment of the present application provides a product component upgrading device, comprising:

[0082] The detection unit 301 is used to detect multiple target product components to be upgraded that are associated with the same target compatible file among the product components to be upgraded contained in the multiple product code repositories, and determine the target version product component to which the target product component to be upgraded needs to be upgraded;

[0083] An acquisition unit 302 is used to acquire a target version product component from a first preset server and acquire a target compatible file from a second preset server;

[0084] The detection unit 301 is further used to run the target version product component based on the target compatible file to detect the running status of the target version product component;

[0085] The upgrading unit 303 is used to upgrade each target product component to be upgraded according to the target compatible file and the target version product component if the operation of the target version product component is normal.

[0086] In a specific implementation, the detection unit 301 is specifically configured to determine the first version product component to which each to-be-upgraded product component needs to be upgraded;

[0087] Determine, according to each product component to be upgraded and the first version product component of the product component to be upgraded, a compatible file associated with the product component to be upgraded;

[0088] According to the compatible files associated with each product component to be upgraded, the same compatible files are used as target compatible files;

[0089] A plurality of to-be-upgraded product components associated with the target compatible file are determined as target to-be-upgraded product components, and a first version product component corresponding to the target to-be-upgraded product component is determined as a target version product component.

[0090] In a specific implementation, the acquisition unit 302 is also used to obtain the second version product components to which the other product components to be upgraded need to be upgraded from the first preset server if the other product components to be upgraded contained in the product code repository are not associated with compatible files, and upgrade the other product components to be upgraded according to the second version product components; wherein the other product components to be upgraded are product components to be upgraded other than the target product components to be upgraded.

[0091] In a specific implementation, the device further includes: a registration unit, configured to register a target compatible file determined by the first user;

[0092] The uploading unit is used to upload the target compatible file to the second preset server.

[0093] In a specific implementation, the device further includes: a display unit, configured to display the target compatible file and the operation status of the target version product component to the second user if the operation status of the target version product component is abnormal, so that the second user can modify the target compatible file to obtain the standard compatible file;

[0094] The upgrading unit 303 is further used to upgrade each target product component to be upgraded based on the standard compatible file and the target version product component.

[0095] In a specific implementation, the device further includes: a determination unit, configured to determine, according to a preset upgrade condition, a product component to be upgraded among product components included in a plurality of product code repositories.

[0096] In this embodiment, after the detection unit 301 detects multiple target product components to be upgraded that are associated with the same target compatible file, the acquisition unit 302 acquires the target version product component from the first preset server and acquires the target compatible file from the second preset server, and the upgrade unit 303 upgrades each target product component to be upgraded after the detection unit 301 completes the detection. As long as the product components of different products are associated with the same target compatible file, only one screening and detection is required to upgrade multiple target product components to be upgraded that are associated with the same target compatible file, thereby improving the upgrade efficiency.

[0097] Figure 4It is a structural diagram of a product component upgrade device provided in an embodiment of the present application. The product component upgrade device 400 may include one or more central processing units (CPU) 401 and a memory 405. The memory 405 stores one or more application programs or data.

[0098] The memory 405 may be a volatile storage or a persistent storage. The program stored in the memory 405 may include one or more modules, each of which may include a series of instruction operations in the product component upgrade device. Furthermore, the central processor 401 may be configured to communicate with the memory 405 and execute a series of instruction operations in the memory 405 on the product component upgrade device 400.

[0099] The product component upgrading device 400 may also include one or more power supplies 402, one or more wired or wireless network interfaces 403, one or more input and output interfaces 404, and / or one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0100] The CPU 401 can execute the aforementioned Figures 1 to 3 The operations performed by the product component upgrading device in the illustrated embodiment will not be described in detail here.

[0101] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

[0104] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0105] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. A product component upgrade method, characterized in that: include: Detecting multiple target product components to be upgraded that are associated with the same target compatible file among the product components to be upgraded contained in the multiple product code repositories, and determining the target version product component to which the target product components to be upgraded need to be upgraded; Acquire the target version product component from a first preset server, and acquire the target compatible file from a second preset server; Running the target version product component based on the target compatible file to detect the running status of the target version product component; If the target version product component operates normally, each of the target product components to be upgraded is upgraded according to the target compatible file and the target version product component.

2. The method according to claim 1, characterized in that The detecting of multiple target product components to be upgraded that are associated with the same target compatible file and determining the target version product component to which the target product component to be upgraded needs to be upgraded includes: Determine a first version product component to which each of the to-be-upgraded product components needs to be upgraded; Determine, according to each of the to-be-upgraded product components and the first version product component of the to-be-upgraded product component, a compatible file associated with the to-be-upgraded product component; According to the compatible files associated with each of the product components to be upgraded, using the same compatible files as target compatible files; A plurality of to-be-upgraded product components associated with the target compatible file are determined as target to-be-upgraded product components, and the first version product component corresponding to the target to-be-upgraded product component is determined as the target version product component.

3. The method according to claim 1, characterized in that The method further comprises: If the other product components to be upgraded contained in the product code repository are not associated with compatible files, the second version product components to which the other product components to be upgraded need to be upgraded are obtained from the first preset server, and the other product components to be upgraded are upgraded according to the second version product components; wherein the other product components to be upgraded are product components to be upgraded other than the target product components to be upgraded.

4. The method according to claim 1, characterized in that: Before detecting multiple target product components to be upgraded that are associated with the same target compatible file and determining the target version product component to which the target product component to be upgraded needs to be upgraded, the method further includes: registering a target compatible file determined by a first user; The target compatible file is uploaded to the second preset server.

5. The method according to claim 1, characterized in that After detecting the running status of the target version product component, the method further includes: If the operation status of the target version product component is abnormal, displaying the target compatible file and the operation status of the target version product component to the second user, so that the second user can modify the target compatible file to obtain a standard compatible file; Each of the target product components to be upgraded is upgraded based on the standard-compliant file and the target version product component.

6. The method according to claim 1, characterized in that Before detecting multiple target product components to be upgraded that are associated with the same target compatible file and determining the target version product component to which the target product component to be upgraded needs to be upgraded, the method further includes: Determine, according to a preset upgrade condition, a product component to be upgraded among the product components included in the multiple product code repositories.

7. A product component upgrading device, characterized in that: include: A detection unit, configured to detect, among the product components to be upgraded contained in the multiple product code repositories, multiple target product components to be upgraded that are associated with the same target compatible file, and determine a target version product component to which the target product components to be upgraded need to be upgraded; An acquisition unit, configured to acquire the target version product component from a first preset server, and acquire the target compatible file from a second preset server; The detection unit is further used to run the target version product component based on the target compatible file to detect the running status of the target version product component; An upgrading unit is used for upgrading each of the target product components to be upgraded according to the target compatible file and the target product component if the operation of the target version product component is normal.

8. The product component upgrading device according to claim 7, characterized in that: include: The detection unit is specifically used to determine the first version product component to which each of the to-be-upgraded product components needs to be upgraded; Determine, according to each of the to-be-upgraded product components and the first version product component of the to-be-upgraded product component, a compatible file associated with the to-be-upgraded product component; According to the compatible files associated with each of the product components to be upgraded, using the same compatible files as target compatible files; A plurality of to-be-upgraded product components associated with the target compatible file are determined as target to-be-upgraded product components, and the first version product component corresponding to the target to-be-upgraded product component is determined as the target version product component.

9. A computer device, characterized in that: include: CPU, memory and input / output interface; The memory is a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 6.

10. A computer storage medium, characterized in that: The computer storage medium stores instructions, and when the instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 6.

Images