Component management method, system, server and storage medium for multi-version development
By managing component versions through multiple indexes, the problem of excessive component management costs in large development teams is solved, and efficient multi-version development management is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SHANGHAI SHIZHUANG INFORMATION TECHNOLOGY CO LTD
- Filing Date
- 2022-11-03
- Publication Date
- 2026-05-15
AI Technical Summary
In large development teams, the excessive number of components leads to high component management costs. Existing methods of manually specifying component version numbers or limiting the number of components are not effective for large-scale teams and are prone to errors.
Component versions are managed through multiple indexes, and the additions and deletions of component indexes are recorded to avoid component version updates. Automated management tools are used to reduce management costs.
It enables efficient management of multiple versions of development without updating component versions, reducing management difficulty and cost, and improving management efficiency.
Smart Images
Figure CN115794077B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the field of software development technology, and in particular to a component management method, system, server and storage medium for multi-version development. Background Technology
[0002] A component typically refers to a collection of code blocks used to implement a requirement or solve a problem, while an index typically refers to a repository or container that stores version information and configuration descriptions of several components.
[0003] Modern code development is typically carried out by multiple teams. When the same component needs to be modified simultaneously in multiple versions developed by different teams, the code commits and version updates of the component will become messy and disordered if they are not controlled. Solving the management of component code under multi-version development is a problem that large development teams need to face together.
[0004] Currently, there are several solutions in the industry, generally involving manually specifying component version numbers or limiting the number of components. However, these methods have several problems: 1. Fixing version numbers requires manual maintenance or a complete backend management system and service, which is very costly; 2. While this might be barely usable if the number of components is in the tens or even hundreds, it exceeds management limits when the number of components reaches 500, 1000, or even 5000, making it difficult to manage manually; 3. If an incorrect version number is specified, the entire team will be affected.
[0005] Therefore, manually specifying component version numbers is only suitable for small teams or situations with a small number of components. In a large team or project with hundreds or thousands of components, it cannot support the team's operation, and the maintenance of all components will be so costly that it cannot support the normal iterative development of the entire team. Summary of the Invention
[0006] This invention provides a component management method for multi-version development, which solves the problem of excessive component management costs caused by an excessive number of different versions of components in the prior art, and achieves the effect of using a single version of components to achieve multi-version development.
[0007] This invention provides a component management method for multi-version development, comprising:
[0008] In response to the code development behavior, the first version of the code after development is obtained, the target component version of the first version is set to a fixed value, and the target component index library of the first version is recorded as the first index library.
[0009] In response to the secondary development behavior of the first version, a second version after the secondary development is completed is obtained, and the target component index library of the second version is compared with the first index library;
[0010] When the target component index library of the second version has new content compared with the first index library, the target component version is not modified, and the new content of the target component index library of the second version is recorded as the second index library. The target component index library of the second version is the first index library and the second index library.
[0011] Preferably, in response to the secondary development behavior of the first version, after obtaining the second version after the secondary development is completed, and comparing the target component index library of the second version with the first index library, the method further includes:
[0012] When the content of the second version component index library is consistent with that of the first index library, the target component index library of the second version is the first index library.
[0013] Preferably, in response to the secondary development behavior of the first version, after obtaining the second version after the secondary development is completed, and comparing the target component index library of the second version with the first index library, the method further includes:
[0014] When the second version of the component index library has been reduced compared with the first index library, the target component index library of the second version is recorded as the third index library, the reduced content is recorded as the fourth index library, and the first index library is recorded as the third index library and the fourth index library.
[0015] Preferably, when the second version of the target component index library has new content compared to the first index library, the target component version is not modified, and the new content of the second version of the target component index library is recorded as the second index library. After the steps of the second version of the target component index library being the first index library and the second index library, the method further includes:
[0016] When parallel development of the secondary development exists, a third version is obtained after the parallel development is completed;
[0017] When it is necessary to merge the second version and the third version, compare the target component index library of the second version with the target component index library of the third version;
[0018] When the target component index library of the third version is the first index library, and the content of the target index library of the second version has been reduced, the merged target component index library includes the third index library and the fourth index library.
[0019] Preferably, when it is necessary to merge the second version and the third version, after the step of comparing the target component index library of the second version and the target component index library of the third version, the method further includes:
[0020] When the target component index library of the third version is the first index library, and the target index library of the second version contains new content, the merged target component index library includes the first index library and the second index library.
[0021] Preferably, when it is necessary to merge the second version and the third version, after the step of comparing the target component index library of the second version and the target component index library of the third version, the method further includes:
[0022] When the target component index library of the third version is the first index library and the fifth index library, wherein the fifth index library is the new content added to the target index library of the third version compared to the first index library, and the target index library of the second version also has new content, the merged target component index library includes the first index library, the second index library and the sixth index library, wherein the sixth index library is the content added to the second index library relative to the second index library after the second index library and the fifth index library are merged.
[0023] This invention also proposes a component management system for multi-version development, comprising:
[0024] The code development unit, in response to the code development behavior, obtains the first version of the code after the development is completed, sets the target component version of the first version to a fixed value, and records the target component index library of the first version as the first index library.
[0025] The version update unit, in response to the secondary development behavior of the first version, obtains the second version after the secondary development is completed, and compares the target component index library of the second version with the first index library;
[0026] The component management unit, when the target component index library of the second version has new content compared with the first index library, does not modify the target component version, but records the new content of the target component index library of the second version as the second index library, and the target component index library of the second version is the first index library and the second index library.
[0027] The present invention also proposes a server, the server comprising: a memory, a processor, and a component management program for multi-version development stored on the memory and capable of running on the processor, wherein the component management program for multi-version development implements the component management method for multi-version development as described above when executed by the processor.
[0028] The present invention also proposes a readable storage medium storing a component management program for multi-version development, wherein the component management program for multi-version development implements the steps of the component management method for multi-version development as described above when executed by a processor.
[0029] This invention manages components without updating component versions by using multiple index libraries, so that code execution does not require specifying the component version. This solves the problem of excessive component management costs caused by the large number of different versions of components in the prior art, and achieves the effect of using a single version of the component to achieve multi-version development. Attached Figure Description
[0030] Figure 1 This is a flowchart illustrating an embodiment of the component management method for multi-version development according to the present invention;
[0031] Figure 2 This is a flowchart illustrating another embodiment of the component management method for multi-version development of the present invention;
[0032] Figure 3 This is a flowchart illustrating another embodiment of the component management method for multi-version development of the present invention;
[0033] Figure 4 This is a schematic diagram of the system structure in an embodiment of the present invention;
[0034] Figure 5 This is a schematic diagram of the server structure in an embodiment of the present invention. Detailed Implementation
[0035] The present invention will now be described in further detail 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 not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.
[0036] Figure 1 A flowchart of a component management method for multi-version development provided in this embodiment of the invention specifically includes:
[0037] S100. In response to the code development behavior, obtain the first version of the code after the development is completed, set the target component version of the first version to a fixed value, and record the target component index library of the first version as the first index library.
[0038] It should be noted that the development behavior of this code can be newly developed code or a new version released based on a previous code version. When the development behavior is newly developed code, the fixed value of the target component version can be left blank, and only the component name needs to be kept. If it is a new version released based on a previous code version, the fixed value can be any version other than the existing component version.
[0039] S200: In response to the secondary development behavior of the first version, a second version after the secondary development is completed is obtained, and the target component index library of the second version is compared with the first index library;
[0040] It is worth emphasizing that since the index stores version information and configuration descriptions of several components, it can serve as a substitute for component versions and obtain specific information about different versions of components, so as to facilitate automatic management through automation tools such as automation scripts, machine language recognition and processing tools, etc.
[0041] It is easy to understand that, since the differences between different versions of components cannot be obtained solely based on the component version number, and different code requires a specified version number to run properly, management through an index library eliminates the need for code modifications; only the index library needs to be adjusted to apply the changes to all code.
[0042] It should be noted that modifications, corruption, or dirty data in a single index will not affect other indexes or versions. The version list in a single version index clearly shows which versions of the component exist, and there will be no unreadable content due to too many versions. The version number of a component can be different, duplicated, independent, or customized in different indexes.
[0043] S300. When the target component index library of the second version has new content compared with the first index library, the target component version is not modified, and the new content of the target component index library of the second version is recorded as the second index library. The target component index library of the second version is the first index library and the second index library.
[0044] It is important to emphasize that the above-mentioned new content includes the repository and container described in the index, which is generally a Git repository. When the code runs, you only need to use Git to pull the corresponding container or repository from the network according to the description in the index, and configure it according to the description to apply it to the code that uses this component.
[0045] This embodiment manages components without updating component versions by using multiple index libraries, so that code execution does not require specifying the component version. This solves the problem of excessive component management costs caused by the large number of different versions of components in the prior art, and achieves the effect of using a single version of the component to achieve multi-version development.
[0046] Reference Figure 2 , Figure 2 This is a flowchart of a component management method for multi-version development according to the present invention. The component management method for multi-version development, in response to the secondary development behavior of the first version, obtains a second version after the secondary development is completed, and after comparing the target component index library of the second version with the first index library, further includes:
[0047] S210. When the content of the second version component index library is consistent with that of the first index library, the target component index library of the second version is the first index library.
[0048] It is easy to understand that when the content of the second version component index library is consistent with that of the first index library, it means that the target component has not changed in this version update, so no adjustment is needed. Therefore, the index library does not need to be changed, and the first index library can be used.
[0049] Specifically, in response to the secondary development behavior of the first version, after obtaining the second version after the secondary development is completed, and comparing the target component index library of the second version with the first index library, the process further includes:
[0050] S220. When the second version of the component index library has been reduced compared with the content of the first index library, the target component index library of the second version is recorded as the third index library, the reduced content is recorded as the fourth index library, and the first index library is recorded as the third index library and the fourth index library.
[0051] It should be noted that, normally, the first index can be used directly even when the index is being reduced, but splitting the first index into a third and a fourth index usually improves performance.
[0052] This embodiment improves the technical solution by disclosing specific management methods for multiple index databases. By decomposing the index databases, performance is improved to a certain extent. Furthermore, merging multiple index databases is not difficult and can be done using existing automated scripts. This facilitates more complex management through additional automated management tools when there is sufficient capacity after the project's development.
[0053] Reference Figure 3 , Figure 3This is a flowchart illustrating another embodiment of the component management method for multi-version development of the present invention. When the target component index library of the second version has new content compared with the first index library, the target component version is not modified, and the new content of the target component index library of the second version is recorded as the second index library. After the steps of the target component index library of the second version being the first index library and the second index library, the method further includes:
[0054] S400. When there is parallel development of the secondary development, a third version is obtained after the parallel development is completed;
[0055] It is easy to understand that large-scale, multi-team code development is usually accompanied by parallel development. The technical solution of this application can still achieve good component version management when facing the complex environment of parallel development.
[0056] S500. When it is necessary to merge the second version and the third version, compare the target component index library of the second version with the target component index library of the third version.
[0057] It should be noted that since the secondary development of the code does not change all components, it is necessary to compare the index to confirm which components have been changed, and trigger the corresponding preset merging method based on the comparison results.
[0058] S600. When the target component index library of the third version is the first index library, and the content of the target index library of the second version has been deleted, the merged target component index library includes the third index library and the fourth index library.
[0059] It is worth emphasizing that the existing method of managing component version numbers requires the use of backend services, which involve databases, backend development, backend management systems, service maintenance, domain names, etc. In contrast, the management process of this application can be achieved with just a few lines of scripts, which greatly reduces management costs and improves management efficiency.
[0060] Specifically, when it is necessary to merge the second version and the third version, after the step of comparing the target component index library of the second version with the target component index library of the third version, the method further includes:
[0061] S700. When the target component index library of the third version is the first index library, and the target index library of the second version has new content, the merged target component index library includes the first index library and the second index library.
[0062] What is easy to understand is that the merged target component index library includes the first index library and the second index library, and also contains the code execution conditions of the second and third versions, ensuring the correct operation of the code. Moreover, the difficulty of this merger is close to that of pasting the other party's code after a line of code, which greatly reduces the management difficulty.
[0063] Specifically, when it is necessary to merge the second version and the third version, after the step of comparing the target component index library of the second version with the target component index library of the third version, the method further includes:
[0064] S800. When the target component index library of the third version is the first index library and the fifth index library, wherein the fifth index library is the new content added to the target index library of the third version compared to the first index library, and the target index library of the second version also has new content, the merged target component index library includes the first index library, the second index library and the sixth index library, wherein the sixth index library is the content added to the second index library relative to the second index library after the second index library and the fifth index library are merged.
[0065] It is worth noting that the second index library and the fifth index library may have duplicate content. Therefore, the fifth index library needs to be replaced by a sixth index library. The sixth index library can also be described as the fifth index library with the duplicate content removed from the second index library.
[0066] This embodiment improves the technical solution, reduces management difficulty and costs, and enhances the user experience by further disclosing the splitting and replacement of mutually inclusive index libraries, as well as how to publish new index libraries for mutually exclusive index libraries.
[0067] Reference Figure 4 , Figure 4 This is a schematic diagram of the system structure in an embodiment of the present invention.
[0068] Specifically, the component management system for multi-version development includes:
[0069] The code development unit 10, in response to the code development behavior, obtains the first version of the code after the development is completed, sets the target component version of the first version to a fixed value, and records the target component index library of the first version as the first index library.
[0070] Version update unit 20, in response to the secondary development behavior of the first version, obtains the second version after the secondary development is completed, and compares the target component index library of the second version with the first index library;
[0071] The component management unit 30, when the target component index library of the second version has new content compared with the first index library, does not modify the target component version, and records the new content of the target component index library of the second version as the second index library, and the target component index library of the second version is the first index library and the second index library.
[0072] This embodiment has the corresponding functional modules and beneficial effects of a component management method for multi-version development, which will not be described in detail here.
[0073] like Figure 5 As shown, Figure 5 This is a schematic diagram of a server structure according to another embodiment of the present invention. The server includes a processor 70, a memory 71, an input device 72, and an output device 73; the number of processors 70 in the server can be one or more. Figure 5 Taking a processor 70 as an example; the processor 70, memory 71, input device 72, and output device 73 in the server can be connected via a bus or other means. Figure 5 Taking the example of a connection between China and Israel via a bus.
[0074] The memory 71, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions corresponding to the component management method for multi-version development in this embodiment of the invention. The processor 70 executes various server functions and data processing by running the software programs, instructions, and modules stored in the memory 71, thereby implementing the aforementioned component management method for multi-version development.
[0075] The memory 71 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on terminal usage. Furthermore, the memory 71 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory, or other non-volatile solid-state storage device. In some instances, the memory 71 may further include memory remotely located relative to the processor 70, which can be connected to a server via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
[0076] Input device 72 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the server. Output device 73 may include a display server such as a display screen.
[0077] This embodiment has the corresponding functional modules and beneficial effects of the execution method, which will not be described in detail here.
[0078] This invention also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a component management method for multi-version development, the method comprising:
[0079] In response to the code development behavior, the first version of the code after development is obtained, the target component version of the first version is set to a fixed value, and the target component index library of the first version is recorded as the first index library.
[0080] In response to the secondary development behavior of the first version, a second version after the secondary development is completed is obtained, and the target component index library of the second version is compared with the first index library;
[0081] When the target component index library of the second version has new content compared with the first index library, the target component version is not modified, and the new content of the target component index library of the second version is recorded as the second index library. The target component index library of the second version is the first index library and the second index library.
[0082] Specifically, in response to the secondary development behavior of the first version, after obtaining the second version after the secondary development is completed, and comparing the target component index library of the second version with the first index library, the process further includes:
[0083] When the content of the second version component index library is consistent with that of the first index library, the target component index library of the second version is the first index library.
[0084] Specifically, in response to the secondary development behavior of the first version, after obtaining the second version after the secondary development is completed, and comparing the target component index library of the second version with the first index library, the process further includes:
[0085] When the second version of the component index library has been reduced compared with the first index library, the target component index library of the second version is recorded as the third index library, the reduced content is recorded as the fourth index library, and the first index library is recorded as the third index library and the fourth index library.
[0086] Specifically, when the second version of the target component index library has new content compared to the first index library, the target component version is not modified, and the new content of the second version of the target component index library is recorded as the second index library. After the steps of the second version of the target component index library being the first index library and the second index library, the following is also included:
[0087] When parallel development of the secondary development exists, a third version is obtained after the parallel development is completed;
[0088] When it is necessary to merge the second version and the third version, compare the target component index library of the second version with the target component index library of the third version;
[0089] When the target component index library of the third version is the first index library, and the content of the target index library of the second version has been reduced, the merged target component index library includes the third index library and the fourth index library.
[0090] Specifically, when it is necessary to merge the second version and the third version, after the step of comparing the target component index library of the second version with the target component index library of the third version, the method further includes:
[0091] When the target component index library of the third version is the first index library, and the target index library of the second version contains new content, the merged target component index library includes the first index library and the second index library.
[0092] Specifically, when it is necessary to merge the second version and the third version, after the step of comparing the target component index library of the second version with the target component index library of the third version, the method further includes:
[0093] When the target component index library of the third version is the first index library and the fifth index library, wherein the fifth index library is the new content added to the target index library of the third version compared to the first index library, and the target index library of the second version also has new content, the merged target component index library includes the first index library, the second index library and the sixth index library, wherein the sixth index library is the content added to the second index library relative to the second index library after the second index library and the fifth index library are merged.
[0094] Of course, the computer-executable instructions provided in the embodiments of the present invention are not limited to the above-described method operations. They can also execute related operations in the component management method for multi-version development provided in any embodiment of the present invention, and have the corresponding functional modules and beneficial effects of the execution method. These will not be described in detail here.
[0095] Based on the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of the various embodiments of the present invention.
[0096] It is worth noting that in the embodiments of the search device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.
[0097] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.
Claims
1. A component management method for multi-version development, characterized in that, include: In response to the code development behavior, the first version of the code after development is obtained, the target component version of the first version is set to a fixed value, and the target component index library of the first version is recorded as the first index library. In response to the secondary development behavior of the first version, a second version after the secondary development is completed is obtained, and the target component index library of the second version is compared with the first index library; When the target component index library of the second version has new content compared with the first index library, the target component version is not modified, and the new content of the target component index library of the second version is recorded as the second index library. The target component index library of the second version is the first index library and the second index library. In response to the secondary development behavior of the first version, a second version is obtained after the secondary development is completed. After the step of comparing the target component index library of the second version with the first index library, the method further includes: When the content of the second version component index library is the same as that of the first index library, the target component index library of the second version is the first index library; In response to the secondary development behavior of the first version, a second version is obtained after the secondary development is completed. After the step of comparing the target component index library of the second version with the first index library, the method further includes: When the second version of the component index library has been reduced compared with the first index library, the target component index library of the second version is recorded as the third index library, the reduced content is recorded as the fourth index library, and the first index library is recorded as the third index library and the fourth index library; When the second version of the target component index library has new content compared to the first index library, the target component version is not modified, and the new content of the second version of the target component index library is recorded as the second index library. After the steps of the second version of the target component index library being the first index library and the second index library, the following is also included: When parallel development of the secondary development exists, a third version is obtained after the parallel development is completed; When it is necessary to merge the second version and the third version, compare the target component index library of the second version with the target component index library of the third version; When the target component index library of the third version is the first index library, and the content of the target index library of the second version has been reduced, the merged target component index library includes the third index library and the fourth index library.
2. The component management method for multi-version development according to claim 1, characterized in that, When it is necessary to merge the second version and the third version, the step of comparing the target component index library of the second version with the target component index library of the third version further includes: When the target component index library of the third version is the first index library, and the target index library of the second version contains new content, the merged target component index library includes the first index library and the second index library.
3. The component management method for multi-version development according to claim 1, characterized in that, When it is necessary to merge the second version and the third version, the step of comparing the target component index library of the second version with the target component index library of the third version further includes: When the target component index library of the third version is the first index library and the fifth index library, wherein the fifth index library is the new content added to the target index library of the third version compared to the first index library, and the target index library of the second version also has new content, the merged target component index library includes the first index library, the second index library and the sixth index library, wherein the sixth index library is the content added to the second index library relative to the second index library after the second index library and the fifth index library are merged.
4. A component management system for multi-version development, characterized in that, include: The code development unit, in response to the code development behavior, obtains the first version of the code after the development is completed, sets the target component version of the first version to a fixed value, and records the target component index library of the first version as the first index library. The version update unit, in response to the secondary development behavior of the first version, obtains the second version after the secondary development is completed, and compares the target component index library of the second version with the first index library; The component management unit, when the target component index library of the second version has new content compared with the first index library, does not modify the target component version, records the new content of the target component index library of the second version as the second index library, and the target component index library of the second version is the first index library and the second index library; In response to the secondary development behavior of the first version, a second version is obtained after the secondary development is completed. After the step of comparing the target component index library of the second version with the first index library, the method further includes: When the content of the second version component index library is the same as that of the first index library, the target component index library of the second version is the first index library; In response to the secondary development behavior of the first version, a second version is obtained after the secondary development is completed. After the step of comparing the target component index library of the second version with the first index library, the method further includes: When the second version of the component index library has been reduced compared with the first index library, the target component index library of the second version is recorded as the third index library, the reduced content is recorded as the fourth index library, and the first index library is recorded as the third index library and the fourth index library; When the second version of the target component index library has new content compared to the first index library, the target component version is not modified, and the new content of the second version of the target component index library is recorded as the second index library. After the steps of the second version of the target component index library being the first index library and the second index library, the following is also included: When parallel development of the secondary development exists, a third version is obtained after the parallel development is completed; When it is necessary to merge the second version and the third version, compare the target component index library of the second version with the target component index library of the third version; When the target component index library of the third version is the first index library, and the content of the target index library of the second version has been reduced, the merged target component index library includes the third index library and the fourth index library.
5. A server, characterized in that, The server includes: a memory, a processor, and a component management program for multi-version development stored on the memory and capable of running on the processor. When the component management program for multi-version development is executed by the processor, it implements the component management method for multi-version development as described in any one of claims 1 to 3.
6. A readable storage medium, characterized in that, The readable storage medium stores a component management program for multi-version development, which, when executed by a processor, implements the steps of the component management method for multi-version development according to any one of claims 1 to 3.