CN114637526A - Product component upgrading method and related equipment - Google Patents
Product component upgrading method and related equipment Download PDFInfo
- Publication number
- CN114637526A CN114637526A CN202210254775.6A CN202210254775A CN114637526A CN 114637526 A CN114637526 A CN 114637526A CN 202210254775 A CN202210254775 A CN 202210254775A CN 114637526 A CN114637526 A CN 114637526A
- Authority
- CN
- China
- Prior art keywords
- target
- product
- upgraded
- compatible file
- version
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application discloses a product assembly upgrading method and related equipment, which are used for improving the upgrading efficiency of a product assembly. The method in the embodiment of the application comprises the following steps: detecting a plurality of target product assemblies to be upgraded related to the same target compatible file in the product assemblies to be upgraded contained in a plurality of product code warehouses, and determining the target version product assembly to which the target product assemblies to be upgraded need to be upgraded; acquiring the target version product component from a first preset server, and acquiring 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 condition of the target version product component; and if the operation condition of the target version product assembly is normal, upgrading each target product assembly to be upgraded according to the target compatible file and the target version product assembly.
Description
Technical Field
The embodiment of the application relates to the field of software, in particular to a product component upgrading method and related equipment.
Background
In order to meet the front-end security requirements, developers are required to upgrade different product lines or components of products of the same product line in different forms. If the upgraded component is incompatible with other components of the product, the compatible file required by the upgrade needs to be manually screened and detected, and the compatible file is added to a code warehouse of the product, so that the upgraded product component can normally run.
In practical application, product components of different products may need compatible files of the same version, and if the components of the different products need to be upgraded, the compatible files of the same version are repeatedly screened and detected, so that the upgrading efficiency is low.
Disclosure of Invention
A first aspect of an embodiment of the present application provides a method for upgrading a product component, including:
detecting a plurality of target product components to be upgraded related to the same target compatible file in the product components to be upgraded contained in a plurality of product code warehouses, and determining a target version product component to which the target product components to be upgraded need to be upgraded;
acquiring the target version product component from a first preset server, and acquiring 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 condition of the target version product component;
and if the operation condition of the target version product assembly is normal, upgrading each target product assembly to be upgraded according to the target compatible file and the target version product assembly.
In a specific implementation manner, the detecting a plurality of target product assemblies to be upgraded related to the same target compatible file, and determining a target version product assembly to which the target product assembly to be upgraded needs to be upgraded includes:
determining a first version product assembly to which each product assembly to be upgraded needs to be upgraded;
determining a compatible file associated with the product component to be upgraded according to each product component to be upgraded and a first version product component of the product component to be upgraded;
according to the compatible file associated with each product component to be upgraded, taking the same compatible file as a target compatible file;
determining a plurality of product components to be upgraded related to the target compatible file as target product components to be upgraded, and determining the first version product components corresponding to the target product components to be upgraded as the target version product components.
In a specific implementation, the method further includes:
if the other product components to be upgraded contained in the product code warehouse are not associated with compatible files, acquiring a second version product component to which the other product components to be upgraded need to be upgraded from the first preset server, and upgrading the other product components to be upgraded according to the second version product component; and the other product components to be upgraded are product components to be upgraded except the target product component to be upgraded.
In a specific implementation manner, before the detecting and associating multiple target product assemblies to be upgraded of the same target compatible file, and determining a target version product assembly to which the target product assembly to be upgraded needs to be upgraded, the method further includes:
registering a target compatible file determined by a first user;
and uploading the target compatible file to the second preset server.
In a specific implementation manner, after the detecting the operation condition of the target version product component, the method further includes:
if the running condition of the target version product component is abnormal, showing the running condition of the target compatible file and the target version product component to a second user so that the second user modifies the target compatible file to obtain a standard compatible file;
and upgrading each target product component to be upgraded based on the standard compatible file and the target version product component.
In a specific implementation manner, before detecting a plurality of target product components to be upgraded associated with the same target compatible file and determining a target version product component to which the target product components to be upgraded need to be upgraded, the method further includes:
and determining the product components to be upgraded in the product components contained in the plurality of product code warehouses according to preset upgrading conditions.
A second aspect of the embodiments of the present application provides a product component upgrading apparatus, including:
the system comprises a detection unit, a storage unit and a processing unit, wherein the detection unit is used for detecting a plurality of target product components to be upgraded related to the same target compatible file in the product components to be upgraded contained in a plurality of product code warehouses, and determining the target version product components to which the target product components to be upgraded need to be upgraded;
the acquisition unit is used for acquiring the target version product component from a first preset server and acquiring the target compatible file from a second preset server;
the detection unit is further configured to run the target version product component based on the target compatible file to detect a running condition of the target version product component;
and the upgrading unit is used for upgrading each target product component to be upgraded according to the target compatible file and the target version product component if the running condition of the target version product component is normal.
In a specific implementation manner, the detection unit is specifically configured to determine a first version product component to which each product component to be upgraded needs to be upgraded;
determining a compatible file associated with the product component to be upgraded according to each product component to be upgraded and a first version product component of the product component to be upgraded;
according to the compatible file associated with each product component to be upgraded, taking the same compatible file as a target compatible file;
determining a plurality of product assemblies to be upgraded related to the target compatible file as target product assemblies to be upgraded, and determining the first version product assembly corresponding to the target product assemblies to be upgraded as the target version product assembly.
In a specific implementation manner, the obtaining unit is further configured to obtain, from the first preset server, a second version product component to which the other product component to be upgraded needs to be upgraded if the other product component to be upgraded included in the product code repository is not associated with a compatible file, and upgrade the other product component to be upgraded according to the second version product component; and the other product components to be upgraded are product components to be upgraded except the target product component to be upgraded.
In a specific implementation manner, the apparatus further includes: the registration unit is used for registering the target compatible file determined by the first user;
and the uploading unit is used for uploading the target compatible file to the second preset server.
In a specific implementation manner, the apparatus further includes: the display unit is used for displaying the target compatible file and the running condition of the target version product component to a second user if the running condition of the target version product component is abnormal, so that the second user modifies the target compatible file to obtain a standard compatible file;
the upgrading unit is further used for upgrading each target product component to be upgraded based on the standard compatible file and the target version product component.
In a specific implementation manner, the apparatus further includes: and the determining unit is used for determining the product assemblies to be upgraded in the product assemblies contained in the plurality of product code warehouses according to preset upgrading conditions.
A third aspect of embodiments of the present application provides a computer device, including:
the system comprises a central processing unit, a memory and an input/output interface;
the memory is a transient storage memory or a persistent storage memory;
the central processor is configured to communicate with the memory and execute the operations of the instructions in the memory to perform the method of the first aspect.
A fourth aspect of embodiments of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method according to the first aspect.
A fifth aspect of embodiments of the present application provides a computer storage medium having instructions stored therein, which when executed on a computer, cause the computer to perform the method according to the first aspect.
According to the technical scheme, the embodiment of the application has the following advantages: when a plurality of target product components to be upgraded which are associated with the same target compatible file are detected, the target version product components are obtained from a first preset server, the target compatible file is obtained from a second preset server, and each target product component to be upgraded is upgraded after detection. Product components of different products can be upgraded on a plurality of target product components to be upgraded related to the same target compatible file only by screening and detecting once as long as the same target compatible file is related to the product components, so that the upgrading efficiency is improved.
Drawings
Fig. 1 is a schematic flowchart of a method for upgrading a product component according to an embodiment of the present disclosure;
FIG. 2 is a system architecture diagram of a front end scaffold as disclosed in an embodiment of the present application;
fig. 3 is a schematic structural diagram of a product component upgrading apparatus disclosed in an embodiment of the present application;
fig. 4 is another schematic structural diagram of the product component upgrading apparatus disclosed in the embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Considering the cost and market of the product, an enterprise typically has multiple product lines oriented in different markets. In order to meet the front-end security requirements, developers are required to upgrade different product lines or components of products of the same product line in different forms. The upgrading process needs manual operation of developers, and different product lines cannot be upgraded uniformly. In addition, after the product assembly is upgraded, because the version of the original product assembly is different from the version of the upgraded product assembly, the upgraded product assembly is incompatible with other product assemblies of the corresponding product, and the upgraded product assembly cannot be normally used. At present, generally, a required compatible file is manually searched in an open source compatible file library, a large amount of adaptive modification needs to be performed on the usually selected compatible file, and then the processed compatible file is added to a code warehouse of the product, so as to ensure that the upgraded product component operates normally.
In practical application, product components of different products may need compatible files of the same version, and if the components of these different products need to be upgraded, the compatible files of the same version are repeatedly screened and detected, so that the upgrading efficiency is low. Meanwhile, the manual version screening is low in efficiency and high in error rate.
Based on the above problems, the present application provides a product component upgrading method and related devices, which are used for improving the product component upgrading efficiency.
Referring to fig. 1, a first aspect of the present embodiment provides a method for upgrading a product component, including:
101. in the product assemblies to be upgraded contained in the product code warehouses, a plurality of target product assemblies to be upgraded related to the same target compatible file are detected, and the target version product assemblies to which the target product assemblies to be upgraded need to be upgraded are determined.
When the product assemblies to be upgraded contained in the product code warehouses of a plurality of products need to be upgraded, each product assembly to be upgraded related to the same target compatible file is detected and confirmed as a target product assembly to be upgraded. Meanwhile, the target version to which each product component to be upgraded needs to be upgraded and the target version product component need to be determined.
In some embodiments, step 101 is implemented by: determining a first version product assembly to which each product assembly to be upgraded needs to be upgraded; determining a compatible file associated with each product component to be upgraded according to each product component to be upgraded and the first version product component of the product component to be upgraded; according to the compatible file associated with each product component to be upgraded, taking the same compatible file as a target compatible file; determining a plurality of product components to be upgraded related to the target compatible file as target product components to be upgraded, and determining a first version product component corresponding to the target product components to be upgraded as a target version product component.
Each first version product assembly and the corresponding product assembly to be upgraded are the same product assembly with different versions, such as a third party library with different versions.
It will be appreciated that in practical applications, there may be multiple sets of target product components to be upgraded, each set being associated with a different compatible file. In this embodiment, only one set of target product components to be upgraded and one target compatible file associated therewith are described, and each set of other target product components to be upgraded can be upgraded by the method provided in this embodiment.
102. And acquiring the target version product component from the first preset server, and acquiring the target compatible file from the second preset server.
After the detection of a plurality of target product components to be upgraded associated with the same target compatible file is completed in step 101, target version product components to which the plurality of target product components to be upgraded need to be upgraded are obtained from a first preset server, and target compatible files needed for normally operating the target version product components after upgrading are obtained from a second preset server.
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 image server of a Node Package Manager (NPM) that downloads a target version product component, and the second preset server may be an NPM official server or another server that downloads a target compatible file.
103. And running the target version product component based on the target compatible file to detect the running condition of the target version product component.
After the target version product component and the target compatible file are obtained in step 102, the target version product component is operated based on the target compatible file to detect the operation condition of the target version product component.
Specifically, if the operation status is normal, step 104 is executed; and if the running condition is abnormal, displaying the running condition of the target compatible file and the target version product component to the second user, so that the second user modifies the target compatible file according to the displayed running condition to obtain the standard compatible file. And then, upgrading each target product component to be upgraded based on the modified standard compatible file and the target version product component.
The second user may be a user who initiates the upgrade detection in step 101 or a developer of a product corresponding to the target product component to be upgraded, and specifically may be a preset legal user or any user having an upgrade right, which is not limited herein.
104. And if the operation condition of the target version product assembly is normal, upgrading each target product assembly to be upgraded according to the target compatible file and the target version product assembly.
If the operation condition of the target version product component is normal according to the detection of the step 103, each target product component to be upgraded can be upgraded according to the target compatible file and the target version product component.
Specifically, the target product assembly to be upgraded in the corresponding code warehouse of each target product assembly to be upgraded can be replaced by the target version product assembly and the target compatible file, so that the target product assembly to be upgraded is upgraded, and the normal operation of the upgraded product assembly is ensured.
In the embodiment of the application, when a plurality of target product components to be upgraded which are associated with the same target compatible file are detected, a target version product component is obtained from a first preset server, a target compatible file is obtained from a second preset server, and each target product component to be upgraded is upgraded after detection. Product components of different products can be upgraded on a plurality of target product components to be upgraded related to the same target compatible file only by screening and detecting once as long as the same target compatible file is related to the product components, so that the upgrading efficiency is improved.
In some embodiments, on the basis of the foregoing steps 101 to 104, before the foregoing step 101, a product component to be upgraded among product components included in the plurality of product code warehouses may be determined according to a preset upgrade condition. 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 at least one of a minimum version requirement of a developer on a corresponding product component preset by the detection of this time, whether an upgrade detection initiating user is legal, whether the second preset server completes presetting, and the like. It can be known that there are other determination conditions in practical application, and this embodiment is not limited.
In the embodiment, a specific method for determining the component to be upgraded according to the preset condition is provided, so that the realizability of the scheme is improved.
In other embodiments, on the basis of the foregoing embodiments, before the foregoing step 101, a target compatible file determined by the first user may also be registered; and uploading the target compatible file to a second preset server.
In practical application, the first user is required to complete registration and uploading of the target compatible file before performing upgrade detection, and the registered compatible file can be used for detection and comparison of the compatible file in step 101. The compatible file is screened and modified by the first user according to the current version of the product assembly and the target version of the product assembly, and only the only compatible file is corresponding to the product assembly which is upgraded from the version A to the version B.
In the embodiment, the only corresponding target compatible file after registration can be determined according to the current version and the target version of the product assembly, developers do not need to screen and modify from a large number of compatible file libraries, the upgrading efficiency of the product assembly is improved, and the error reporting rate of the upgraded product is reduced.
In practical applications, after step 103, the running condition obtained by running the target version product component based on the target compatible file may also be sent to the first user in the form of an upgrade log, so that the first user can conveniently view the upgrade condition.
In some embodiments, on the basis of the foregoing embodiment, if other product components to be upgraded included in the product code repository are not associated with compatible files, a second version product component to which the other product components to be upgraded need to be upgraded is acquired from the first preset server, and the other product components to be upgraded are upgraded according to the second version product component; and the other product components to be upgraded are product components to be upgraded except the target product components to be upgraded.
It will be appreciated that all version distinctions of the foregoing embodiments may be determined by the version identification of the product component. Specifically, the version identifier may be a version number or a version name, and this embodiment is not limited.
Further, the embodiment of the application provides a product component upgrading method, which is realized through a front-end scaffold. Firstly, developers of a safety upgrading department or other product lines release and register compatible files meeting different versions through a scaffold, then each product line can be upgraded to the version meeting the safety requirement through the scaffold and contains the compatible files, manual upgrading is replaced by automatic upgrading, and product component version upgrading of a plurality of product lines is completed efficiently.
The front end scaffold structure diagram provided by the embodiment of the application is shown in fig. 2 and mainly comprises four systems. The system is a release system and is responsible for releasing the version and compatible with the low version API file; a git operation system responsible for completing some git basic operations; the cache system promotes the high efficiency of repeated upgrading verification through local file cache and variable cache; and the OPEN API enables the service line to set a first preset server and a second preset server, a file directory and version configuration by itself.
Referring to fig. 3, an embodiment of the present application provides a product component upgrading apparatus, including:
the detection unit 301 is configured to detect a plurality of target product assemblies to be upgraded, which are associated with the same target compatible file, in the product assemblies to be upgraded included in the plurality of product code warehouses, and determine a target version product assembly to which the target product assembly to be upgraded needs to be upgraded;
an obtaining unit 302, configured to obtain a target version product component from a first preset server, and obtain a target compatible file from a second preset server;
the detection unit 301 is further configured to run the target version product component based on the target compatible file to detect a running condition of the target version product component;
and the upgrading unit 303 is configured to upgrade each target product component to be upgraded according to the target compatible file and the target version product component if the operation condition of the target version product component is normal.
In a specific implementation manner, the detection unit 301 is specifically configured to determine a first version product component to which each product component to be upgraded needs to be upgraded;
determining a compatible file associated with each product component to be upgraded according to each product component to be upgraded and the first version product component of the product component to be upgraded;
according to the compatible file associated with each product component to be upgraded, taking the same compatible file as a target compatible file;
determining a plurality of product components to be upgraded related to the target compatible file as target product components to be upgraded, and determining a first version product component corresponding to the target product components to be upgraded as a target version product component.
In a specific implementation manner, the obtaining unit 302 is further configured to obtain, from the first preset server, a second version product component to which other product components to be upgraded need to be upgraded if the other product components to be upgraded included 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 component; and the other product components to be upgraded are product components to be upgraded except the target product components to be upgraded.
In a specific implementation, the apparatus further includes: the registration unit is used for registering the target compatible file determined by the first user;
and the uploading unit is used for uploading the target compatible file to a second preset server.
In a specific implementation, the apparatus further includes: the display unit is used for displaying the target compatible file and the running condition of the target version product component to a second user if the running condition 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;
the upgrading unit 303 is further configured to upgrade each target product component to be upgraded based on the standard compatible file and the target version product component.
In a specific implementation, the apparatus further comprises: and the determining unit is used for determining the product components to be upgraded in the product components contained in the plurality of product code warehouses according to the preset upgrading conditions.
In this embodiment, after the detection unit 301 detects a plurality of target product components to be upgraded that are associated with the same target compatible file, the obtaining unit 302 obtains a target version product component from a first preset server, obtains a target compatible file from a second preset server, and upgrades each target product component to be upgraded after the detection unit 301 completes the detection by the upgrading unit 303. Product assemblies of different products can be upgraded by only screening and detecting once as long as being associated with the same target compatible file, and therefore the upgrading efficiency is improved.
Fig. 4 is a schematic structural diagram of a product component upgrading apparatus according to an embodiment of the present disclosure, where the product component upgrading apparatus 400 may include one or more Central Processing Units (CPUs) 401 and a memory 405, where the memory 405 stores one or more application programs or data.
The product component upgrade device 400 may also include one or more power supplies 402, one or more wired or wireless network interfaces 403, one or more input-output interfaces 404, and/or one or more operating systems, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
The central processing unit 401 may perform the operations performed by the product component upgrading apparatus in the embodiments shown in fig. 1 to fig. 3, which are not described herein again.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, which are essential or part of the technical solutions contributing to the prior art, or all or part of the technical solutions, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like.
Claims (10)
1. A method for upgrading a product component, comprising:
detecting a plurality of target product components to be upgraded related to the same target compatible file in the product components to be upgraded contained in a plurality of product code warehouses, and determining a target version product component to which the target product components to be upgraded need to be upgraded;
acquiring the target version product component from a first preset server, and acquiring 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 condition of the target version product component;
and if the operation condition of the target version product assembly is normal, upgrading each target product assembly to be upgraded according to the target compatible file and the target version product assembly.
2. The method according to claim 1, wherein the detecting a plurality of target product components to be upgraded associated with the same target compatible file and determining a target version product component to which the target product components to be upgraded need to be upgraded comprises:
determining a first version product assembly to which each product assembly to be upgraded needs to be upgraded;
determining a compatible file associated with the product component to be upgraded according to each product component to be upgraded and a first version product component of the product component to be upgraded;
according to the compatible file associated with each product component to be upgraded, taking the same compatible file as a target compatible file;
determining a plurality of product components to be upgraded related to the target compatible file as target product components to be upgraded, and determining the first version product components corresponding to the target product components to be upgraded as the target version product components.
3. The method of claim 1, further comprising:
if the other product components to be upgraded contained in the product code warehouse are not associated with compatible files, acquiring a second version product component to which the other product components to be upgraded need to be upgraded from the first preset server, and upgrading the other product components to be upgraded according to the second version product component; and the other product components to be upgraded are product components to be upgraded except the target product component to be upgraded.
4. The method according to claim 1, wherein before the detecting a plurality of target product components to be upgraded associated with the same target compatible file and determining a target version product component to which the target product components to be upgraded need to be upgraded, the method further comprises:
registering a target compatible file determined by a first user;
and uploading the target compatible file to the second preset server.
5. The method of claim 1, wherein after detecting the operational condition of the target version product component, the method further comprises:
if the running condition of the target version product component is abnormal, displaying the target compatible file and the running condition of the target version product component to a second user so that the second user modifies the target compatible file to obtain a standard compatible file;
and upgrading each target product component to be upgraded based on the standard compatible file and the target version product component.
6. The method of claim 1, wherein before detecting a plurality of target product components to be upgraded associated with the same target compatible file and determining a target version product component to which the target product components to be upgraded need to be upgraded, the method further comprises:
and determining the product components to be upgraded in the product components contained in the plurality of product code warehouses according to preset upgrading conditions.
7. A product component upgrade device, comprising:
the system comprises a detection unit, a target version product assembly and a target version product assembly, wherein the detection unit is used for detecting a plurality of target product assemblies to be upgraded related to the same target compatible file in the product assemblies to be upgraded contained in a plurality of product code warehouses and determining the target product assembly to which the target product assembly to be upgraded needs to be upgraded;
the acquisition unit is used for acquiring the target version product component from a first preset server and acquiring the target compatible file from a second preset server;
the detection unit is further configured to run the target version product component based on the target compatible file to detect a running condition of the target version product component;
and the upgrading unit is used for upgrading each target product component to be upgraded according to the target compatible file and the target version product component if the running condition of the target version product component is normal.
8. The product component upgrade device according to claim 7, comprising: the detection unit is specifically used for determining a first version product assembly to which each product assembly to be upgraded needs to be upgraded;
determining a compatible file associated with each product component to be upgraded according to each product component to be upgraded and the first version product component of the product component to be upgraded;
according to the compatible file associated with each product component to be upgraded, taking the same compatible file as a target compatible file;
determining a plurality of product components to be upgraded related to the target compatible file as target product components to be upgraded, and determining the first version product components corresponding to the target product components to be upgraded as the target version product components.
9. A computer device, comprising:
the system comprises a central processing unit, a memory and an input/output interface;
the memory is a transient memory or a persistent memory;
the central processor is configured to communicate with the memory and execute the instructions in the memory to perform the method of any of claims 1-6.
10. A computer storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210254775.6A CN114637526A (en) | 2022-03-15 | 2022-03-15 | Product component upgrading method and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210254775.6A CN114637526A (en) | 2022-03-15 | 2022-03-15 | Product component upgrading method and related equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114637526A true CN114637526A (en) | 2022-06-17 |
Family
ID=81947537
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210254775.6A Pending CN114637526A (en) | 2022-03-15 | 2022-03-15 | Product component upgrading method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114637526A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117472411A (en) * | 2023-12-27 | 2024-01-30 | 北谷电子(无锡)有限公司 | Upgrade method compatible with multiple upgrade protocols |
-
2022
- 2022-03-15 CN CN202210254775.6A patent/CN114637526A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117472411A (en) * | 2023-12-27 | 2024-01-30 | 北谷电子(无锡)有限公司 | Upgrade method compatible with multiple upgrade protocols |
| CN117472411B (en) * | 2023-12-27 | 2024-05-14 | 北谷电子(无锡)有限公司 | Upgrade method compatible with multiple upgrade protocols |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2018196559A1 (en) | Method and apparatus for dealing with abnormality of application program, and storage medium | |
| CN111144839B (en) | Project construction method, continuous integration system and terminal equipment | |
| CN110414239B (en) | Software supply chain security analysis method and device | |
| CN109918285B (en) | Security identification method and device for open source software | |
| CN111723313A (en) | Page jump processing method, device, equipment and storage medium | |
| CN110225078B (en) | Application service updating method, system and terminal equipment | |
| EP3828696A1 (en) | Method invoke chain tracing method, electronic apparatus, and computer-readable storage medium | |
| CN105095759A (en) | File detection method and device | |
| CN109828780B (en) | Open source software identification method and device | |
| CN108460271B (en) | Terminal identification method and device | |
| CN111367531B (en) | Code processing method and device | |
| CN112380170B (en) | File updating operation association method and device and computer equipment | |
| CN112068874B (en) | Continuous integration method and device for software items, terminal equipment and storage medium | |
| CN115292163A (en) | Application program detection method and device and computer readable storage medium | |
| CN111124480A (en) | Application package generation method and device, electronic equipment and storage medium | |
| CN114637526A (en) | Product component upgrading method and related equipment | |
| CN111611124A (en) | Monitoring equipment analysis method and device, computer device and storage medium | |
| US6865742B1 (en) | Run-time property-based linking of software modules | |
| CN112416385A (en) | Acquisition component management method and system | |
| CN109408104B (en) | Method and device for acquiring game integration information | |
| CN113595762B (en) | Network card configuration storage method and device | |
| CN115455414A (en) | Safety detection method and device | |
| CN110891097B (en) | Cross-device user identification method and device | |
| CN114356346A (en) | Application program deployment method, device, storage medium and electronic equipment | |
| CN110704483A (en) | User routing process positioning method, device, storage medium and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |