CN111399898A

CN111399898A - Management method and device for multi-module system code version and computer equipment

Info

Publication number: CN111399898A
Application number: CN202010142301.3A
Authority: CN
Inventors: 皮浩
Original assignee: Ping An Technology Shenzhen Co Ltd
Current assignee: Ping An Technology Shenzhen Co Ltd
Priority date: 2020-03-04
Filing date: 2020-03-04
Publication date: 2020-07-10
Anticipated expiration: 2040-03-04
Also published as: CN111399898B; WO2021174830A1

Abstract

The invention provides a method and a device for managing multi-module system code versions and computer equipment. The system at least comprises a first module and a second module, and the management method comprises the following steps: 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 number with the newer version sequence 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 multi-module system code version, so that the management among the modules can be independent and can be conveniently rolled back.

Description

Management method and device for multi-module system code version and computer equipment

Technical Field

The invention relates to the technical field of data processing, in particular to a method and a device for managing a multi-module system code version and computer equipment.

Background

As the integration of the functions of the computer software system becomes larger, the computer software system in the prior art usually comprises a plurality of functional modules. When a system is composed of a plurality of functional modules, the code versions of the modules need to be managed, so that the system can release a code of a certain specified version at any time. Currently, there are two main methods for code version management of a multi-module system:

one is centralized. Namely, the code blocks of all modules are placed in the same code warehouse, and the code blocks of the modules share one version number and are packaged and issued together. When the system scale increases, the code blocks of the modules increase, and different modules belong to different departments respectively, the centralized management mode can increase the coupling between the code blocks. Since the code blocks of all modules are in the same repository, each change of a code block of a module affects the unified repository. 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 code blocks of different departments cannot be separately managed, the exposure ranges of codes of different modules cannot be effectively controlled, and the risk of operation management is increased.

The other is a separated type. The modules are divided into different warehouses for management, the version numbers are independent, the authority problem of centralized management and the coupling problem among the code blocks are solved, however, the version numbers among the code blocks of the modules do not have an association relation, and the whole system cannot be rolled back to a certain historical function point.

Therefore, a method, an apparatus and a computer device for managing multi-module system code versions are provided to better manage multi-module system code versions, so that management among modules can be independent and conveniently rolled back, and a technical problem to be solved in the art is urgently needed.

Disclosure of Invention

The invention aims to provide a method and a device for managing a code version of a multi-module system and computer equipment, which are used for solving the technical problem that the code version management method of the separated multi-module system in the prior art is inconvenient for rolling back the whole system to the same historical node.

In one aspect, 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 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 number with the newer version sequence 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 with a newer version sequence according to the version sequence rule to obtain the third version number includes: determining an update level of a code block update of a first module; acquiring sub-information corresponding to the determined updating level from the version number with the newer version sequence 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 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; and 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 newer 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 the 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 simultaneously, judging whether the first module and the second module meet a preset incidence relation or not; when the first module and the second module meet the preset incidence relation, determining the updated version number of the second module as a third version number; and when the first module and the second module do not meet the preset incidence 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 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 method further includes: creating a version record 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 simultaneously and the first module and the second module meet a preset incidence relation, setting the first information, the second information and the third information to be a third version number in the version record; and 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 relationship, 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 sequence 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 the 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 sequence in the first version number and the second version number comprises the following steps: before the step of creating a new 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 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 to a code warehouse corresponding to the first module.

Further, the step of determining in the system the module corresponding to the code block to be stored comprises: providing a module selection interface; acquiring module selection operation received by a module selection interface; the determination module selects the module selected for operation in the system.

Further, the step of determining in the system the module corresponding to the code block to be stored comprises: acquiring identification information of a code block to be stored; a module having identification information is located in the system.

In another aspect, the present invention provides a device for managing code versions of a multi-module system.

The multi-module system includes at least a first module and a second module, and the management apparatus includes: the first determining module is used for determining a version number with a newer version sequence in 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 number with the newer version sequence according to the version sequence rule to obtain a third version number; and the second determining module is used for determining the updated version number of the first module as a third version number.

In another aspect, to achieve the above object, the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and running on the processor, and when the processor executes the computer program, the steps of the method are implemented.

In a further aspect, to achieve the above object, the present invention further 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.

According to the management method, device and computer equipment of the multi-module system code version, provided by the invention, for a system comprising a plurality of modules, in the process of system code development, when the modules in the system need to be updated, the version numbers corresponding to the modules are updated. Wherein, when updating the version number, determining the version number with the latest version sequence from the current version numbers of all modules, then updating according to the version sequence updating rule on the basis of the version number with the latest version sequence, and the obtained updated version number is used as the version number of the updating module, thereby showing that each module of the system has respective version number, each module can be managed independently, simultaneously, the version number of each module is correlated, the version number obtained after any module is updated is obtained by updating on the basis of the version number with the latest version sequence, therefore, when the system needs to roll back to a certain node, for example, when the system needs to roll back to a node where a certain module is a certain version number, the version number can be used as a reference, and the version number of other modules which is not higher than the version number and is closest to the version number is obtained, the versions of all modules of the system at the rollback node can be obtained, and rollback of the system is facilitated.

Drawings

Fig. 1 is a flowchart of a method for managing code versions of a multi-module system according to an embodiment of the present invention;

fig. 2 is a flowchart of a method for managing code versions of a multi-module system according to a second embodiment of the present invention;

fig. 3 is a flowchart of a method for managing code versions of a multi-module system according to a third embodiment of the present invention;

fig. 4 is a flowchart of a method for managing code versions of a multi-module system according to a fourth embodiment of the present invention;

fig. 5 is a flowchart of a method for managing code versions of a multi-module system according to a fifth embodiment of the present invention;

fig. 6 is a flowchart of a method for managing code versions of a multi-module system according to a sixth embodiment of the present invention;

fig. 7 is a block diagram of a management 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

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The invention provides a management method, a device and a computer device of a multi-module system code version, aiming at the management of the system code version comprising at least two modules, when one module 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 a version sequence rule to obtain the updated version number, the updated version number is used as the version number of an updating module, each module of the system respectively has the version number, each module can be managed independently, simultaneously, the version numbers of each module are mutually associated, when any module is updated, the updating is carried out according to the same version sequence rule on the basis of the version number with the latest version sequence, so that when the system needs to roll back to a certain node, for example, when a module in the system is a node where a version number is located, all modules in the system can be obtained by taking the version number as a reference and obtaining the version which is not higher than the version number and is closest to the version number of other modules, so that the system can conveniently roll back.

Embodiments of a method, an apparatus, and a computer device for managing versions of multi-module system code provided by the present invention will be described in detail below.

Example one

In the embodiment, the system includes a first module and a second module as an example, it should be noted that the system is not limited to include two modules, and a "first" and a "second" in the first module and the second module are only used for distinguishing the two modules, and do not constitute a limitation on an 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, the module can obtain a new version number only when the module is updated, and the new version number is updated on the basis of the current latest version number of all the modules, so that the version numbers of the first module and the second module have an association relationship, and the system rollback is facilitated. Specifically, fig. 1 is a flowchart of a management method for a multi-module system code version according to an embodiment of the present invention, and as shown in fig. 1, the management method for a multi-module system code version according to the embodiment includes steps S101 to S103 as follows.

Step S101: and when the first module is updated, determining the version number with the newer version sequence in the first version number and the second version number.

The initial version number of each module in the system can be set to be a uniform initial version number. In this embodiment, the updated version number of the module and the corresponding updated code block are recorded, optionally, a management table is set to record the version number after each update, and a code warehouse is respectively set to store the updated code block for different modules.

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, the current version numbers of the first module and the second module, that is, the latest version numbers of the first module and the second module are obtained and defined as the first version number and the second version number, respectively, in turn, and then, according to the version order rule, the version number with the newer version order in the first version number and the second version number is determined.

Wherein, the version order rule can be predefined, for example, the version number comprises a single natural number, and the larger the number, the newer the version; for another example, the version number includes a single letter, and the later the letter is, the newer the version; for another example, the version number includes at least two pieces of sub information, each piece of sub information corresponds to an update level, the piece of sub information corresponding to the same update level may be a single natural number or a single letter, wherein when the high-low order of the version number is determined, the comparison is performed from the highest update level, the larger the number (or the later the letter) of the same update level is, the newer the version is, and if the number (or the letter) of the same update level is the same, the comparison is continued for the next update level. Note that, although only some of the version order rules have been described above, the present application is not limited to this, and other version order rules may be used.

For a certain version order rule, each module of the system updates the version number by using the version order rule. In this step, the first version number and the second version number are compared by using the version order rule, and a version number with a newer version order is determined.

Step S102: and updating the version number with the newer version sequence 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 includes one letter, and the initial version number is a.a.a.a.a. From left to right, the first to fourth update levels are respectively corresponded, wherein 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 updated in sequence, the update level higher than the updated update level is not changed, and the update levels lower than the updated update level are all set as a.

The first version number is a.a.a.c, 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 is updated to the second update level, in this step, the version number a.a.b.a is updated according to the version sequence rule, and then the 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, in the process of system code development, when the module needs to be updated, the version number corresponding to the module is updated. Wherein, when updating the version number, determining the version number with the latest version sequence from the current version numbers of all modules, then updating according to the version sequence updating rule on the basis of the version number with the latest version sequence, and the obtained updated version number is used as the version number of the updating module, thereby showing that each module of the system has respective version number, each module can be managed independently, simultaneously, the version number of each module is correlated, the version number obtained after any module is updated is obtained by updating on the basis of the version number with the latest version sequence, therefore, when the system needs to roll back to a certain node, for example, when the system needs to roll back to a node where a certain module is a certain version number, the version number can be used as a reference, and the version number of other modules which is not higher than the version number and is closest to the version number is obtained, the versions of all modules of the system at the rollback node can be obtained, and rollback of the system is facilitated.

Example two

A second embodiment of the present invention provides a method for preferentially managing a multi-module system code version, where some steps of the method for managing a multi-module system code version are the same as those in the first embodiment, and are not described in detail in this embodiment, and reference may be made to the first embodiment specifically. Specifically, fig. 2 is a flowchart of a management method for multi-module system code versions according to a second embodiment of the present invention, and as shown in fig. 2, the management method for multi-module system code versions according to the second embodiment includes steps S201 to S208 as follows.

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 number with the newer version sequence in the first version number and the second version number according to the version sequence rule.

In the method for managing a multi-module system code version 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 the update levels may be updated. Optionally, a separator is arranged between the pieces of sub information, that is, one piece of sub information is arranged between two adjacent separators, and when the version number includes n separators, the version number includes n +1 pieces of sub information, and the version number has n +1 update levels; optionally, the data format of the predefined sub information determines the number of sub information included in the version number according to the data format, and further determines the update level included in the version number, for example, when the data format of the predefined sub information is a single letter, and the version number includes 5 letters, it may be determined that the version number includes 5 sub information, and further, it may be determined that the version number includes 5 update levels.

Step S203: an update level of the first module update is determined.

Optionally, in an embodiment, a corresponding relationship 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 update content corresponds to the first update level in the version number, so that when the first content in the first module is updated, the first update level is the update level that needs to be updated; when the updated content is the second content, the second update level in the version number is corresponding, so that when the second content in the first module is updated, the second update level is the update level needing to be updated; determining the updating level updated by the first module in the corresponding relation according to the updating content updated by the first module; or, optionally, after the first module is updated, the original name of the code block includes an update flag, where the update flag includes an update level, and the update level updated by the first module can be determined by reading the original name of the code block after the first module is updated.

Step S204: and acquiring sub information corresponding to the determined updating level in the version number with the newer version sequence to obtain the sub information to be updated.

After the update level is determined, according to the corresponding relationship between the sub information and the update level, the sub information corresponding to the determined update level can be obtained in 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, a first bit of the sub information corresponds to a first update level, a second bit of the sub information corresponds to a second update level, and a third bit of the sub information corresponds to a third update level. If the version number of the version sequence is newer is 2.1.3, and the determined update level is the second update level, the sub information corresponding to the second update level is 1 in the version number of 2.1.3, that is, the sub information to be updated is 1.

Step S205: and adding a preset increment to the sub-information to be updated to obtain the updated sub-information.

For example, if the preset increment is 1, and the sub information to be updated is 1, the update sub information obtained after adding the preset increment is 2.

Step S206: and if the sub information to be updated is 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.

Step S207: and 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 newer 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 the initial sub information to obtain a third version number.

For example, if the version number is 2.1.3, the sub information to be updated is the middle update level, but not the lowest update level, and the initial sub information is set to 1, 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 the highest update level, but not the lowest update level, and the initial sub information is set to 1, 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 incidence relation among the version numbers of the modules not only can be favorable for the rollback of the system, but also can embody the update level of each version relative to the previous version.

EXAMPLE III

A third embodiment of the present invention provides a method for preferentially managing a multi-module system code version, where some steps of the method for managing a multi-module system code version are the same as those in the foregoing embodiments, and details of the steps are not repeated in this embodiment, and reference may be made to the foregoing embodiments specifically. Specifically, fig. 3 is a flowchart of a method for managing versions of a multi-module system code according to a third embodiment of the present invention, and as shown in fig. 3, the method for managing versions of a multi-module system code according to the third embodiment includes steps S301 to S309 as follows.

Step S301: and when the first module and the second module are updated simultaneously, acquiring the information in the last version record in the management table, and establishing a new version record in the management table.

The management table of the preset code version forms a version record in the management table every time when the system is updated, and 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 the first module and the 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. 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 module update occurs, the last version record information is first obtained from the management table to obtain the latest version number currently existing in 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 as an example.

Alternatively, after reading the version record in the management table, a write operation may be performed on the management table, and a new version record may be created in the management table. Of course, the step of creating a new version record in the management table may be disposed at any position before step S306 described below, and the present application is not limited thereto.

Step S302: and acquiring third information in the last version record to obtain a version number with a newer version sequence in the first version number and the second version number.

When the first module and the second module are updated simultaneously, the first information, namely the current version number of the first module, is acquired in the last version record of the management table and is used as a first version number; the obtained second information, that is, 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 modules when any module is updated, the version number of the system is also the latest version number in the sequence of the current version numbers of all modules in the same version record. Therefore, in this step, the third information in the last version record is obtained, and the version number with the newer version sequence in the first version number and the second version number can be obtained.

Step S303: and updating the version number with the newer version sequence according to the version sequence rule to obtain a third version number.

Step S304: and judging whether the first module and the second module meet a preset incidence relation.

Optionally, according to the service functions of the first module and the second module, an association relationship or an independent relationship between the first module and the second module is preset, for example, functions of the first module and the second module are interdependent, when one of the functions is updated, the other needs to be updated simultaneously based on the function dependency, and then 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 from each other, and there is no mutual influence between the intersections, so that the first module and the second module do not satisfy the association relationship.

Or, optionally, a pair of module identifiers satisfying the association relationship is preset, and when it is determined whether the first module and the second module satisfy the preset association relationship, it is determined whether the module identifier of the first module and the module label of the second module belong to a certain pair of module identifiers, if so, the first module and the second module satisfy the preset association relationship, otherwise, the first module and the second module do not satisfy the preset association relationship.

Step S305: and when the first module and the second module meet the preset incidence relation, determining that the updated version numbers of the first module and the second module are the third version number.

With this step, the updated version numbers are the same for modules that have a dependency relationship with each other and are updated at the same time.

Step S306: and in the newly-created version record, setting the first information, the second information and the third information to be a third version number.

Through the step, the version number of the system is the current highest version number of all modules.

Step S307: and when the first module and the second module do not meet the preset incidence 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 independent from each other and updated simultaneously, the modules are updated on the basis of the version number of the system in the management table to obtain the updated version number of one module, then the modules are further updated on the basis of the updated version number to obtain the updated version number of the other module, and the like, so that all the modules obtain the updated version numbers.

For example, when two of the systems do not satisfy the preset association relationship, in step S303, a first update is performed to obtain a third version number as the updated version number of 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 updated version number of the second module. It should be noted that, when the version number needs an update level to determine which sub-information is updated when updating the version number, it is determined that the module at the update level is the module to which the updated version number belongs when updating, for example, if the update level of the first module is used when updating in step S303, the obtained third version number is the updated version number of the first module, and if the update level of the second module is used when updating in step S307, 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: and in the newly-created version record, setting the first information as a third version number, and setting the second information and the third information as a fourth version number.

By adopting the management method for the multi-module system code version provided by the embodiment, when two or more modules in the system are updated, the relationship between the updated modules needs to be considered, if the updated modules are mutually dependent, namely the preset association relationship is satisfied, the updated modules have the same updated version number, and if the updated modules are mutually independent, namely the preset association relationship is not satisfied, the updated version numbers respectively correspond to the updated version numbers in sequence to obtain different version numbers. In addition, by setting the management table and setting the version records in the management table for each update, one version record corresponds to one system version, and the system can be further conveniently rolled back to a node where a certain version number is located.

Example four

A fourth embodiment of the present invention provides a method for preferentially managing a multi-module system code version, where some steps of the method for managing a multi-module system code version are the same as those in the foregoing embodiments, and details of the steps are not repeated in this embodiment, and reference may be made to the foregoing embodiments specifically. Specifically, fig. 4 is a flowchart of a management method for a multi-module system code version according to a fourth embodiment of the present invention, and as shown in fig. 4, the management method for a multi-module system code version according to the fourth embodiment includes steps S401 to S405 as follows.

Step S401: and when the first module is updated, acquiring the information in the last version record in the management table, and newly building a version record 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 acquiring third information in the last version record to obtain a version number with a newer version sequence in the first version number and the second version number.

Step S403: and updating the version number with the newer version sequence 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: and in the newly-created version record, setting the first information and the third information as a third version number respectively, and setting the second information as a second version number.

By adopting the management method for the multi-module system code version 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 system version, and the system can be further conveniently rolled back to a 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 order among the version numbers of the current respective modules can be obtained through the management table.

EXAMPLE five

A fifth embodiment of the present invention provides a method for preferentially managing a multi-module system code version, where some steps of the method for managing a multi-module system code version are the same as those in the foregoing embodiments, and details of the steps are not repeated 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 interacting with a user, a server back end processing data and a storage device 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 management method for a multi-module system code version according to a fifth embodiment of the present invention, and as shown in fig. 5, the management method for a multi-module system code version according to the fifth embodiment includes steps S501 to S509 as follows.

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 interactive front end, a system developer can upload the code blocks to be stored to the management platform based on the receiving channel, and the server rear end receives the stored code blocks through the interactive front end.

Step S502: a module corresponding to a block of code to be stored is determined in the system.

Optionally, in an embodiment, the management platform provides a module selection interface through the interactive front end, a plurality of option controls are set on the module selection interface, each option control corresponds to one 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, the server back end presets a corresponding relationship between the module and the identification information, 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 server back end 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 acquiring the current version number of the first module to obtain a first version number, and acquiring the current version number of the second module to obtain a second version number.

Step S505: and determining the version number with the newer version sequence in the first version number and the second version number according to the version sequence rule.

Step S506: and updating the version number with the newer version sequence 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 block to be stored according to the third version number.

Step S509: and storing the code blocks to be stored to a code warehouse corresponding to the first module.

EXAMPLE six

A sixth embodiment of the present invention provides a method for preferentially managing a multi-module system code version, where partial steps of the method for managing a multi-module system code version are the same as those in the foregoing embodiments, and details of the partial steps are not repeated 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 interacting with a user, a server back end processing data and a storage device 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 management method for multi-module system code versions according to a sixth embodiment of the present invention, and as shown in fig. 6, the management method for multi-module system code versions according to the sixth embodiment includes steps S601 to S615 as follows.

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 block of code to be stored is determined in the system.

Step S604: and when the code block to be stored is single and the module corresponding to the code block to be stored is the first module, updating the version number with the newer version sequence according to the version sequence rule to obtain a third version number.

Wherein, when updating the version number with a newer version sequence according to the version sequence rule, the following steps can be specifically adopted:

step S6041: an update level of a code block update of the first module is determined.

Step S6042: and acquiring sub information corresponding to the determined updating level in the version number with the newer version sequence to obtain the sub information to be updated.

Step S6043: and adding a preset increment to the sub-information to be updated to obtain the updated sub-information.

Step S6044: and if the sub information to be updated is 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.

Step S6045: and 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 newer 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 the 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 created version record, the version number of the first module and the version number of the system are set to be respectively a third version number, and the version numbers of other modules are set to be correspondingly the same as the version number in the last version record.

Step S607: and naming the code blocks to be stored according to the third version number, and storing the code blocks to be stored to a code warehouse corresponding to the first module.

Step S608: and when the number of the code blocks to be stored is two, the module corresponding to the first code block to be stored is the first module, and the module corresponding to the second code block to be stored is the second module, judging whether the first module and the second module meet the preset association relationship.

Step S609: and when the first module and the second module meet the preset incidence relation, updating the version number with the newer version sequence according to the version sequence rule to obtain a third version number.

The process of obtaining the third version number in step S609 is the same as the process of obtaining the third version number in step S604, and details are not repeated here.

Step S610: and determining that the updated version numbers of the first module and the second module are the third version number.

Step S611: and in the newly-created version record, setting the version numbers of the first module, the second module and the system to be third version numbers.

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 to a code warehouse corresponding to the first module, and storing the second code block to be stored to a code warehouse corresponding to the second module.

Step S613: and when the first module and the second module do not meet the preset association relationship, updating the version number with the newer version sequence 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 step S613 is the same as the process of obtaining the third version number in step S604, and details thereof are not repeated.

The step of obtaining the fourth version number in 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 updating 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 the updated sub-information.

Step S6134: and if the sub information to be updated is the lowest update level, replacing the sub information to be updated in the third version number with the update sub information to obtain a fourth version number.

Step S6135: and 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 with 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 the initial sub information to obtain a fourth version number.

In one embodiment, the system includes three modules a, B, and C, and the update history of the version numbers of the code blocks of the three modules should be as follows, and the description for each update of the following table is as follows:

1) the three ABC modules are updated dependently to obtain the version number of 1.0.0.

2) And updating the module A to obtain the version number of 1.0.1. The BC module version number is unchanged.

3) The AB block has interdependent updates, taking a version number of 1.1.0. 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) Three ABC modules are updated dependently to obtain version number 1.2.0.

7) And updating the module C to obtain the version number 1.3.0. The AB block version number is unchanged.

8) And updating the module C to obtain the version number 1.3.1. The AB block version number is unchanged.

9) The AB block has interdependent updates, taking the version number 1.4.0. The C module version number is unchanged.

Step S614: and in the newly-created version record, setting the first information as a third version number, and setting the second information and the third information as a fourth version number.

Step S615: naming a first code block to be stored according to the third version number, naming a second code block to be stored according to the fourth version number, storing the first code block to be stored to a code warehouse corresponding to the first module, and storing the second code block to be stored to a code warehouse corresponding to the second module.

With the multi-module system code version management method provided in this embodiment, the version numbers of all modules are ordered, that is, the next assigned version number must be greater than the version number with the latest version sequence in the current version numbers of all modules, for example, the version sequence in the current version numbers of all modules is 1.4.8, and then the next assigned version number 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 ensured to be ordered, and version conflicts caused by the fact that different modules are distributed with the same version number through different distribution are prevented. And as long as the module is updated, the version number can be updated once, the module can be ensured to have a corresponding version number every time the module is updated, when the updates of a plurality of modules are mutually dependent, each module can obtain the same version number, and as for the version number of the system, the version number with the latest version sequence in the current version numbers of all the modules is taken as the version number of the whole system every time the version number of the system is updated. The management method of the multi-module system code version inherits the advantage of flexible authority management when the modules are managed separately, effectively controls the operation risk of non-module owners, and the department where the module is located only needs to update the module of the module, can independently update and release the module without depending on other departments, thereby improving the production efficiency. The problem that the version numbers are not uniform when the modules are separately managed and the system is not favorable for releasing the codes of the specified versions is solved. When the system needs to release a code of a certain version, the version number corresponding to each module can be conveniently found, and the code block corresponding to the determined version number is used for deployment, so that the problem of deployment failure caused by the fact that dependency among the modules cannot correspond to each other is avoided.

EXAMPLE seven

Corresponding to the management method of the multi-module system code version provided in the above embodiments, a seventh embodiment of the present invention provides a management apparatus of the multi-module system code version, and reference may be made to the above embodiments for related technical features and corresponding technical effects, and the embodiments are only briefly described. Fig. 7 is a block diagram of an apparatus for managing code versions of a multi-module system according to a seventh embodiment of the present invention, as shown in fig. 7, the apparatus includes: a first determining module 701, an updating module 702 and a second determining 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 in 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 the version number with the newer version sequence according to the version sequence rule to obtain a third version number; and the second determining module 703 is configured to determine that the updated version number of the first module is the third version number.

Optionally, in an embodiment, the version number includes at least two pieces of sub information, each piece of sub information corresponds to an update level, and the update module 702 includes a first determining unit, a first obtaining unit, a first processing unit, a first updating unit, and a second updating unit. The first determining unit is used for determining the update level of the code block update of the first module; the first obtaining unit is used for obtaining the sub information corresponding to the determined updating level in the version number with the newer version sequence to obtain the sub information to be updated; the first processing unit is used for increasing a 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 a newer version sequence by using the updating sub information to obtain a third version number when the sub information to be updated is at the lowest updating level; and the second updating unit is used for replacing the sub information to be updated in the version number with the updated sub information 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 the initial sub information to obtain a third version number.

Optionally, in an embodiment, the management apparatus further includes a determining module, a third determining module, and a fourth determining module, where the determining module is configured to determine whether the first module and the second module satisfy a preset association relationship when the first module and the second module are updated simultaneously; the third determining module is used for determining the updated version number of the second module as a third version number when the first module and the second module meet the preset incidence relation; 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 incidence relation, and determining the updated version number of the second module as 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 apparatus further includes a new creation module, a first processing module, a second processing module, and a third processing module, where the new creation module is configured to create a new version record in the management table; the first processing module is used for setting the first information and the third information to be a third version number and setting the second information to be 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 to be a third 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 meet a preset incidence relation; the third processing module is used for setting the first information as a third version number and setting the second information and the third information as fourth version numbers 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 meet the preset association relationship.

Optionally, in an embodiment, the management apparatus 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 from among 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 the first module, it is determined that the first module is updated; the first determining module 701 includes a second obtaining unit, configured to obtain third information in a last version record in the management table before a step of creating a new 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, which is used for naming the code block 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 block to be stored to the code warehouse corresponding to the first module.

Optionally, in an embodiment, when the fifth determining module determines the module corresponding to the code block to be stored in the system, the specifically executed step includes: providing a module selection interface; acquiring module selection operation received by a module selection interface; the determination module selects the module selected for operation in the system.

Optionally, in an embodiment, when the fifth determining module determines the module corresponding to the code block to be stored in the system, the specifically executed step includes: acquiring identification information of a code block to be stored; a module having identification information is located in the system.

Example eight

The eighth embodiment further provides a computer device, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster composed of multiple servers) capable of executing programs. As shown in fig. 8, the computer device 01 of the present embodiment at least includes but is not limited to: a memory 011 and a processor 012 which are communicatively connected to each other via a system bus, as shown in fig. 8. It is noted that fig. 8 only shows the computer device 01 having the component memory 011 and the processor 012, but it is to be understood that not all of the shown components are required to be implemented, and that more or fewer components may be implemented instead.

In this embodiment, the memory 011 (i.e., a readable storage medium) includes 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, and the like. In some embodiments, the storage 011 can be an internal storage unit of the computer device 01, such as a hard disk or a memory of the computer device 01. In other embodiments, the memory 011 can also be an external storage device of the computer device 01, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc. provided on the computer device 01. Of course, the memory 011 can also include both internal and external memory units of the computer device 01. In this embodiment, the memory 011 is generally used for storing an operating system installed in the computer device 01 and various application software, such as program codes of the management apparatus of the multi-module system code version of the seventh embodiment. Further, the memory 011 can also be used to temporarily store various kinds of data that have been output or are to be output.

The processor 012 may be a Central Processing Unit (CPU), a controller, a microcontroller, a microprocessor, or other data Processing chip in some embodiments. The processor 012 is generally used to control the overall operation of the computer device 01. In the present embodiment, the processor 012 is configured to run a program code stored in the memory 011 or process data, and for example, is configured to manage a version of a multi-module system code.

Example nine

The ninth embodiment further 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 implements corresponding functions. The computer-readable storage medium of this embodiment is used for storing a management apparatus for multi-module system code versions, and when executed by a processor, implements the management method for multi-module system code versions 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 an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A method for managing code versions in a multi-module system, the system comprising 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 number with the newer version sequence according to the version sequence rule to obtain a third version number; and

and determining the updated version number of the first module as the third version number.

2. The method for managing versions of multi-module system codes 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 order according to the 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 updating level in the version number with the updated version sequence 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 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;

and 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 version sequence by using the updated sub information, and setting all the sub information with the update level lower than that of the sub information to be updated as the initial sub information to obtain the third version number.

3. The method for managing versions of multi-module system code according to claim 1, further comprising:

when the first module and the second module are updated simultaneously, judging whether the first module and the second module meet a preset incidence relation or not;

when the first module and the second module meet a preset incidence 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 the preset incidence 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.

4. The method for managing code versions of a multi-module system according to claim 3, wherein a code version management table is preset, the management table includes a plurality of version records, each of the version records 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 further includes:

creating a version record 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 simultaneously and the first module and the second module meet a preset association relationship, setting the first information, the second information and the third information to be the third version number in the version record;

and 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 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.

5. The method for managing versions of multi-module system code according to claim 4, wherein before the step of determining the version number with the newer version number in the order of the first version number and the second version number, the method for managing versions of multi-module system code comprises: 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, it is determined that the first module is updated;

the step of determining the version number with the newer version sequence in the first version number and the second version number comprises the following steps: before the step of creating a new 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 that the updated version number of the first module is the third version number, the management method further includes: naming the code block to be stored according to the third version number, and storing the code block to be stored to a code warehouse corresponding to the first module.

6. The method for managing code versions of a multi-module system according to claim 5, wherein the step of determining the module corresponding to the code block to be stored in the system comprises:

providing a module selection interface;

obtaining module selection operation received by the module selection interface;

determining in the system that the module selection operation selected module.

7. The method for managing code versions of a multi-module system according to claim 5, wherein the step of determining the module corresponding to the code block to be stored in the system comprises:

acquiring identification information of the code block to be stored;

and searching the module with the identification information in the system.

8. A management apparatus for code versions of a multi-module system, the system comprising at least a first module and a second module, the management apparatus comprising:

the first determining module is configured to determine, when the first module is updated, a version number with a newer version sequence in 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 is used for updating the version number with the newer version sequence according to the version sequence rule to obtain a third version number; and

and the second determining module is used for determining the updated version number of the first module as the third version number.

9. 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 steps of the method of any of claims 1 to 7 are implemented by the processor when executing the computer program.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that: the computer program when executed by a processor implements the steps of the method of any one of claims 1 to 7.