CN117971284A - Method, system, equipment and storage medium for upgrading components in batches - Google Patents
Method, system, equipment and storage medium for upgrading components in batches Download PDFInfo
- Publication number
- CN117971284A CN117971284A CN202410383155.1A CN202410383155A CN117971284A CN 117971284 A CN117971284 A CN 117971284A CN 202410383155 A CN202410383155 A CN 202410383155A CN 117971284 A CN117971284 A CN 117971284A
- Authority
- CN
- China
- Prior art keywords
- component
- upgrading
- installation
- installation package
- server
- 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
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000009434 installation Methods 0.000 claims abstract description 145
- 238000012545 processing Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 4
- 238000004891 communication Methods 0.000 claims description 3
- 238000009877 rendering Methods 0.000 claims description 3
- 230000003203 everyday effect Effects 0.000 abstract description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002354 daily effect Effects 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000011900 installation process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Landscapes
- Stored Programmes (AREA)
Abstract
The application provides a method, a system, equipment and a storage medium for upgrading components in batches, and relates to the technical field of computers. The scheme comprises the following steps: responding to a client component installation upgrading request and/or a server component upgrading request, and acquiring page input information carrying an IP value of a server and a URL value of an installation package which are input by a user; traversing the IP value carried by the page input information based on the client component installation upgrading request to remotely log in a corresponding server, and determining to execute a corresponding component installation flow or component upgrading flow; and/or traversing the IP value carried by the page input information based on the server component upgrading request to remotely log in the corresponding server, traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding component. The scheme can effectively cope with the scene that a plurality of clients and/or service terminals are provided, and frequent component upgrading is required every day, so that the labor burden of corresponding staff is remarkably reduced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, a system, an apparatus, and a storage medium for upgrading components in batches.
Background
With increasing market competition and accelerating system iteration, higher requirements are particularly put on component upgrading iteration of a client and a server. The tester is often faced with a scene of facing a plurality of clients and/or servers and frequently upgrading the corresponding components for a plurality of times, so that the tester has complicated working content and large workload, and the operation and maintenance and the burden of the tester are greatly increased.
Disclosure of Invention
The application aims to provide a method, a system, equipment and a storage medium for upgrading components in batches, which can effectively cope with a scene that a plurality of clients and/or service ends are provided, and the components are frequently upgraded every day, so that the labor burden of corresponding staff is obviously reduced.
The application is realized in the following way:
in a first aspect, the present application provides a method for batch upgrade of components, comprising the steps of:
Responding to the component upgrading request, and acquiring corresponding page input information; the component upgrade request comprises a client component installation upgrade request and/or a server component upgrade request, and the page input information carries an IP value of a server and a URL value of an installation package which are input by a user; traversing the IP value carried by the page input information based on the client component installation upgrading request to remotely log in a corresponding server, and determining to execute a corresponding component installation flow or component upgrading flow; and/or traversing the IP value carried by the page input information based on the server component upgrading request to remotely log in the corresponding server, traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding component.
Further, based on the foregoing, the component mounting process includes: and judging whether the installation package is installed or not based on the URL value of the installation package, if so, determining to uninstall the corresponding component installed by the installation package, otherwise, determining to install the installation package. Downloading the installation package into a folder in the first path through the curl, and deleting the directory with the storage time greater than a first preset time threshold value in the first path. And judging whether the client belongs to the master version or not based on the URL value of the installation package, and calling corresponding installation instructions respectively based on a judging result.
Further, based on the foregoing solution, the foregoing installing, based on the client component, an upgrade request, traversing an IP value carried by page input information, includes: when the IP values of the server input by the user are multiple, writing all the IP values into the configuration file, and when the corresponding component installation flow or the corresponding component upgrading flow is executed, reading all the IP values from the configuration file to perform batch installation processing.
Further, based on the foregoing aspect, the step of calling the corresponding installation instruction based on the determination result includes: if the judging result is that the installation package belongs to the main version, judging the specific version of the installation package according to the URL value of the installation package again, and calling corresponding installation instructions according to different versions; and if the judging result does not belong to the main version, respectively calling corresponding installation instructions according to the suffix classification of the installation package. After the installation package is successfully installed, the installation result is stored in the target path in the form of a character string through command retrieval processing.
Further, based on the foregoing solution, the component upgrade procedure includes:
Downloading the installation package into a folder in the second path through the curl, and deleting the catalogue with the storage time greater than a second preset time threshold value in the second path. Analyzing the URL value of the installation package to obtain a client version identifier, and calling a corresponding upgrading instruction according to the client version identifier; the client version identifier is used for representing a system version index corresponding to the installation package.
Further, based on the foregoing solution, the step of downloading the corresponding installation package and upgrading the corresponding component includes: and traversing all URL values carried by the page input information, and identifying the component names included in the installation package based on the URL values so as to download the corresponding installation package based on the component names and upgrade the corresponding components.
In a second aspect, the present application provides a system for batch upgrade of components, comprising:
An information acquisition module configured to: responding to the component upgrading request, and acquiring corresponding page input information; the component upgrade request comprises a client component installation upgrade request and/or a server component upgrade request, and the page input information carries an IP value of a server and a URL value of an installation package which are input by a user. The client installation upgrade module is configured to: based on the client component installation upgrading request, traversing the IP value carried by the page input information to remotely log in the corresponding server, and determining to execute the corresponding component installation flow or component upgrading flow. And/or, a server upgrade module configured to: based on the server side component upgrading request, traversing the IP value carried by the page input information to remotely log in the corresponding server, traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding component.
Further, based on the foregoing scheme, the system is formed by a front-end and rear-end separated technical structure, wherein the rear end adopts a Flask framework based on Python to be responsible for specific business logic, and the front end adopts a CSS and JavaScript framework to pay attention to analysis and rendering of page styles and dynamic data.
In a third aspect, the present application provides an electronic device comprising at least one processor, at least one memory, and a data bus; wherein: the processor and the memory complete communication with each other through the data bus; the memory stores program instructions for execution by the processor, the processor invoking the program instructions to perform the method of any of the first aspects.
In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method as in any of the first aspects above.
Compared with the prior art, the application has at least the following advantages or beneficial effects:
The application provides a method for upgrading components in batches, which comprises the steps of sequentially traversing IP and URL after corresponding page input information is acquired, remotely logging in a corresponding server and carrying out batch installation and upgrading on the components, so that the operation flow of upgrading the components by a tester can be greatly simplified, and the time and the workload of the tester are saved. That is, for the scenario that multiple clients and/or servers are provided and frequent component upgrades are required every day, the tester can more efficiently complete daily component upgrade work, and the test efficiency of the system is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method for batch upgrade of components according to an embodiment of the present application;
FIG. 2 is a flow chart of client side component installation upgrade according to an embodiment of the present application;
FIG. 3 is a flowchart of a server-side component upgrade according to an embodiment of the present application;
FIG. 4 is a block diagram illustrating one embodiment of a system for batch upgrade of components in accordance with the present application;
fig. 5 is a block diagram of an electronic device according to an embodiment of the present application.
Icon: 1. an information acquisition module; 2. the client is provided with an upgrade module; 3. a server side upgrading module; 4. a processor; 5. a memory; 6. a data bus.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The various embodiments and features of the embodiments described below may be combined with one another without conflict. And the naming or numbering of the steps in the present application does not mean that the steps in the method flow must be executed according to the time/logic sequence indicated by the naming or numbering, and the named or numbered flow steps may change the execution sequence according to the technical purpose to be achieved, so long as the same or similar technical effects can be achieved.
Example 1
For testers, a scenario that needs to face multiple clients and/or servers, and that needs to upgrade the corresponding components multiple times per day, is often encountered, resulting in a significant waste of the tester's working time and effort. Therefore, the embodiment of the application provides a method for upgrading components in batches, which can install or upgrade corresponding components in batches, so that a tester does not need to manually log in a server to execute a large number of commands in the test process, the automatic batch upgrading of the components is realized, the efficiency can be greatly improved, and the time and the workload of the tester are saved.
Referring to fig. 1-3, the method for upgrading components in batches includes the following steps:
Step S101: responding to the component upgrading request, and acquiring corresponding page input information; the component upgrade request comprises a client component installation upgrade request and/or a server component upgrade request, and the page input information carries an IP value of a server and a URL value of an installation package which are input by a user.
When the application is concretely implemented, two tab options can be set on the page: client component installation upgrades and server component upgrades. And then clicking a determination button after filling in the URL of the server IP and the installation package on the page so as to acquire corresponding page input information. Specifically, a Flask framework based on Python can be adopted at the back end when the corresponding system is designed, and a CSS and JavaScript framework are adopted at the front end, so that a friendly interface and good user experience are provided for a user.
Step S102: based on the client component installation upgrading request, traversing the IP value carried by the page input information to remotely log in the corresponding server, and determining to execute the corresponding component installation flow or component upgrading flow.
And/or, step S103: based on the server side component upgrading request, traversing the IP value carried by the page input information to remotely log in the corresponding server, traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding component.
When the component upgrading request is a client installation upgrading request, after responding to the client component installation upgrading request, acquiring corresponding page input information, and then judging whether to install or upgrade the component by the rear end so as to execute a component installation flow or a component upgrading flow according to a judging result. Meanwhile, if the component upgrading request is a server component upgrading request, upgrading all installation packages corresponding to the URL values on the servers corresponding to all the IP values in a mode of traversing the IP values and then traversing the URL values. Through the technical means of the embodiment, the system can process a plurality of IP values, realize the concurrent upgrade of a plurality of clients and reduce a large amount of upgrade time. Meanwhile, the last executed IP value can be recorded, so that when a plurality of clients are upgraded, only the first IP value is needed to be input, and the services corresponding to all the last executed IP values can be upgraded. Correspondingly, the URL value can be recorded, so that the URL value of the last time is automatically acquired and used for downloading the corresponding component package when upgrading next time. Therefore, only the IP value is required to be filled, the URL value is not filled, and batch upgrading of the components can be carried out by utilizing the URL value recorded last time.
Illustratively, an upgrade portion is installed for the client component: in order to facilitate maintenance and to accommodate more versions, step S102 may be encapsulated into a Work method class, where upgrades and installations, as well as other different versions, are determined to be compatible and adapted. Correspondingly, in order to achieve the goal of installing or upgrading a plurality of clients, mutiprocessing libraries can be used for calculating the number of ips filled in by pages to create a plurality of threads, a Queue object and other parameters are brought into a Work method class, the result put of each thread (the resources on the update server (the whole resources after the clients provide the update)) is put into the Queue object in the Work method class, and after all the threads are finished, the result is taken out of the Queue object and displayed on the page.
Based on the foregoing solution, in an implementation manner of the present application, the installing an upgrade request based on a client component, traversing an IP value carried by page input information, includes: when the IP values of the server input by the user are multiple, writing all the IP values into the configuration file, and when the corresponding component installation flow or the corresponding component upgrading flow is executed, reading all the IP values from the configuration file to perform batch installation processing. That is, in order to realize batch installation, after all the IP values are obtained, the number of the IPs is determined, if the number is greater than 1, all the IP values are written into the configuration file, and when installation and upgrading are performed next time, all the IPs are preferentially read out from the configuration file and are transmitted to the Work method for use.
In addition, for the server component upgrade portion: in order to realize the upgrading of a plurality of component installation packages and a plurality of servers, the URL value and the IP value can be separated and processed in a comma form on the corresponding page so as to accurately acquire the corresponding page input information. Accordingly, in order to facilitate maintenance and to be compatible with more versions, in a specific implementation of the present application, the above-mentioned step S103 may be encapsulated into the UpgradeServer method. Next, to update all installation packages at one time, the option of page selection is processed, and URL values may be processed through the Requests and BeautifulSoup library in Python to obtain the link information of all installation packages in the URL values, and then the method of entering UpgradeServer is traversed to implement the upgrade. Furthermore, for convenience of use, instead of inputting the URL value into the page every time, after the URL value is input for component upgrade for the first time, the URL value of the current time is stored into the corresponding configuration file, and the URL value is not input when the component is upgraded next time, but the URL value in the configuration file is read first and used for component upgrade.
The step S102 and the step S103 may be performed simultaneously or separately. The execution order of steps S102 and S103 is not limited if they are performed separately.
Based on the foregoing, in an implementation manner of the present application, the component mounting process includes:
Step S201: judging whether the installation package is installed or not based on the URL value of the installation package, if so, determining to uninstall the corresponding component installed by the installation package, otherwise, determining to install the installation package;
Step S202: downloading the installation package into a folder in the first path through the curl, and deleting the catalogue with the storage time greater than a first preset time threshold value in the first path;
Step S203: and judging whether the client belongs to the master version or not based on the URL value of the installation package, and calling corresponding installation instructions respectively based on a judging result.
As shown in fig. 2, after the back end determines that the client component is installed, it needs to determine whether the corresponding installation package is installed, and if so, it needs to uninstall and then install, and then download the corresponding installation package into the folder under the first path through the curl (the name of the folder may be named with the timestamp of the client so as to determine the setup time thereof). Meanwhile, the catalogue larger than the first preset time threshold can be deleted, so that the root catalogue is prevented from being full. Illustratively, the directory in the first path may be checked for deletion by the find command for more than 2 days (which may be set as desired). And finally, judging the values of the URL values corresponding to the different components to carry out corresponding installation instructions on the clients of different types. Therein, the full name of Curl is CommandLine Uniform Resource Locator, i.e. data or file transfer is performed in the command line using a URL.
Specifically, in an implementation manner of the present application, the step of calling the corresponding installation instruction based on the determination result includes: if the judging result is that the installation package belongs to the main version, judging the specific version of the installation package according to the URL value of the installation package again, and calling corresponding installation instructions according to different versions; if the judging result does not belong to the main version, respectively calling corresponding installation instructions according to suffix classification of the installation package; after the installation package is successfully installed, the installation result is stored in the target path in the form of a character string through command retrieval processing.
For example, if it is determined that the client belongs to the master version, it is specifically determined to which version the client belongs again according to the name of the installation package, and different versions execute different installation instructions. And if the client is judged not to belong to the main version, respectively executing corresponding installation instructions according to whether the suffix of the installation package is run or rpm. And after the installation is successful, the installation result is stored in the corresponding data string (e.g., res_str) through command retrieval.
Based on the foregoing, in an implementation manner of the present application, the component upgrade procedure includes:
Step S401: downloading the installation package into a folder in a second path through a curl, and deleting the catalogue with the storage time in the second path being longer than a second preset time threshold;
Step S402: analyzing the URL value of the installation package to obtain a client version identifier, and calling a corresponding upgrading instruction according to the client version identifier; the client version identifier is used for representing a system version index corresponding to the installation package.
As shown in fig. 2, compared with the component installation process, the component upgrade process has one less step of determining whether the corresponding component has been installed, and it can also download the installation package required for updating into the folder of the second path through the curl, and name the folder with the timestamp of the client so as to determine the setup time thereof. Meanwhile, the catalogue larger than the second preset time threshold can be deleted, so that the root catalogue is prevented from being full. Illustratively, the directory in the second path may be checked for deletion by the find command for more than 2 days (which may be set as desired). And finally, judging the values of the URL values corresponding to the different components to carry out corresponding upgrading instructions on the clients of different types.
Based on the foregoing solution, in an implementation manner of the present application, the step of downloading the corresponding installation package and upgrading the corresponding component includes: and traversing all URL values carried by the page input information, and identifying the component names included in the installation package based on the URL values so as to download the corresponding installation package based on the component names and upgrade the corresponding components.
For the upgrade of the server-side component, the method mainly comprises the following steps: after the page input information is obtained, judging whether the component name is in the package name according to the package name in the URL so as to execute the corresponding upgrading command of the component, and returning an execution result. For example, a director (obviously uniquely distinguishable identifier) is in a package name, a folder of a director+timestamp is created and a package is downloaded, decompression and upgrade are performed (upgrade. Sh command is used for a technical support engineer to manually perform a system or a system component upgrade, or is used for configuring a system upgrade flow, etc.), and other packages execute elif (re-judgment) and upgrade commands corresponding to other packages.
Example 2
Referring to fig. 4, an embodiment of the present application provides a system for upgrading components in batches, which includes:
An information acquisition module 1 configured to: responding to the component upgrading request, and acquiring corresponding page input information; the component upgrade request comprises a client component installation upgrade request and/or a server component upgrade request, and the page input information carries an IP value of a server and a URL value of an installation package which are input by a user. The client installation upgrade module 2 is configured to: based on the client component installation upgrading request, traversing the IP value carried by the page input information to remotely log in the corresponding server, and determining to execute the corresponding component installation flow or component upgrading flow. And/or, the server upgrade module 3 is configured to: based on the server side component upgrading request, traversing the IP value carried by the page input information to remotely log in the corresponding server, traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding component.
Based on the foregoing scheme, in an implementation manner of the present application, the system is formed by a technical structure with separated front and rear ends, wherein the rear end adopts a Flask framework based on Python to be responsible for specific service logic, and the front end adopts a CSS and JavaScript framework to pay attention to analysis and rendering of page styles and dynamic data.
The specific implementation process of the above system refers to a method for upgrading components in batches provided in embodiment 1, which is not described herein.
Example 3
Referring to fig. 5, an embodiment of the present application provides an electronic device comprising at least one processor 4, at least one memory 5 and a data bus 6; wherein: the processor 4 and the memory 5 complete the communication with each other through the data bus 6; the memory 5 stores program instructions executable by the processor 4, which the processor 4 invokes to perform a method of batch upgrades of components. For example, implementation:
Responding to the component upgrading request, and acquiring corresponding page input information; the component upgrade request comprises a client component installation upgrade request and/or a server component upgrade request, and the page input information carries an IP value of a server and a URL value of an installation package which are input by a user; traversing the IP value carried by the page input information based on the client component installation upgrading request to remotely log in a corresponding server, and determining to execute a corresponding component installation flow or component upgrading flow; and/or traversing the IP value carried by the page input information based on the server component upgrading request to remotely log in the corresponding server, traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding component.
The Memory 5 may be, but is not limited to, random access Memory (Random Access Memory, RAM), read Only Memory (ROM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.
The processor 4 may be an integrated circuit chip with signal processing capabilities. The processor 4 may be a general-purpose processor including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but may also be a digital signal processor (DIGITAL SIGNAL Processing, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components.
It will be appreciated that the configuration shown in fig. 5 is merely illustrative, and that the electronic device may also include more or fewer components than shown in fig. 5, or have a different configuration than shown in fig. 5. The components shown in fig. 5 may be implemented in hardware, software, or a combination thereof.
Example 4
The present application provides a computer readable storage medium having stored thereon a computer program which when executed by a processor 4 implements a method of component batch upgrades. For example, implementation:
Responding to the component upgrading request, and acquiring corresponding page input information; the component upgrade request comprises a client component installation upgrade request and/or a server component upgrade request, and the page input information carries an IP value of a server and a URL value of an installation package which are input by a user; traversing the IP value carried by the page input information based on the client component installation upgrading request to remotely log in a corresponding server, and determining to execute a corresponding component installation flow or component upgrading flow; and/or traversing the IP value carried by the page input information based on the server component upgrading request to remotely log in the corresponding server, traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding component.
The above functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It will be evident to those skilled in the art that the application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (10)
1. A method for batch upgrading of components, comprising the steps of:
Responding to the component upgrading request, and acquiring corresponding page input information; the component upgrading request comprises a client component installation upgrading request and/or a server component upgrading request, and the page input information carries an IP value of a server and a URL value of an installation package which are input by a user;
Traversing the IP value carried by the page input information based on the client component installation upgrading request to remotely log in a corresponding server, and determining to execute a corresponding component installation flow or component upgrading flow; and/or the number of the groups of groups,
Based on the server side component upgrading request, traversing the IP value carried by the page input information to remotely log in the corresponding server, traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding component.
2. The method for batch upgrading of components according to claim 1, wherein the component mounting process comprises:
judging whether the installation package is installed or not based on the URL value of the installation package, if so, determining to uninstall the corresponding component installed by the installation package, otherwise, determining to install the installation package;
Downloading the installation package into a folder in the first path through the curl, and deleting the catalogue with the storage time greater than a first preset time threshold value in the first path;
and judging whether the client belongs to the master version or not based on the URL value of the installation package, and calling corresponding installation instructions respectively based on a judging result.
3. The method for batch upgrade of components according to claim 2, wherein the traversing the IP value carried by the page input information based on the client component installation upgrade request comprises:
when the IP values of the server input by the user are multiple, writing all the IP values into the configuration file, and when the corresponding component installation flow or the corresponding component upgrading flow is executed, reading all the IP values from the configuration file to perform batch installation processing.
4. The method for batch upgrade of components according to claim 2, wherein the step of calling the corresponding installation instructions based on the determination results respectively comprises:
If the judging result is that the installation package belongs to the main version, judging the specific version of the installation package according to the URL value of the installation package again, and calling corresponding installation instructions according to different versions; if the judging result does not belong to the main version, respectively calling corresponding installation instructions according to suffix classification of the installation package;
After the installation package is successfully installed, the installation result is stored in the target path in the form of a character string through command retrieval processing.
5. The method for batch upgrading of components according to claim 1, wherein the component upgrading process comprises:
Downloading the installation package into a folder in a second path through a curl, and deleting the catalogue with the storage time in the second path being longer than a second preset time threshold;
analyzing the URL value of the installation package to obtain a client version identifier, and calling a corresponding upgrading instruction according to the client version identifier; the client version identifier is used for representing a system version index corresponding to the installation package.
6. The method for upgrading components in batch according to claim 1, wherein the step of traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding components comprises:
And traversing all URL values carried by the page input information, and identifying the component names included in the installation package based on the URL values so as to download the corresponding installation package based on the component names and upgrade the corresponding components.
7. A system for batch upgrades of components, comprising:
An information acquisition module configured to: responding to the component upgrading request, and acquiring corresponding page input information; the component upgrading request comprises a client component installation upgrading request and/or a server component upgrading request, and the page input information carries an IP value of a server and a URL value of an installation package which are input by a user;
the client installation upgrade module is configured to: traversing the IP value carried by the page input information based on the client component installation upgrading request to remotely log in a corresponding server, and determining to execute a corresponding component installation flow or component upgrading flow; and/or the number of the groups of groups,
The server-side upgrading module is configured to: based on the server side component upgrading request, traversing the IP value carried by the page input information to remotely log in the corresponding server, traversing all URL values carried by the page input information, downloading the corresponding installation package and upgrading the corresponding component.
8. The system for batch upgrade of components according to claim 7, wherein the system is composed of a front-end and back-end separated technical structure, wherein the back-end adopts a Flask framework based on Python to be responsible for specific business logic, and the front-end adopts a CSS and JavaScript framework to pay attention to the style of page and the analysis and rendering of dynamic data.
9. An electronic device comprising at least one processor, at least one memory, and a data bus; wherein: the processor and the memory complete communication with each other through the data bus; the memory stores program instructions for execution by the processor, the processor invoking the program instructions to perform the method of any of claims 1-6.
10. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the method according to any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410383155.1A CN117971284A (en) | 2024-04-01 | 2024-04-01 | Method, system, equipment and storage medium for upgrading components in batches |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410383155.1A CN117971284A (en) | 2024-04-01 | 2024-04-01 | Method, system, equipment and storage medium for upgrading components in batches |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117971284A true CN117971284A (en) | 2024-05-03 |
Family
ID=90863506
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410383155.1A Pending CN117971284A (en) | 2024-04-01 | 2024-04-01 | Method, system, equipment and storage medium for upgrading components in batches |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117971284A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105335183A (en) * | 2014-08-06 | 2016-02-17 | 乐视致新电子科技（天津）有限公司 | Software upgrade method and system |
| US20170351507A1 (en) * | 2016-06-04 | 2017-12-07 | Airwatch Llc | Silent upgrade of software with dependencies |
| CN115361119A (en) * | 2022-08-15 | 2022-11-18 | 中国铁道科学研究院集团有限公司 | Batch upgrading method and device for vehicle-mounted equipment software |
-
2024
- 2024-04-01 CN CN202410383155.1A patent/CN117971284A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105335183A (en) * | 2014-08-06 | 2016-02-17 | 乐视致新电子科技（天津）有限公司 | Software upgrade method and system |
| US20170351507A1 (en) * | 2016-06-04 | 2017-12-07 | Airwatch Llc | Silent upgrade of software with dependencies |
| CN115361119A (en) * | 2022-08-15 | 2022-11-18 | 中国铁道科学研究院集团有限公司 | Batch upgrading method and device for vehicle-mounted equipment software |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111061643B (en) | SDK cluster compatibility detection method and device, electronic equipment and storage medium | |
| CN111274512A (en) | Page loading method, device and medium | |
| CN113076253A (en) | Test method and test device | |
| CN111666201A (en) | Regression testing method, device, medium and electronic equipment | |
| CN113886485A (en) | Data processing method, device, electronic equipment, system and storage medium | |
| CN115757014A (en) | Power consumption testing method and device | |
| CN111107133A (en) | Generation method of difference packet, data updating method, device and storage medium | |
| CN109446047B (en) | Performance test platform script storage method, device, equipment and storage medium | |
| CN112860538A (en) | Method and device for performing interface regression test based on online log | |
| CN117971284A (en) | Method, system, equipment and storage medium for upgrading components in batches | |
| CN113821486B (en) | Method and device for determining dependency relationship between pod libraries and electronic equipment | |
| CN114879985B (en) | Method, device, equipment and storage medium for installing certificate file | |
| CN116204428A (en) | Test case generation method and device | |
| CN116069366A (en) | Client application program updating method and device, storage medium and electronic equipment | |
| CN111159142A (en) | Data processing method and device | |
| CN114968770A (en) | Automatic testing method, device, equipment and storage medium | |
| CN114189745A (en) | Set top box software switching management method and system and computer device | |
| CN111881112A (en) | Database configuration method and device and related equipment | |
| CN112988560A (en) | Method and device for testing system robustness | |
| CN113535221A (en) | Method and device for managing application version | |
| CN113254325A (en) | Test case processing method and device | |
| CN112579428A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN113608996B (en) | Mirror image compiling test method, system, device and readable storage medium | |
| EP3992782B1 (en) | Configuration retention service for web application servers | |
| CN118170630A (en) | Automatic test method 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 |