CN113535221A - Method and device for managing application version - Google Patents
Method and device for managing application version Download PDFInfo
- Publication number
- CN113535221A CN113535221A CN202010301220.3A CN202010301220A CN113535221A CN 113535221 A CN113535221 A CN 113535221A CN 202010301220 A CN202010301220 A CN 202010301220A CN 113535221 A CN113535221 A CN 113535221A
- Authority
- CN
- China
- Prior art keywords
- configuration table
- application
- configuration
- component
- identification
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/53—Decompilation; Disassembly
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a device for managing application versions, and relates to the technical field of computers. One embodiment of the method comprises: determining an application version identifier of an application to be installed, and acquiring a target configuration table corresponding to the application version identifier from a configuration table set of the application to be installed; and acquiring component data corresponding to each configuration record according to the integration type and the component identification of each configuration record in the target configuration table, and installing the application to be installed according to the component data. The implementation method creates a configuration table for each version of the application, can realize efficient management of the application of each version, is convenient to search, does not need component open source, and has small content risk. By setting the integration type including source code integration in the configuration table, source code form integration can be performed, and problems can be located and repaired quickly.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for managing application versions.
Background
In the prior art, the modules in the iOS application are generally managed by using cocoadods (OS X and a third class library management tool under the iOS). The Cooapaods integrates the binary files of each component into the main project, and cannot integrate in a source code form. The simultaneous development effect of multiple versions of applications is not obvious, and the searching of historical versions is difficult. In addition, installation of the application often requires that the components be open source, which presents a significant content risk.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for managing application versions, which create a configuration table for each version of an application, can implement efficient management of applications of each version, are convenient to search, do not need component sourcing, and have a low content risk. By setting the integration type including source code integration in the configuration table, source code form integration can be performed, and problems can be located and repaired quickly.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a method for application version management, including:
determining an application version identifier of an application to be installed, and acquiring a target configuration table corresponding to the application version identifier from a configuration table set of the application to be installed; the set of configuration tables includes: at least one configuration table and an application version identification of the configuration table;
acquiring component data corresponding to each configuration record according to the integration type and the component identification of each configuration record in the target configuration table, and installing the application to be installed according to the component data; the configuration record includes: component identification and integration type.
Optionally, the method of the embodiment of the present invention further includes: before a target configuration table corresponding to the application version identification is obtained from the configuration table set of the application to be installed, the configuration table set is created according to the following steps:
creating an empty configuration table, and determining an application version identifier of the configuration table;
selecting components to be integrated into each configuration record in the configuration table from the published component set, setting component identifications and integration types of the components, and forming each configuration record of the configuration table.
Optionally, the method of the embodiment of the present invention further includes: before selecting the components to be integrated into each configuration record in the configuration table from the published component set, converting the component source codes of the components of the applications to be installed into binary files for publishing, and marking the component identifiers of the components.
Optionally, the integration type includes: source code integration and binary integration.
Optionally, the configuration table set further includes: a written description of the configuration table.
Optionally, the application version identification includes: a release version identification and an internal version identification.
Optionally, the component identification comprises: a component name identification and a component version identification.
Optionally, the configuration record further comprises at least one of: integration time, integrator.
According to a second aspect of the embodiments of the present invention, there is provided an apparatus for application version management, including:
the analysis module is used for determining an application version identifier of an application to be installed and acquiring a target configuration table corresponding to the application version identifier from a configuration table set of the application to be installed; the set of configuration tables includes: at least one configuration table and an application version identification of the configuration table;
the installation module is used for acquiring component data corresponding to each configuration record according to the integration type and the component identification of each configuration record in the target configuration table and installing the application to be installed according to the component data; the configuration record includes: component identification and integration type.
Optionally, the apparatus in this embodiment of the present invention further includes a configuration module, configured to: before the analysis module acquires a target configuration table corresponding to the application version identifier from the configuration table set of the application to be installed, the configuration table set is created according to the following steps:
creating an empty configuration table, and determining an application version identifier of the configuration table;
selecting components to be integrated into each configuration record in the configuration table from the published component set, setting component identifications and integration types of the components, and forming each configuration record of the configuration table.
Optionally, the apparatus in the embodiment of the present invention further includes a publishing module, configured to: before the configuration module selects the components to be integrated into each configuration record in the configuration table from the published component set, converting the component source codes of the components of the applications to be installed into binary files for publishing, and marking the component identifications of the components.
Optionally, the integration type includes: source code integration and binary integration.
Optionally, the configuration table set further includes: a written description of the configuration table.
Optionally, the application version identification includes: a release version identification and an internal version identification.
Optionally, the component identification comprises: a component name identification and a component version identification.
Optionally, the configuration record further comprises at least one of: integration time, integrator.
According to a third aspect of the embodiments of the present invention, there is provided an electronic device for application version management, including:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method provided by the first aspect of the embodiments of the present invention.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the method provided by the first aspect of embodiments of the present invention.
One embodiment of the above invention has the following advantages or benefits: the configuration table is created for each version of the application, so that the efficient management of the application of each version can be realized, the searching is convenient, the component opening source is not needed, and the content risk is low. By setting the integration type including source code integration in the configuration table, source code form integration can be performed, and problems can be located and repaired quickly.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main flow of a method of application version management of an embodiment of the present invention;
FIG. 2 is a schematic diagram of a configuration table set in an embodiment of the invention;
FIG. 3 is a schematic diagram of the composition of a configuration table in some embodiments of the invention;
FIG. 4 is a schematic diagram of the components of a configuration table in accordance with further embodiments of the present invention;
FIG. 5 is a flow diagram illustrating component publishing in an embodiment of the invention;
FIG. 6 is a flow chart illustrating the generation of a configuration table in an embodiment of the present invention;
FIG. 7 is a schematic diagram of the main modules of an apparatus for application version management according to an embodiment of the present invention;
FIG. 8 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 9 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
According to an aspect of an embodiment of the present invention, there is provided a method for managing application versions, including:
determining an application version identifier of an application to be installed, and acquiring a target configuration table corresponding to the application version identifier from a configuration table set of the application to be installed;
and acquiring component data corresponding to each configuration record according to the integration type and the component identification of each configuration record in the target configuration table, and installing the application to be installed according to the component data.
The application version identification is used for uniquely representing one version of the application, and each version corresponds to one configuration table. The application Version identification may include only an identification of a release Version (Version), i.e., a publicly released Version of the application, emphasizing functionality, typically with some/significant changes, improvements, or additions in functionality, including repairs to some significant vulnerabilities, such as: v1.0, V1.01, V2.0, V2.3. The application version identifier may also only include an identifier (Build) of an internal version, that is, a version generated after any modification and recompilation of the program source code, which may occur in a debugging, optimizing and testing stage before the software is released publicly, or may occur after the software is released officially. In an alternative embodiment, the application version identification comprises: a release version identification and an internal version identification. Each configuration record in the configuration table comprises a release version identifier and an internal version identifier, so that the application of each release version and internal version can be managed conveniently.
The configuration table set refers to a set of configuration tables for all versions of an application, as shown in fig. 2. The set of configuration tables includes: the configuration table comprises at least one configuration table and application version identification of the configuration table, so that the corresponding configuration table can be obtained according to the application version identification. The embodiment of the invention creates a configuration table for each version of the application, can realize the high-efficiency management of the application of each version, is convenient to search, does not need to open the source of the component, and has smaller content risk. The configuration tables can be flexibly switched, the information is automatically pulled according to the configuration tables for installation when the application is installed, the application running environment is quickly established, and application special scenes can be efficiently created even during development and testing. If a problem is found during application maintenance, a certain version can be traced back quickly, so that labor and time can be saved in development and maintenance, and the time required for recovering the application environment is greatly prolonged.
Optionally, the configuration table set further comprises: the configuration table is a written description, which is a simple introduction to the configuration table, such as the primary function (e.g., due to testing or publishing, etc.). And a text description is set for each configuration table, so that the quick distinction between similar version identifications is convenient to carry out during version selection.
As shown in fig. 2, the configuration table includes one or more configuration records, and each configuration record corresponds to a component of the application. The configuration record includes: component identification and integration type. The component identification is used for uniquely representing one component, and the component corresponding to the configuration record can be determined according to the component identification. The content of the component identification can be selectively set according to actual conditions. Optionally, the component identification comprises: a component name identification and a component version identification. Each configuration record in the configuration table comprises a component name identifier and a component version identifier, so that components of different versions can be selected conveniently according to integration requirements.
The integration modes are different, and the acquired component data types are different. The specific content of the integration type can be selectively set according to actual conditions, and the integration type exemplarily comprises source code integration and binary integration. The integration type including source code integration is set in the configuration table, source code form integration can be performed, problems can be located and repaired quickly, modification in an independent component is not needed, and then the integration type is integrated into an application for verification, and development and debugging are very convenient. In addition, the embodiment can realize fast switching between the source code and the binary.
Optionally, the configuration record further comprises at least one of: integration time, integrator. Each configuration record in the configuration table comprises an integration time, so that the last completion time of the configuration record can be conveniently known, and each configuration record in the configuration table comprises an integrator, so that a person in charge can be conveniently and quickly found when the function of the component is in a problem.
The configuration table of an application can be composed in various ways, and those skilled in the art can selectively set the configuration table according to actual needs. Fig. 3 and 4 show schematic diagrams of the composition of the configuration table in alternative embodiments of the invention. In the embodiment shown in fig. 3, all components are components under the application. As shown in fig. 3, all the components contained in the configuration table come from the application App-a, and each component contains different business logic contents. The configuration selection is made as required, and the use of the configuration table to the component A, C, D below the application App-A is shown in FIG. 3. In the embodiment shown in FIG. 4, the configuration table contains components under multiple applications. As shown in fig. 4, the components under three applications B, C, D are used below one configuration table of the application App-a. These include component A, B under application B, component B under application C, and component A under application D.
Fig. 1 is a schematic diagram of a main flow of a method for application version management according to an embodiment of the present invention, and fig. 1 shows an installation flow of a single configuration table. Firstly, a configuration table required to be used is selected according to personal requirements. The record in the table can be regarded as an array, each of the array is a configuration record, one configuration record is read, whether the component integration type in the configuration record is source code integration or not is judged, if the component integration type is the source code integration, the component source code is acquired to the project directory, and if the component integration type is a binary system, the binary file is acquired to the project. And sequentially reading the contents in the configuration table until the last configuration record is read, and then installing the contents in the configuration table. At this time, the switching project can completely reproduce the content of the application version corresponding to the configuration table. The installation process is also executed when the configuration table is switched for installation, but if some components in the new configuration table are downloaded before, the files of the server do not need to be pulled, so that the time for installing the configuration table can be saved.
Optionally, the method of the embodiment of the present invention further includes: before a target configuration table corresponding to the application version identification is obtained from the configuration table set of the application to be installed, the configuration table set is created according to the following steps: creating an empty configuration table, and determining an application version identifier of the configuration table; selecting components to be integrated into each configuration record in the configuration table from the published component set, setting component identifications and integration types of the components, and forming each configuration record of the configuration table.
Illustratively, as shown in fig. 6, the step of generating a configuration table includes:
(1) creating a configuration table: and filling Version identifications Version and Build of the configuration table, and configuring a simple text description for the configuration table to illustrate the main function of the configuration table, so that the quick distinction between similar Version numbers is conveniently carried out when the versions are selected later.
(2) And (3) component release: this step may be skipped if the component has already published a version and has no updated content. When the component is released, the source code part of the component is printed into a binary file (frame), the frame is uploaded to the server, and the code is printed with a version label, which is shown in fig. 5.
(3) Assembly integration: to integrate the components into a certain configuration table, the Version and Version of the configuration table to be integrated are selected first, and the Version identification and the integration type of the components are prompted to be selected during integration so as to integrate the component content according to the needs. The functions of different versions of the component are possibly not the same, and the required version of the component is selected. The configuration table integration type selects source code integration, so that debugging and code modification can be conveniently carried out, and problems can be quickly corrected.
(4) If other components are required to be integrated, repeating the steps (2) and (3) until the components required to be integrated are completely integrated, and forming a complete configuration table.
Optionally, the method of the embodiment of the present invention further includes: before selecting the components to be integrated into each configuration record in the configuration table from the published component set, converting the component source codes of the components of the applications to be installed into binary files for publishing, and marking the component identifiers of the components. In the actual application process, the binary file may be uploaded to the server for storage and release, as shown in fig. 5.
The embodiment of the invention creates a configuration table for each version of the application, can realize the high-efficiency management of the application of each version, is convenient to search, does not need to open the source of the component, and has smaller content risk. By setting the integration type including source code integration in the configuration table, source code form integration can be performed, and problems can be located and repaired quickly.
When the configuration table of each application version is created, the configuration table can be locked first, and after the integration time is finally determined, the unlocking is performed within the integration time range, and each module principal performs the integration of the modules. Locking and unlocking is equivalent to the management of rights, and anyone cannot add components to the configuration table or update existing versions of components while locking. After unlocking, the person with the configuration table integration authority can implement the integration component operation. In general, each version of the application is released, and the configuration table corresponding to the version is in a locked state and is not modified by anyone.
It should be noted that the method in the embodiment of the present invention may be used for managing modules in an iOS application, and may also be used for managing modules in an android application. When the method is applied to the module management in the android application, the implementation details of a part of the module management are slightly changed, for example, the application Version identifier signs Version and Build are modified into the Version identifier of the application in the android system.
According to a second aspect of the embodiments of the present invention, there is provided an apparatus for implementing the above method.
Fig. 7 is a schematic diagram of main modules of an apparatus for application version management according to an embodiment of the present invention, and as shown in fig. 7, an apparatus 700 for application version management includes:
the analysis module 701 determines an application version identifier of an application to be installed, and acquires a target configuration table corresponding to the application version identifier from a configuration table set of the application to be installed; the set of configuration tables includes: at least one configuration table and an application version identification of the configuration table;
an installation module 702, configured to obtain component data corresponding to each configuration record according to the integration type and the component identifier of each configuration record in the target configuration table, and install the application to be installed according to the component data; the configuration record includes: component identification and integration type.
Optionally, the apparatus of the embodiment of the present invention further includes a configuration module (not shown in the figure) configured to: before the analysis module acquires a target configuration table corresponding to the application version identifier from the configuration table set of the application to be installed, the configuration table set is created according to the following steps:
creating an empty configuration table, and determining an application version identifier of the configuration table;
selecting components to be integrated into each configuration record in the configuration table from the published component set, setting component identifications and integration types of the components, and forming each configuration record of the configuration table.
Optionally, the apparatus according to the embodiment of the present invention further includes a publishing module (not shown in the figure), configured to: before the configuration module selects the components to be integrated into each configuration record in the configuration table from the published component set, converting the component source codes of the components of the applications to be installed into binary files for publishing, and marking the component identifications of the components.
Optionally, the configuration table set further includes: a written description of the configuration table.
Optionally, the application version identification includes: a release version identification and an internal version identification.
Optionally, the integration type includes: source code integration and binary integration.
Optionally, the component identification comprises: a component name identification and a component version identification.
Optionally, the configuration record further comprises at least one of: integration time, integrator.
According to a third aspect of the embodiments of the present invention, there is provided an electronic device for application version management, including:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method provided by the first aspect of the embodiments of the present invention.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the method provided by the first aspect of embodiments of the present invention.
Fig. 8 illustrates an exemplary system architecture 800 of an apparatus to which a method of application version management or application version management of an embodiment of the invention may be applied.
As shown in fig. 8, the system architecture 800 may include terminal devices 801, 802, 803, a network 804, and a server 805. The network 804 serves to provide a medium for communication links between the terminal devices 801, 802, 803 and the server 805. Network 804 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 801, 802, 803 to interact with a server 805 over a network 804 to receive or send messages or the like. The terminal devices 801, 802, 803 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 801, 802, 803 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 805 may be a server that provides various services, such as a back-office management server (for example only) that supports shopping-like websites browsed by users using the terminal devices 801, 802, 803. The background management server may analyze and perform other processing on the received data such as the application version rollback request, and feed back a processing result (for example, component data of the historical version application corresponding to the rollback request — only by way of example) to the terminal device.
It should be noted that the method for managing application versions provided by the embodiment of the present invention is generally executed by the server 805, and accordingly, the apparatus for managing application versions is generally disposed in the server 805.
It should be understood that the number of terminal devices, networks, and servers in fig. 8 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 9, shown is a block diagram of a computer system 900 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU)901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The above-described functions defined in the system of the present invention are executed when the computer program is executed by a Central Processing Unit (CPU) 901.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprising: the analysis module is used for determining an application version identifier of an application to be installed and acquiring a target configuration table corresponding to the application version identifier from a configuration table set of the application to be installed; the set of configuration tables includes: at least one configuration table and an application version identification of the configuration table; the installation module is used for acquiring component data corresponding to each configuration record according to the integration type and the component identification of each configuration record in the target configuration table and installing the application to be installed according to the component data; the configuration record includes: component identification and integration type. The names of these modules do not in some cases form a limitation on the module itself, for example, a parsing module may also be described as a "module for installing the application to be installed according to the component data".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: determining an application version identifier of an application to be installed, and acquiring a target configuration table corresponding to the application version identifier from a configuration table set of the application to be installed; the set of configuration tables includes: at least one configuration table and an application version identification of the configuration table; acquiring component data corresponding to each configuration record according to the integration type and the component identification of each configuration record in the target configuration table, and installing the application to be installed according to the component data; the configuration record includes: component identification and integration type.
According to the technical scheme of the embodiment of the invention, the configuration table is created for each version of the application, so that the high-efficiency management of the application of each version can be realized, the searching is convenient, the component opening source is not needed, and the content risk is low. By setting the integration type including source code integration in the configuration table, source code form integration can be performed, and problems can be located and repaired quickly.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (11)
1. A method for application version management, comprising:
determining an application version identifier of an application to be installed, and acquiring a target configuration table corresponding to the application version identifier from a configuration table set of the application to be installed; the set of configuration tables includes: at least one configuration table and an application version identification of the configuration table;
acquiring component data corresponding to each configuration record according to the integration type and the component identification of each configuration record in the target configuration table, and installing the application to be installed according to the component data; the configuration record includes: component identification and integration type.
2. The method of claim 1, further comprising: before a target configuration table corresponding to the application version identification is obtained from the configuration table set of the application to be installed, the configuration table set is created according to the following steps:
creating an empty configuration table, and determining an application version identifier of the configuration table;
selecting components to be integrated into each configuration record in the configuration table from the published component set, setting component identifications and integration types of the components, and forming each configuration record of the configuration table.
3. The method of claim 2, further comprising: before selecting the components to be integrated into each configuration record in the configuration table from the published component set, converting the component source codes of the components of the applications to be installed into binary files for publishing, and marking the component identifiers of the components.
4. The method of any of claims 1-3, wherein the set of configuration tables further comprises: a written description of the configuration table.
5. A method according to any one of claims 1-3, wherein the application version identification comprises: a release version identification and an internal version identification.
6. The method of any of claims 1-3, wherein the component identification comprises: a component name identification and a component version identification.
7. An apparatus for application version management, comprising:
the analysis module is used for determining an application version identifier of an application to be installed and acquiring a target configuration table corresponding to the application version identifier from a configuration table set of the application to be installed; the set of configuration tables includes: at least one configuration table and an application version identification of the configuration table;
the installation module is used for acquiring component data corresponding to each configuration record according to the integration type and the component identification of each configuration record in the target configuration table and installing the application to be installed according to the component data; the configuration record includes: component identification and integration type.
8. The apparatus of claim 7, further comprising a configuration module to: before the analysis module acquires a target configuration table corresponding to the application version identifier from the configuration table set of the application to be installed, the configuration table set is created according to the following steps:
creating an empty configuration table, and determining an application version identifier of the configuration table;
selecting components to be integrated into each configuration record in the configuration table from the published component set, setting component identifications and integration types of the components, and forming each configuration record of the configuration table.
9. The apparatus of claim 8, further comprising a publishing module to: before the configuration module selects the components to be integrated into each configuration record in the configuration table from the published component set, converting the component source codes of the components of the applications to be installed into binary files for publishing, and marking the component identifications of the components.
10. An electronic device that applies version management, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-6.
11. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010301220.3A CN113535221B (en) | 2020-04-16 | 2020-04-16 | Method and device for managing application version |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010301220.3A CN113535221B (en) | 2020-04-16 | 2020-04-16 | Method and device for managing application version |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113535221A true CN113535221A (en) | 2021-10-22 |
| CN113535221B CN113535221B (en) | 2024-10-18 |
Family
ID=78120273
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010301220.3A Active CN113535221B (en) | 2020-04-16 | 2020-04-16 | Method and device for managing application version |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113535221B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114217847A (en) * | 2021-12-23 | 2022-03-22 | 四川启睿克科技有限公司 | Configuration adding and storing method for multiple versions in same environment |
| CN114489762A (en) * | 2021-11-26 | 2022-05-13 | 北京中软国际信息技术有限公司 | A method, system and electronic device for realizing multi-version application |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040188511A1 (en) * | 2002-12-20 | 2004-09-30 | Sprigg Stephen A. | System to automatically process components on a device |
| US20040188510A1 (en) * | 2002-12-20 | 2004-09-30 | Sprigg Stephen A. | System for registry-based automatic installation and component handling on a device |
| CN1739103A (en) * | 2002-12-20 | 2006-02-22 | 高通股份有限公司 | System for registry-based automatic installation and component handling on a device |
| CN102804132A (en) * | 2009-06-15 | 2012-11-28 | 微软公司 | Catalog-based software component management |
| CN105760184A (en) * | 2014-12-18 | 2016-07-13 | 深圳云之家网络有限公司 | Method and device for loading component |
| CN109086071A (en) * | 2018-08-22 | 2018-12-25 | 平安普惠企业管理有限公司 | A kind of method and server of management software version information |
| CN109871208A (en) * | 2019-01-04 | 2019-06-11 | 平安科技（深圳）有限公司 | Software systems generation method, device, computer readable storage medium and server |
-
2020
- 2020-04-16 CN CN202010301220.3A patent/CN113535221B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040188511A1 (en) * | 2002-12-20 | 2004-09-30 | Sprigg Stephen A. | System to automatically process components on a device |
| US20040188510A1 (en) * | 2002-12-20 | 2004-09-30 | Sprigg Stephen A. | System for registry-based automatic installation and component handling on a device |
| CN1739103A (en) * | 2002-12-20 | 2006-02-22 | 高通股份有限公司 | System for registry-based automatic installation and component handling on a device |
| CN102804132A (en) * | 2009-06-15 | 2012-11-28 | 微软公司 | Catalog-based software component management |
| CN105760184A (en) * | 2014-12-18 | 2016-07-13 | 深圳云之家网络有限公司 | Method and device for loading component |
| CN109086071A (en) * | 2018-08-22 | 2018-12-25 | 平安普惠企业管理有限公司 | A kind of method and server of management software version information |
| CN109871208A (en) * | 2019-01-04 | 2019-06-11 | 平安科技（深圳）有限公司 | Software systems generation method, device, computer readable storage medium and server |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114489762A (en) * | 2021-11-26 | 2022-05-13 | 北京中软国际信息技术有限公司 | A method, system and electronic device for realizing multi-version application |
| CN114489762B (en) * | 2021-11-26 | 2025-06-13 | 北京中软国际信息技术有限公司 | A method, system and electronic device for implementing multi-version application |
| CN114217847A (en) * | 2021-12-23 | 2022-03-22 | 四川启睿克科技有限公司 | Configuration adding and storing method for multiple versions in same environment |
| CN114217847B (en) * | 2021-12-23 | 2024-05-31 | 四川启睿克科技有限公司 | Multi-version configuration adding and saving method in same environment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113535221B (en) | 2024-10-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107832045B (en) | Method and apparatus for cross programming language interface conversion | |
| CN107491382B (en) | Log output method and device | |
| US8650288B2 (en) | Runtime usage analysis for a distributed policy enforcement system | |
| CN110795147A (en) | Interface protocol file management method and device | |
| CN113760276B (en) | Method and device for generating page code | |
| WO2019029451A1 (en) | Method for publishing mobile applications and electronic apparatus | |
| CN112988583A (en) | Method and device for testing syntax compatibility of database | |
| CN113312900A (en) | Data verification method and device | |
| CN113742321B (en) | Data updating method and device | |
| CN113535221B (en) | Method and device for managing application version | |
| CN116069725A (en) | File migration method, device, apparatus, medium and program product | |
| CN113032004A (en) | Method, apparatus and program product for managing development jobs in a development environment | |
| CN112905164B (en) | Project code processing method and device | |
| CN113805878B (en) | Plug-in engineering method, device, computer system and medium | |
| CN109683942B (en) | Script management method, script management device, script management medium and electronic equipment | |
| CN113448960A (en) | Method and device for importing form file | |
| CN116737662A (en) | Method, device, electronic equipment and storage medium for processing business data | |
| CN113254019B (en) | Method and device for registering front-end data stream status file | |
| CN115993981A (en) | Data processing method, device, electronic equipment and computer readable medium | |
| CN114489674A (en) | Data verification method and device of dynamic data model | |
| CN113746661A (en) | Service processing method and device | |
| CN113342357B (en) | Deployment method and device of software system | |
| CN113448932A (en) | Application program optimization method and device | |
| CN118069539B (en) | Data processing method, device, electronic equipment and storage medium | |
| CN110727739B (en) | Data storage 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |