CN111399898B - Method and device for managing multi-module system code version and computer equipment - Google Patents
Method and device for managing multi-module system code version and computer equipment Download PDFInfo
- Publication number
- CN111399898B CN111399898B CN202010142301.3A CN202010142301A CN111399898B CN 111399898 B CN111399898 B CN 111399898B CN 202010142301 A CN202010142301 A CN 202010142301A CN 111399898 B CN111399898 B CN 111399898B
- Authority
- CN
- China
- Prior art keywords
- module
- version
- version number
- updated
- information
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The invention provides a method, a device and computer equipment for managing multi-module system code versions. The system at least comprises a first module and a second module, and the management method comprises the following steps: when a first module is updated, determining a version number with a newer version sequence in a first version number and a second version number, wherein the first version number is the current version number of the first module, and the second version number is the current version number of the second module; updating the version numbers with newer version sequences according to the version sequence rule to obtain a third version number; and determining the updated version number of the first module as a third version number. The invention can better manage the code version of the multi-module system, so that the management among the modules can be independent and can be rolled back conveniently.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a method, an apparatus, and a computer device for managing code versions of a multi-module system.
Background
As the integration of computer software system functions increases, prior art computer software systems typically include multiple functional modules. When a system is composed of a plurality of functional modules, it is necessary to manage the code versions of the respective modules so that the system can issue a code of a specific version at any time. For code version management of a multi-module system, there are currently two main methods:
One is centralized. That is, the code blocks of all the modules are placed in the same code warehouse, and the code blocks of the modules share a version number and are packaged and issued together. When the system scale grows, the code blocks of the modules are increased, and different modules respectively belong to different departments, the centralized management mode can increase the coupling among the code blocks. Because the code blocks of all modules are in the same repository, each time a code block of a module changes, this unified repository is affected. This is a risk for other modules that do not need to be updated. In addition, in the same code warehouse, different authorities cannot be set according to different modules, so that separate management cannot be performed on code blocks of different departments, the exposure ranges of codes of different modules cannot be effectively controlled, and the risk of operation management is increased.
The other is a separation type. The method has the advantages that the modules are divided into different warehouses for management, version numbers are mutually independent, the authority problem of centralized management and the coupling problem between code blocks are solved, however, the version numbers of the code blocks of the modules have no association relationship, and the whole system cannot roll back to a certain historical functional point.
Therefore, the management method, the device and the computer equipment for the multi-module system code version are provided, so that the management of the multi-module system code version is better, the management of each module can be independent and can be conveniently rolled back, and the technical problem to be solved in the field is needed.
Disclosure of Invention
The invention aims to provide a method, a device and computer equipment for managing code versions of a multi-module system, which are used for solving the technical problem that the code version management method of a separated multi-module system in the prior art is inconvenient to roll back the whole system to the same historical node.
In order to achieve the above object, the present invention provides a method for managing code versions of a multi-module system.
The multi-module system at least comprises a first module and a second module, and the management method comprises the following steps: when a first module is updated, determining a version number with a newer version sequence in a first version number and a second version number, wherein the first version number is the current version number of the first module, and the second version number is the current version number of the second module; updating the version numbers with newer version sequences according to the version sequence rule to obtain a third version number; and determining the updated version number of the first module as a third version number.
Further, the version number includes at least two pieces of sub information, each piece of sub information corresponds to an update level, and the step of updating the version number updated in sequence according to the version sequence rule to obtain a third version number includes: determining an update level of code block updates of the first module; in version numbers with newer version sequences, sub-information corresponding to the determined update level is obtained, and sub-information to be updated is obtained; adding a preset increment to the sub-information to be updated to obtain updated sub-information; if the sub information to be updated is at the lowest update level, replacing the sub information to be updated in the version number with the newer version sequence by using the update sub information to obtain a third version number; if the sub information to be updated is not the lowest update level, replacing the sub information to be updated in the version number with the updated sub information in version sequence, and setting all the sub information with the update level lower than that of the sub information to be updated as initial sub information to obtain a third version number.
Further, the management method further comprises: when the first module and the second module are updated at the same time, judging whether the first module and the second module meet a preset association relation; when the first module and the second module meet a preset association relation, determining that the updated version number of the second module is a third version number; and when the first module and the second module do not meet the preset association relation, updating the third version number according to the version sequence rule to obtain a fourth version number, and determining the updated version number of the second module as the fourth version number.
Further, a code version management table is preset, the management table comprises a plurality of version records, each version record comprises first information corresponding to a first module, second information corresponding to a second module and third information corresponding to a system, and the management method further comprises: a version record is newly built in the management table; when the first module is updated and the second module is not updated, setting the first information and the third information as a third version number and setting the second information as a second version number in the version record; when the first module and the second module are updated at the same time and the first module and the second module meet the preset association relation, setting the first information, the second information and the third information as third version numbers in the version records; when the first module and the second module are updated simultaneously and the first module and the second module do not meet the preset association relation, setting the first information as a third version number and setting the second information and the third information as a fourth version number in the version record.
Further, before the step of determining the version number with the newer version order in the first version number and the second version number, the management method includes: receiving a code block to be stored, determining a module corresponding to the code block to be stored in a system, and determining that the first module is updated when the module corresponding to the code block to be stored is the first module; the step of determining the version number with the newer version order in the first version number and the second version number comprises the following steps: before a step of newly establishing a version record in the management table, obtaining third information in the last version record in the management table to obtain a version number with a newer version sequence in the first version number and the second version number; after the step of determining that the updated version number of the first module is the third version number, the management method further includes: and naming the code blocks to be stored according to the third version number, and storing the code blocks to be stored into a code warehouse corresponding to the first module.
Further, the step of determining a module corresponding to the code block to be stored in the system comprises: providing a module selection interface; obtaining a module selection operation received by a module selection interface; a module selection operation is determined for the selected module in the system.
Further, the step of determining a module corresponding to the code block to be stored in the system comprises: acquiring identification information of a code block to be stored; the module with the identification information is found in the system.
On the other hand, in order to achieve the above purpose, the present invention provides a device for managing code versions of a multi-module system.
The multi-module system comprises at least a first module and a second module, the management device comprising: the first determining module is used for determining a version number with a newer version sequence from a first version number and a second version number when the first module is updated, wherein the first version number is the current version number of the first module, and the second version number is the current version number of the second module; the updating module is used for updating the version numbers with newer version sequences according to the version sequence rule to obtain a third version number; and the second determining module is used for determining that the updated version number of the first module is a third version number.
In a further aspect, the present invention also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above method when executing the computer program.
In a further aspect, the present invention provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above method.
The method, the device and the computer equipment for managing the multi-module system code version provided by the invention are used for updating the version number corresponding to the module when the module in the system code development process needs to be updated for the system comprising a plurality of modules. When the version numbers are updated, the version number with the latest version sequence is determined from the current version numbers of all the modules, then the version numbers are updated according to a version sequence updating rule on the basis of the version numbers with the latest version sequence, and the obtained updated version numbers are used as version numbers of the updated modules.
Drawings
FIG. 1 is a flowchart of a method for managing multi-module system code versions according to a first embodiment of the present invention;
FIG. 2 is a flowchart of a method for managing multi-module system code versions according to a second embodiment of the present invention;
FIG. 3 is a flowchart of a method for managing multi-module system code versions according to a third embodiment of the present invention;
FIG. 4 is a flowchart of a method for managing multi-module system code versions according to a fourth embodiment of the present invention;
FIG. 5 is a flowchart of a method for managing multi-module system code versions according to a fifth embodiment of the present invention;
FIG. 6 is a flowchart of a method for managing multi-module system code versions according to a sixth embodiment of the present invention;
FIG. 7 is a block diagram of a managing apparatus for multi-module system code versions according to a seventh embodiment of the present invention;
fig. 8 is a hardware configuration diagram of a computer device according to an eighth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
In the management method of the multi-module system code version, the system code version management comprising at least two modules is aimed at, when one of the modules is updated, the version number with the latest version sequence is found out from the current version numbers of all the modules, then the version number with the latest version sequence is updated according to the version sequence rule, the updated version number is obtained, the updated version number is used as the version number of the updated module, each module of the system is provided with a version number, the modules can be managed independently, meanwhile, the version numbers of the modules are related to each other, when any one module is updated, the system is updated according to the same version sequence rule on the basis of the version number with the latest version sequence, for example, when the system needs to be rolled back to a node where a certain version number is located, the version number of the system is rolled back, the other modules can be obtained without being higher than the version number and the version number closest to the version number of the version number, and all the system nodes where the version number is located can be obtained.
Embodiments of a method, an apparatus, and a computer device for managing multi-module system code versions provided in the present invention will be described in detail below.
Example 1
In an embodiment, a system including a first module and a second module is described as an example, where the system is not limited to include two modules, and "first" and "second" in the first module and the second module are only used to distinguish the two modules, and do not constitute a limitation in order. By the method, the first module and the second module respectively have respective version numbers, so that the first module and the second module can be respectively and independently managed, meanwhile, only the modules are updated, the modules can obtain new version numbers, the new version numbers are updated on the basis of the current latest version numbers of all the modules, the version numbers of the first module and the second module have an association relationship, and system rollback is facilitated. Specifically, fig. 1 is a flowchart of a method for managing multi-module system code versions according to an embodiment of the present invention, as shown in fig. 1, where the method for managing multi-module system code versions includes the following steps S101 to S103.
Step S101: when the first module is updated, the version numbers with newer version sequences in the first version number and the second version number are determined.
The initial version numbers of the modules in the system can be set to be uniform initial version numbers. When the modules in the system are updated, the version numbers of the modules are updated correspondingly, in this embodiment, the updated version numbers of the modules and the corresponding updated code blocks are recorded, optionally, a management table is set to record the updated version numbers each time, and a code warehouse is set to store the updated code blocks for different modules respectively.
In this embodiment, the first version number is the current version number of the first module and the second version number is the current version number of the second module.
Optionally, in an embodiment, when the first module is updated, current version numbers of the first module and the second module are obtained, that is, latest version numbers existing in the first module and the second module up to now are obtained and are respectively defined as a first version number and a second version number in sequence, and then, according to a version sequence rule, version sequence newer version numbers in the first version number and the second version number are determined.
Wherein the version order rules may be predefined, e.g., the version number includes a single natural number, the larger the number, the newer the version; as another example, the version number includes a single letter, with the version being newer the more recent the letter is in order from a to z; for another example, the version number includes at least two pieces of sub information, each piece of sub information corresponds to one update level, and the sub information corresponding to the same update level may be a single natural number or a single letter, where when determining the order of the version number, the version number is updated from the highest update level, and if the number (or letter) of the same update level is the same, the next update level is continuously compared. The above only exemplifies a part of the version sequence rule, and the present application is not limited to this, and other version sequence rules may be adopted.
For a determined version order rule, each module of the system updates the version number using the version order rule. In the step, the version sequence rule is adopted, and the first version number and the second version number are compared to determine the version number with newer version sequence.
Step S102: and updating the version numbers with newer version sequences according to the version sequence rule to obtain a third version number.
For example, a version number includes four pieces of sub-information, each piece of sub-information including a letter, and the initial version number is a.a.a. The first update level is the highest level, and the fourth update level is the lowest level. When any update level is updated, the updated update levels are sequentially updated, the update level higher than the updated update level is unchanged, and the update level lower than the updated update level is set as a.
And the first version number is a.a.a.c, and the second version number is a.a.b.a, and the version number with the newer version sequence in the first version number and the second version number is the second version number, namely a.a.b.a. If the first module updates the second update level, in this step, after updating the version number a.a.b.a according to the version sequence rule, a third version number a.b.a.a is obtained.
Step S103: and determining the updated version number of the first module as a third version number.
By adopting the management method of the multi-module system code version provided by the embodiment, for a system comprising a plurality of modules, when the module in the system code needs to be updated in the process of developing the system code, the version number corresponding to the module is updated. When the version numbers are updated, the version number with the latest version sequence is determined from the current version numbers of all the modules, then the version numbers are updated according to a version sequence updating rule on the basis of the version numbers with the latest version sequence, and the obtained updated version numbers are used as version numbers of the updated modules.
Example two
The second embodiment of the present invention provides a method for managing a multi-module system code version, where part of the steps of the method for managing a multi-module system code version are the same as those of the first embodiment, and the part of the steps are not described in detail in the embodiment, and reference may be made to the first embodiment. Specifically, fig. 2 is a flowchart of a method for managing multi-module system code versions according to a second embodiment of the present invention, as shown in fig. 2, where the method for managing multi-module system code versions according to the second embodiment includes the following steps S201 to S208.
Step S201: when the first module is updated, the current version number of the first module is obtained to obtain a first version number, and the current version number of the second module is obtained to obtain a second version number.
Step S202: and determining the version numbers with newer version sequences in the first version number and the second version number according to the version sequence rule.
In the method for managing multi-module system code versions provided in this embodiment, the version number includes at least two pieces of sub-information, each piece of sub-information corresponds to one update level, and different update levels may be updated simultaneously, or only a part of update levels may be updated. Optionally, a separator is set between the sub-information, that is, a sub-information is set between two adjacent separators, when the version number includes n separators, the version number includes n+1 sub-information, and the version number has n+1 update levels; optionally, the data format of the sub information is predefined, the number of the sub information included in the version number is determined according to the data format, and thus the update level included in the version number can be determined, for example, when the data format of the sub information is predefined to be a single letter and the version number includes 5 letters, it can be determined that the version number includes 5 sub information, and thus the 5 update levels included in the version number can be determined.
Step S203: an update level of the first module update is determined.
Optionally, in an embodiment, a correspondence between the update content and the update level is preset, and different update contents may correspond to different update levels, for example, when the update content is the first content, the first update level in the version number is corresponding to the first update level, so that when the first content in the first module is updated, the first update level is an update level that needs to be updated; when the updated content is the second content, the second updating level in the corresponding version number is corresponding, so that when the second content in the first module is updated, the second updating level is the updating level which needs to be updated; the update level of the first module update can be determined in the corresponding relation through the update content of the first module update; or, alternatively, after the first module is updated, the original naming of the code block includes an update identifier, where the update identifier includes an update level, and then the update level of the first module update may be determined by reading the original naming of the code block after the first module is updated.
Step S204: and acquiring the sub-information corresponding to the determined update level from version numbers with updated version sequences to obtain the sub-information to be updated.
After the update level is determined, according to the correspondence between the sub-information and the update level, the sub-information corresponding to the determined update level can be obtained from the version number with the newer version sequence. For example, the version number includes three pieces of sub-information, each of which has a digital value, the first piece of sub-information corresponds to a first update level, the second piece of sub-information corresponds to a second update level, and the third piece of sub-information corresponds to a third update level. And the version number with the newer version sequence is 2.1.3, and the determined update level is the second update level, and in the version number of 2.1.3, the sub information corresponding to the second update level is 1, namely, the sub information to be updated is 1.
Step S205: and adding a preset increment to the sub-information to be updated to obtain updated sub-information.
For example, if the preset increment is 1, when the sub-information to be updated is 1, the increment is added, and the obtained updated sub-information is 2.
Step S206: and if the sub-information to be updated is at the lowest update level, replacing the sub-information to be updated in the version numbers with the updated version sequences by using the updated sub-information to obtain a third version number.
Step S207: if the sub information to be updated is not the lowest update level, replacing the sub information to be updated in the version number with the updated sub information in version sequence, and setting all the sub information with the update level lower than that of the sub information to be updated as initial sub information to obtain a third version number.
For example, in the version number of 2.1.3, the sub information to be updated is at the middle update level, not at the lowest update level, and the initial sub information is set to 1, then the third version number is 2.2.1, that is, the middle update level is updated to 2, and the lowest update level is set to 1. When the version number is 2.1.2, the sub information to be updated is at the highest update level, not at the lowest update level, and the initial sub information is set to 1, then the third version number is 3.1.1, that is, the highest update level is updated to 3, and both the middle update level and the lowest update level are set to 1.
Step S208: and determining the updated version number of the first module as a third version number.
By adopting the management method of the multi-module system code version, provided by the embodiment, the set version number comprises a plurality of pieces of sub-information corresponding to a plurality of update levels, and the association relationship between the version numbers of each module not only is beneficial to rollback of the system, but also can show the update level of each version relative to the last version.
Example III
The third embodiment of the present invention provides a method for managing a multi-module system code version, where part of the steps of the method for managing a multi-module system code version are the same as those in the foregoing embodiment, and the part of the steps are not described in detail in the foregoing embodiment, and reference may be made to the foregoing embodiments specifically. Specifically, fig. 3 is a flowchart of a method for managing multi-module system code versions according to the third embodiment of the present invention, as shown in fig. 3, where the method for managing multi-module system code versions according to the third embodiment of the present invention includes the following steps S301 to S309.
Step S301: when the first module and the second module are updated simultaneously, information in the last version record is obtained in the management table, and a version record is newly built in the management table.
The management table of the code version is preset, and each time updating occurs in the system, a version record is formed in the management table, wherein the version record comprises a version number corresponding to each module and a version number corresponding to the whole system. In this embodiment, taking the example that the system includes a first module and a second module, the version record includes the version number of the first module, the version number of the second module, and the version number of the system. Wherein, in the management table, the version number of the first module is defined as first information, the version number of the second module is defined as second information, and the version number of the system is defined as third information.
When the module is updated, the information of the last version record is firstly obtained in the management table so as to obtain the current latest version number of each module and the current version number of the system. In this embodiment, the first module and the second module are updated at the same time.
Optionally, after reading the version record in the management table, a write operation may be performed to the management table, and a version record is newly built in the management table. Of course, the step of creating the version record in the management table may be set at any position before step S306 described below, which is not limited in the present application.
Step S302: and obtaining third information in the last version record to obtain a version number with newer version sequence in the first version number and the second version number.
When the first module and the second module are updated at the same time, the obtained first information, namely the current version number of the first module, is used as a first version number in the last version record of the management table; the obtained second information, i.e. the current version number of the second module, is used as the second version number, and since the version number of the system is updated to the highest version number of all the modules when any module is updated, in the same version record, the version number of the system, i.e. the version number with the latest version sequence in the current version numbers of all the modules. Therefore, in this step, the third information in the last version record is obtained, and the version numbers with newer version sequences in the first version number and the second version number can be obtained.
Step S303: and updating the version numbers with newer version sequences according to the version sequence rule to obtain a third version number.
Step S304: judging whether the first module and the second module meet a preset association relation or not.
Optionally, according to the service functions of the first module and the second module, presetting that the first module and the second module belong to an association relationship or an independent relationship, for example, when one of the functions of the first module and the second module is mutually dependent, the other must be updated at the same time based on the function dependence, so that the first module and the second module satisfy the association relationship; for another example, the functions of the first module and the second module are completely independent, and no intersection does not affect each other, so that the first module and the second module do not meet the association relationship.
Or, optionally, presetting a module identification pair meeting the association relation, when judging whether the first module and the second module meet the preset association relation, judging whether the module identification of the first module and the module label of the second module belong to a certain module identification pair, if so, the first module and the second module meet the preset association relation, or else, do not meet the preset association relation.
Step S305: when the first module and the second module meet the preset association relation, the updated version numbers of the first module and the updated version numbers of the second module are determined to be the third version numbers.
By this step, the updated version numbers are the same for the modules that have a dependency relationship with each other and are updated at the same time.
Step S306: in the newly-built version record, setting the first information, the second information and the third information as the third version numbers.
By the step, the version number of the system is the current highest version number of all the modules.
Step S307: and when the first module and the second module do not meet the preset association relation, updating the third version number according to the version sequence rule to obtain a fourth version number.
Through the step, for the modules which are not dependent on each other and are updated at the same time, the version number of one module is updated on the basis of the version number of the system in the management table, then the version number of the other module is further updated on the basis of the updated version number, and the like, so that all the modules obtain the updated version number.
For example, when two systems do not meet the preset association relation update, in step S303, a first update is performed to obtain a third version number as the version number updated by the first module, and then in step S307, a second update is performed to the third version number to obtain a fourth version number as the version number updated by the second module. It should be noted that, when a sentence of update level is needed to determine which sub information is updated when the version number is updated, the module determined to be the updated version number belongs to the module, for example, the update level of the first module is the basis when the update is performed first in step S303, the obtained third version number is the updated version number of the first module, the update level of the second module is the basis when the update is performed in step S307, and the obtained fourth version number is the updated version number of the second module.
Step S308: and determining the updated version number of the first module as a third version number and determining the updated version number of the second module as a fourth version number.
Step S309: in the newly-built version record, the first information is set as a third version number, and the second information and the third information are set as fourth version numbers.
By adopting the management method of the multi-module system code version, when two or more modules in the system are updated, the relation between the updated modules needs to be considered, if the updated modules are mutually dependent, namely, the preset association relation is met, the updated modules have the same updated version numbers, and if the updated modules are mutually independent, namely, the preset association relation is not met, the updated version numbers are respectively and sequentially corresponding to the updated version numbers to obtain different version numbers, so that the version numbers can represent the update processes of different code blocks for a single module, and can represent the sequential update processes of different modules for a plurality of modules, and can also represent whether the mutually dependent modules are simultaneously updated. In addition, by setting the management table and setting the version record in the management table for each update, one version record corresponds to one version of the system, and the system can be further conveniently rolled back to the node where a certain version number is located.
Example IV
The fourth embodiment of the present invention provides a method for managing a multi-module system code version, where part of the steps of the method for managing a multi-module system code version are the same as those in the foregoing embodiment, and the part of the steps are not described in detail in the foregoing embodiment, and reference may be made to the foregoing embodiments specifically. Specifically, fig. 4 is a flowchart of a method for managing multi-module system code versions according to the fourth embodiment of the present invention, as shown in fig. 4, where the method for managing multi-module system code versions according to the fourth embodiment of the present invention includes the following steps S401 to S405.
Step S401: when the first module is updated, information in the last version record is obtained in the management table, and a version record is newly built in the management table.
In the last version record, the current version number of the first module obtains a first version number, and the current version number of the second module obtains a second version number.
Step S402: and obtaining third information in the last version record to obtain a version number with newer version sequence in the first version number and the second version number.
Step S403: and updating the version numbers with newer version sequences according to the version sequence rule to obtain a third version number.
Step S404: and determining the updated version number of the first module as a third version number.
Step S405: in the newly-built version record, setting the first information and the third information as the third version numbers respectively, and setting the second information as the second version numbers.
By adopting the management method of the multi-module system code version, which is provided by the embodiment, the management table is set, and the version record is set in the management table for each update, so that one version record corresponds to one version of the system, and the system can be further conveniently rolled back to the node where a certain version number is located. Meanwhile, when a single module in the system is updated, the version number with the latest version sequence in the version numbers of the current modules can be obtained through the management table.
Example five
The fifth embodiment of the present invention provides a method for managing a multi-module system code version, where part of the steps of the method for managing a multi-module system code version are the same as those in the foregoing embodiment, and the part of the steps are not described in detail in the foregoing embodiment, and reference may be made to the foregoing embodiments specifically. The execution main body of the method can be a management platform of a multi-module system code version, the platform provides a front end for interaction with a user, a server back end for data processing and a storage device for realizing data storage, wherein the execution main body of the method is the server back end, and the storage device can be used for storing version numbers, code warehouses and the like. Specifically, fig. 5 is a flowchart of a method for managing multi-module system code versions according to a fifth embodiment of the present invention, as shown in fig. 5, where the method for managing multi-module system code versions according to the fifth embodiment includes the following steps S501 to S509.
Step S501: a code block to be stored is received.
The management platform provides a receiving channel for receiving the code blocks to be stored through the interaction front end, the system developer can upload the code blocks to be stored to the management platform based on the receiving channel, and the server back end receives the stored code blocks through the interaction front end.
Step S502: a module corresponding to a code block to be stored is determined in the system.
Optionally, in an embodiment, the management platform provides a module selection interface through the interaction front end, a plurality of option controls are set on the module selection interface, each option control corresponds to a module, and a user can select a module corresponding to the code block to be stored, so that the back end of the server can determine the module corresponding to the code block to be stored in the system according to the module selection operation received by the module selection interface.
Optionally, in another embodiment, a correspondence between the module and the identification information is preset at the rear end of the server, the code blocks to be stored uploaded by the user include the identification information, and after the code blocks to be stored are uploaded by the user, the rear end of the server obtains the identification information of the code blocks to be stored, so that the module corresponding to the code blocks to be stored can be determined in the system according to the identification information.
Step S503: and when the module corresponding to the code block to be stored is the first module, determining that the first module is updated.
Step S504: and obtaining the current version number of the first module to obtain a first version number, and obtaining the current version number of the second module to obtain a second version number.
Step S505: and determining the version numbers with newer version sequences in the first version number and the second version number according to the version sequence rule.
Step S506: and updating the version numbers with newer version sequences according to the version sequence rule to obtain a third version number.
Step S507: and determining the updated version number of the first module as a third version number.
Step S508: and naming the code blocks to be stored according to the third version number.
Step S509: and storing the code blocks to be stored into a code warehouse corresponding to the first module.
Example six
The sixth embodiment of the present invention provides a method for managing a multi-module system code version, where part of the steps of the method for managing a multi-module system code version are the same as those in the foregoing embodiment, and the part of the steps are not described in detail in this embodiment, and reference may be made to the foregoing embodiments specifically. The execution main body of the method can be a management platform of a multi-module system code version, the platform provides a front end for interaction with a user, a server back end for data processing and a storage device for realizing data storage, wherein the execution main body of the method is the server back end, and the storage device can be used for storing version numbers, code warehouses and the like. Specifically, fig. 6 is a flowchart of a method for managing multi-module system code versions according to a sixth embodiment of the present invention, as shown in fig. 6, where the method for managing multi-module system code versions according to the sixth embodiment includes the following steps S601 to S615.
Step S601: a code block to be stored is received.
Step S602: and acquiring the last version record in the management table, acquiring the version number of the system in the last version record to obtain the version number with the latest version sequence in each module of the system, and newly building a version record in the management table.
Step S603: a module corresponding to a code block to be stored is determined in the system.
Step S604: when the code blocks to be stored are single and the modules corresponding to the code blocks to be stored are the first modules, updating version numbers with newer version sequences according to the version sequence rule, and obtaining a third version number.
Wherein, when updating the version number of the newer version sequence according to the version sequence rule, the following steps can be adopted:
step S6041: an update level of a code block update of the first module is determined.
Step S6042: and acquiring the sub-information corresponding to the determined update level from version numbers with updated version sequences to obtain the sub-information to be updated.
Step S6043: and adding a preset increment to the sub-information to be updated to obtain updated sub-information.
Step S6044: and if the sub-information to be updated is at the lowest update level, replacing the sub-information to be updated in the version numbers with the updated version sequences by using the updated sub-information to obtain a third version number.
Step S6045: if the sub information to be updated is not the lowest update level, replacing the sub information to be updated in the version number with the updated sub information in version sequence, and setting all the sub information with the update level lower than that of the sub information to be updated as initial sub information to obtain a third version number.
Step S605: and determining the updated version number of the first module as a third version number.
Step S606: in the newly built version record, setting the version number of the first module and the version number of the system as the third version number respectively, and setting the version numbers of other modules to be the same as the version number in the last version record correspondingly.
Step S607: and naming the code blocks to be stored according to the third version number, and storing the code blocks to be stored into a code warehouse corresponding to the first module.
Step S608: when the number of the code blocks to be stored is two, the corresponding module of the first code block to be stored is a first module, and the corresponding module of the second code block to be stored is a second module, whether the first module and the second module meet the preset association relation is judged.
Step S609: when the first module and the second module meet the preset association relation, updating the version numbers with newer version sequences according to the version sequence rule, and obtaining a third version number.
The process of obtaining the third version number in the step S609 is the same as the process of obtaining the third version number in the step S604, and will not be described herein.
Step S610: and determining that the updated version numbers of the first module and the second module are the third version numbers.
Step S611: in the newly-built version record, the version numbers of the first module, the second module and the system are all set to be the third version number.
Step S612: and naming the first code block to be stored and the second code block to be stored according to the third version number, storing the first code block to be stored into a code warehouse corresponding to the first module, and storing the second code block to be stored into a code warehouse corresponding to the second module.
Step S613: when the first module and the second module do not meet the preset association relation, updating version numbers with newer version numbers according to the version sequence rule to obtain a third version number, updating the third version number according to the version sequence rule to obtain a fourth version number, determining the updated version number of the first module as the third version number, and determining the updated version number of the second module as the fourth version number.
The process of obtaining the third version number in the step S613 is the same as the process of obtaining the third version number in the step S604, and will not be described here again.
The step of obtaining the fourth version number in the step S613 includes:
step S6131: an update level of the code block update of the second module is determined.
Step S6132: and in the third version number, acquiring the sub-information corresponding to the determined update level to obtain the sub-information to be updated.
Step S6133: and adding a preset increment to the sub-information to be updated to obtain updated sub-information.
Step S6134: and if the sub-information to be updated is at the lowest update level, replacing the sub-information to be updated in the third version number by using the update sub-information to obtain a fourth version number.
Step S6135: if the sub information to be updated is not the lowest update level, replacing the sub information to be updated in the third version number by using the update sub information, and setting all the sub information with the update level lower than that of the sub information to be updated as initial sub information to obtain a fourth version number.
In one embodiment, the system includes three modules a, B, C, the update history of the version numbers of the code blocks of the three modules should be as follows, while the following is described for each update of the following table:
1) The ABC three modules all have interdependent updates, and commonly obtain version number 1.0.0.
2) And updating the A module to obtain the version number of 1.0.1. The BC module version number is unchanged.
3) The AB module has interdependent updates, and version number 1.1.0 is obtained. The C module version number is unchanged.
4) And updating the A module to obtain the version number 1.1.1. The BC module version number is unchanged.
5) And updating the A module to obtain the version number 1.1.2. The BC module version number is unchanged.
6) The ABC three modules all have interdependent updates, and commonly obtain version number 1.2.0.
7) And C, updating the module to obtain the version number 1.3.0. The AB module version number is unchanged.
8) And C, updating the module to obtain the version number 1.3.1. The AB module version number is unchanged.
9) The AB module has interdependent updates, and obtains version number 1.4.0. The C module version number is unchanged.
Step S614: in the newly-built version record, the first information is set as a third version number, and the second information and the third information are set as fourth version numbers.
Step S615: and naming the first code block to be stored according to the third version number, naming the second code block to be stored according to the fourth version number, storing the first code block to be stored into a code warehouse corresponding to the first module, and storing the second code block to be stored into a code warehouse corresponding to the second module.
With the multi-module system code version management method provided in this embodiment, all the version numbers of the modules are ordered, i.e. the version number allocated next must be greater than the version number with the latest version sequence in the current version number of all the modules, for example, 1.4.8 is the latest version sequence in the current version number of all the modules, and then the version number allocated next must be greater than 1.4.8. Meanwhile, the version numbers of all the modules are uniformly distributed, so that the version numbers among the modules are orderly, and version conflicts caused by the fact that different distribution distributes the same version number to different modules are prevented. And as long as the module has update, will update the version number once, can guarantee that the module has corresponding version number each time to update, when the update of a plurality of modules is interdependent, then each module can obtain the same version number, to the version number of the system, when updating each time, regard the version number that the version sequence is the latest in the current version number of all modules as the version number of the whole system. The management method of the multi-module system code version provided by the embodiment inherits the advantage of flexible authority management when the modules are managed separately, effectively controls the operation risk of non-module owners, and can independently update and release the modules without depending on other departments when the departments where the modules are located only need to update the modules, thereby improving the production efficiency. The problem that version numbers are not uniform when the modules are separately managed and the system is not beneficial to releasing appointed version codes is solved. When the system needs to release a code of a certain version, the version numbers corresponding to all the modules can be conveniently found, and the code blocks corresponding to the determined version numbers are used for deployment, so that the problem of deployment failure caused by incapability of corresponding dependence among the modules is avoided.
Example seven
Corresponding to the management method of the multi-module system code version provided by the above embodiments, the seventh embodiment of the present invention provides a management device of the multi-module system code version, and related technical features and corresponding technical effects may refer to the above embodiments, which are only briefly described. Fig. 7 is a block diagram of a management apparatus for multi-module system code version according to a seventh embodiment of the present invention, as shown in fig. 7, the apparatus includes: a first determination module 701, an update module 702, and a second determination module 703.
The multi-module system includes at least a first module and a second module. The first determining module 701 is configured to determine, when the first module is updated, a version number with a newer version sequence from a first version number and a second version number, where the first version number is a current version number of the first module, and the second version number is a current version number of the second module; the updating module 702 is configured to update version numbers with newer version sequences according to a version sequence rule, so as to obtain a third version number; and the second determining module 703 is configured to determine the updated version number of the first module as the third version number.
Optionally, in one embodiment, the version number includes at least two pieces of sub information, each piece of sub information corresponding to one update level, and the update module 702 includes a first determining unit, a first acquiring unit, a first processing unit, a first update unit, and a second update unit. The first determining unit is used for determining an updating level of the code block updating of the first module; the first acquisition unit is used for acquiring sub-information corresponding to the determined update level in version numbers with updated version sequences to obtain sub-information to be updated; the first processing unit is used for adding preset increment to the sub-information to be updated to obtain updated sub-information; the first updating unit is used for replacing the sub-information to be updated in the version number with the newer version sequence by using the updated sub-information when the sub-information to be updated is at the lowest updating level, so as to obtain a third version number; and the second updating unit is used for replacing the sub-information to be updated in the version number with the updated sub-information to be updated in the version sequence when the sub-information to be updated is not at the lowest updating level, and setting all the sub-information with the updating level lower than that of the sub-information to be updated as initial sub-information to obtain a third version number.
Optionally, in an embodiment, the management device further includes a judging module, a third determining module, and a fourth determining module, where the judging module is configured to judge whether the first module and the second module satisfy a preset association relationship when the first module and the second module are updated at the same time; the third determining module is used for determining that the version number updated by the second module is a third version number when the first module and the second module meet a preset association relation; the fourth determining module is configured to update the third version number according to a version sequence rule to obtain a fourth version number when the first module and the second module do not satisfy a preset association relationship, and determine that the updated version number of the second module is the fourth version number.
Optionally, in an embodiment, a code version management table is preset, where the management table includes a plurality of version records, each version record includes first information corresponding to the first module, second information corresponding to the second module, and third information corresponding to the system, and the management device further includes a new module, a first processing module, a second processing module, and a third processing module, where the new module is configured to newly create a version record in the management table; the first processing module is used for setting the first information and the third information as a third version number and setting the second information as a second version number in the version record when the first module is updated and the second module is not updated; the second processing module is used for setting the first information, the second information and the third information as a third version number in the version record when the first module and the second module are updated at the same time and the first module and the second module meet the preset association relation; the third processing module is configured to set the first information as a third version number and set the second information and the third information as a fourth version number in the version record when the first module and the second module are updated simultaneously and the first module and the second module do not satisfy a preset association relationship.
Optionally, in an embodiment, the management device further includes a receiving module and a fifth determining module, where the receiving module is configured to receive the code block to be stored before determining a version number with a newer version sequence in the first version number and the second version number, and the fifth determining module is configured to determine a module corresponding to the code block to be stored in the system, where when the module corresponding to the code block to be stored is a first module, determine that the first module is updated; the first determining module 701 includes a second obtaining unit, configured to obtain, before the step of newly building a version record in the management table, third information in a last version record in the management table, to obtain a version number with a newer version sequence in the first version number and the second version number; the management device further comprises a storage module, and the storage module is used for naming the code blocks to be stored according to the third version number after the step of determining that the updated version number of the first module is the third version number, and storing the code blocks to be stored into a code warehouse corresponding to the first module.
Optionally, in one embodiment, when the fifth determining module determines a module corresponding to the code block to be stored in the determining system, the specifically executing steps includes: providing a module selection interface; obtaining a module selection operation received by a module selection interface; a module selection operation is determined for the selected module in the system.
Optionally, in one embodiment, when the fifth determining module determines a module corresponding to the code block to be stored in the determining system, the specifically executing steps includes: acquiring identification information of a code block to be stored; the module with the identification information is found in the system.
Example eight
The eighth embodiment also provides a computer device, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack-mounted server, a blade server, a tower server, or a rack-mounted server (including an independent server or a server cluster formed by a plurality of servers) that can execute the program. As shown in fig. 8, the computer device 01 of the present embodiment includes at least, but is not limited to: the memory 011, the processor 012, which can be communicatively connected to each other through a system bus, as shown in fig. 8. It is noted that fig. 8 only shows a computer device 01 having a component memory 011 and a processor 012, but it is understood that not all of the illustrated components are required to be implemented, and more or fewer components may alternatively be implemented.
In this embodiment, the memory 011 (i.e., readable storage medium) includes flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, memory 011 may be an internal storage unit of computer device 01, such as a hard disk or memory of computer device 01. In other embodiments, the memory 011 may also be an external storage device of the computer device 01, such as a plug-in hard disk, smart Media Card (SMC), secure Digital (SD) Card, flash memory Card (Flash Card) or the like, which are provided on the computer device 01. Of course, the memory 011 may also include both the internal memory unit of the computer device 01 and its external memory device. In this embodiment, the memory 011 is generally used to store an operating system and various application software installed in the computer device 01, for example, program codes of a management apparatus of a multi-module system code version of embodiment seven. Further, the memory 011 can also be used for temporarily storing various types of data that have been output or are to be output.
The processor 012 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 012 is typically used to control the overall operation of the computer device 01. In this embodiment, the processor 012 is configured to execute program codes stored in the memory 011 or process data such as a management method of multi-module system code version.
Example nine
The ninth embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application store, etc., on which a computer program is stored, which when executed by a processor, performs a corresponding function. The computer readable storage medium of the present embodiment is used for storing a management device of a multi-module system code version, and when executed by a processor, implements the management method of a multi-module system code version of the first embodiment.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (9)
1. A method for managing code versions of a multi-module system, wherein the system includes at least a first module and a second module, the method comprising:
when the first module is updated, determining a version number with a newer version sequence in a first version number and a second version number, wherein the first version number is the current version number of the first module, and the second version number is the current version number of the second module;
updating the version numbers with the newer version sequences according to the version sequence rules to obtain a third version number; and
determining the updated version number of the first module as the third version number,
when the first module and the second module are updated at the same time, judging whether the first module and the second module meet a preset association relation or not;
when the first module and the second module meet a preset association relation, determining the updated version number of the second module as the third version number;
and when the first module and the second module do not meet a preset association relation, updating the third version number according to the version sequence rule to obtain a fourth version number, and determining the updated version number of the second module as the fourth version number.
2. The method for managing multi-module system code version according to claim 1, wherein the version number includes at least two pieces of sub-information, each piece of sub-information corresponds to an update level, and the step of updating the version number with the newer version number in version order according to a version order rule to obtain a third version number includes:
determining an update level of a code block update of the first module;
acquiring sub-information corresponding to the determined update level from version numbers with newer version sequences to obtain sub-information to be updated;
adding a preset increment to the sub-information to be updated to obtain updated sub-information;
if the sub-information to be updated is at the lowest update level, replacing the sub-information to be updated in the version number with the newer version sequence by using the update sub-information to obtain the third version number;
and if the sub-information to be updated is not at the lowest update level, replacing the sub-information to be updated in the version number with the updated version sequence by using the update sub-information, and setting all the sub-information with the update level lower than that of the sub-information to be updated as initial sub-information to obtain the third version number.
3. The method for managing code versions of a multi-module system according to claim 1, wherein a code version management table is preset, the management table includes a plurality of version records, each version record includes first information corresponding to the first module, second information corresponding to the second module, and third information corresponding to the system, and the method for managing code versions further includes:
a version record is newly built in the management table;
when the first module is updated and the second module is not updated, setting the first information and the third information as the third version number and setting the second information as the second version number in the version record;
when the first module and the second module are updated at the same time and the first module and the second module meet a preset association relationship, setting the first information, the second information and the third information as the third version number in the version record;
when the first module and the second module are updated at the same time and the first module and the second module do not meet a preset association relationship, setting the first information as the third version number and setting the second information and the third information as the fourth version number in the version record.
4. The method for managing multi-module system code versions according to claim 3, wherein,
before the step of determining the version number of which the version order is newer in the first version number and the second version number, the management method includes: receiving a code block to be stored, and determining a module corresponding to the code block to be stored in the system, wherein when the module corresponding to the code block to be stored is the first module, the first module is determined to be updated;
the step of determining the version number with the newer version order in the first version number and the second version number comprises the following steps: before a step of creating a version record in the management table, acquiring third information in the last version record in the management table to obtain a version number with a newer version sequence in the first version number and the second version number;
after the step of determining the updated version number of the first module as the third version number, the management method further includes: and naming the code blocks to be stored according to the third version number, and storing the code blocks to be stored into a code warehouse corresponding to the first module.
5. The method of claim 4, wherein the step of determining the module corresponding to the code block to be stored in the system comprises:
Providing a module selection interface;
acquiring module selection operation received by the module selection interface;
the module selected by the module selection operation is determined in the system.
6. The method of claim 4, wherein the step of determining the module corresponding to the code block to be stored in the system comprises:
acquiring the identification information of the code block to be stored;
and searching a module with the identification information in the system.
7. A multi-module system code version management device, wherein the system comprises at least a first module and a second module, the management device comprising:
the first determining module is used for determining a version number with a newer version sequence from a first version number and a second version number when the first module is updated, wherein the first version number is the current version number of the first module, and the second version number is the current version number of the second module;
the updating module is used for updating the version numbers with the newer version sequences according to the version sequence rule to obtain a third version number;
the second determining module is used for determining that the updated version number of the first module is the third version number;
The judging module is used for judging whether the first module and the second module meet a preset association relation or not when the first module and the second module are updated at the same time;
a third determining module, configured to determine, when the first module and the second module satisfy the preset association relationship, that the version number updated by the second module is the third version number; and
and the fourth determining module is used for updating the third version number according to the version sequence rule to obtain a fourth version number when the first module and the second module do not meet the preset association relation, and determining the updated version number of the second module as the fourth version number.
8. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 6 when the computer program is executed by the processor.
9. A computer-readable storage medium having stored thereon a computer program, characterized by: which computer program, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010142301.3A CN111399898B (en) | 2020-03-04 | 2020-03-04 | Method and device for managing multi-module system code version and computer equipment |
| PCT/CN2020/118544 WO2021174830A1 (en) | 2020-03-04 | 2020-09-28 | Management method and apparatus for code versions of multi-module system, and computer device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010142301.3A CN111399898B (en) | 2020-03-04 | 2020-03-04 | Method and device for managing multi-module system code version and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111399898A CN111399898A (en) | 2020-07-10 |
| CN111399898B true CN111399898B (en) | 2023-09-05 |
Family
ID=71436024
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010142301.3A Active CN111399898B (en) | 2020-03-04 | 2020-03-04 | Method and device for managing multi-module system code version and computer equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111399898B (en) |
| WO (1) | WO2021174830A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111399898B (en) * | 2020-03-04 | 2023-09-05 | 平安科技（深圳）有限公司 | Method and device for managing multi-module system code version and computer equipment |
| CN112667283A (en) * | 2020-12-30 | 2021-04-16 | 深圳证券交易所 | Frame data reference method and device and computer readable storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5881292A (en) * | 1996-09-26 | 1999-03-09 | Microsoft Corporation | Dynamic versioning system for multiple users of multi-module software system |
| JP2011060232A (en) * | 2009-09-14 | 2011-03-24 | Ricoh Co Ltd | Management device, management system, management method, and management program |
| US8762980B1 (en) * | 2010-09-09 | 2014-06-24 | Symantec Corporation | Rolling incremental updates |
| CN107193616A (en) * | 2017-06-30 | 2017-09-22 | 广州云移信息科技有限公司 | A kind of application program updating method and terminal |
| CN107678776A (en) * | 2017-08-09 | 2018-02-09 | 上海壹账通金融科技有限公司 | Multimode version dependence construction method, device, server and storage medium |
| CN108768726A (en) * | 2018-05-30 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of upgrade method and device of server cluster |
| CN109445839A (en) * | 2018-09-25 | 2019-03-08 | 平安普惠企业管理有限公司 | A kind of module management packet dissemination method, device and terminal device |
| CN109783135A (en) * | 2019-01-30 | 2019-05-21 | 深圳琥珀虚颜智能科技有限公司 | Multimode software version management system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW518513B (en) * | 2001-03-28 | 2003-01-21 | Synq Technology Inc | System and method to update an executing application software by modular way |
| US20090144703A1 (en) * | 2007-11-30 | 2009-06-04 | Vallieswaran Vairavan | Method and system for versioning a software system |
| CN104820676B (en) * | 2015-04-14 | 2018-06-19 | 天脉聚源（北京）教育科技有限公司 | A kind of method and device for judging version number's size |
| CN110515637A (en) * | 2019-07-12 | 2019-11-29 | 湖南新云网科技有限公司 | A kind of programme upgrade method, system and terminal device |
| CN111399898B (en) * | 2020-03-04 | 2023-09-05 | 平安科技（深圳）有限公司 | Method and device for managing multi-module system code version and computer equipment |
-
2020
- 2020-03-04 CN CN202010142301.3A patent/CN111399898B/en active Active
- 2020-09-28 WO PCT/CN2020/118544 patent/WO2021174830A1/en active Application Filing
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5881292A (en) * | 1996-09-26 | 1999-03-09 | Microsoft Corporation | Dynamic versioning system for multiple users of multi-module software system |
| JP2011060232A (en) * | 2009-09-14 | 2011-03-24 | Ricoh Co Ltd | Management device, management system, management method, and management program |
| US8762980B1 (en) * | 2010-09-09 | 2014-06-24 | Symantec Corporation | Rolling incremental updates |
| CN107193616A (en) * | 2017-06-30 | 2017-09-22 | 广州云移信息科技有限公司 | A kind of application program updating method and terminal |
| CN107678776A (en) * | 2017-08-09 | 2018-02-09 | 上海壹账通金融科技有限公司 | Multimode version dependence construction method, device, server and storage medium |
| CN108768726A (en) * | 2018-05-30 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of upgrade method and device of server cluster |
| CN109445839A (en) * | 2018-09-25 | 2019-03-08 | 平安普惠企业管理有限公司 | A kind of module management packet dissemination method, device and terminal device |
| CN109783135A (en) * | 2019-01-30 | 2019-05-21 | 深圳琥珀虚颜智能科技有限公司 | Multimode software version management system |
Non-Patent Citations (1)
| Title |
|---|
| 基于多版本服务切换的软件动态更新系统的设计与实现;杜耕;《中国优秀硕士学位论文全文数据库》(第2011年10期);I138-242 * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021174830A1 (en) | 2021-09-10 |
| CN111399898A (en) | 2020-07-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8499296B2 (en) | Multi-branch management for updating software | |
| CN111399898B (en) | Method and device for managing multi-module system code version and computer equipment | |
| CN106031127B (en) | Method and apparatus for management of applications | |
| US8060794B2 (en) | NAND flash memory and method for managing data thereof | |
| CN109804361A (en) | File synchronization in computing system | |
| CN102224492A (en) | Data maintenance system | |
| CN115470191A (en) | Database updating system, method and corresponding computer equipment and storage medium | |
| CN110363330B (en) | Path planning method and device, computer equipment and readable storage medium | |
| CN111488483B (en) | Method, device, terminal and non-transitory computer readable storage medium for updating a library | |
| CN113656098A (en) | Configuration acquisition method and system | |
| CN112579608A (en) | Case data query method, system, device and computer readable storage medium | |
| CN111913777A (en) | Information processing method, information processing device, electronic equipment and storage medium | |
| CN113535206B (en) | Multi-version code upgrading method and system | |
| CN114610959B (en) | Data processing method, device, equipment and storage medium | |
| US9652766B1 (en) | Managing data stored in memory locations having size limitations | |
| US8423989B2 (en) | Software parameter management | |
| CN115756955A (en) | Data backup and data recovery method and device and computer equipment | |
| CN114860362A (en) | Interface updating method and device | |
| CN110704573B (en) | Catalog storage method, catalog storage device, computer equipment and storage medium | |
| US20170090820A1 (en) | Method and device for operating a many-core system | |
| CN108363614B (en) | Application service module management method and device and server | |
| CN112631648A (en) | Service configuration method and device, electronic equipment and storage medium | |
| CN113342647A (en) | Test data generation method and device | |
| CN112527780A (en) | Redis cluster creating and managing method, system, computer device and storage medium | |
| CN117591495B (en) | Data storage method and system for nuclear power historical data migration |
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 |