Multi-warehouse multi-branch change record viewing system and method, electronic equipment and medium

Abstract

The invention discloses a multi-warehouse and multi-branch change record viewing system and method, electronic equipment and a medium. The method comprises the following steps that S1, a storage module stores information of a trigger node; s2, the interaction module receives the specified node information and transmits the specified node information to the storage module; s3, the management module obtains information through the specified node information and the trigger node information of the storage module, wherein the information comprises first information and second information; s4, a comparison module compares the first information and the second information obtained in the step S3 to obtain difference data; and S5, the interaction module presents or displays the difference data in the step S4. According to the method, multi-warehouse and multi-branch comparison can be carried out by analyzing the branch dependency relationship between different constructions; therefore, differences of two times of construction can be compared, and the rationality of submission and troubleshooting can be effectively checked.

Description

Technical Field

[0001] The present invention relates to a code change record viewing method, and in particular to a multi-warehouse and multi-branch change record viewing system, method, electronic equipment and medium, belonging to the technical field of code management. Background Art

[0002] In computer program development, such as game development or large-scale software and project development, many teams choose to use multiple repositories for code and asset management in a project to improve security (that is, one member cannot obtain all asset content), but this also brings the problem of not being able to view change records as a whole.

[0003] Currently, mainstream software such as Jenkins and BlueShield in the industry can only view the changes in a single warehouse after the build. That is, although the changes in a single warehouse can be viewed after the build, they can only display the contents of a single warehouse and a single branch. It is impossible to merge and display the submissions of different types of warehouses and different branches. It is also impossible to merge and display different types of warehouses and submissions of multiple branches before and after the build, and to view the changes of large projects and multi-project merged builds. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a multi-warehouse and multi-branch change record viewing system, method, electronic device and medium, which solves the problem that the prior art cannot query and display multi-warehouse and multi-branch information.

[0005] The technical problem to be solved by the present invention is achieved by adopting the following technical solutions: The present invention provides a multi-warehouse and multi-branch change record viewing system, comprising a management module, a storage module, a comparison module and an interaction module, wherein: The management module is used to connect to the warehouse to obtain information; The storage module is used to store information corresponding to the trigger node; The comparison module is used to compare the information of the trigger node and the specified node and return the difference data; The interaction module is used to display the difference data returned by the comparison module and / or receive the designated node information.

[0006] As a preferred technical solution of the present invention, when the management module obtains information, the outgoing parameters include a first parameter, a second parameter, a third parameter and a fourth parameter.

[0007] As a preferred technical solution of the present invention, the designated node information received by the interaction module includes before construction or after construction.

[0008] The present invention also provides a method for viewing change records of multiple warehouses and multiple branches, which is applied to the aforementioned system for viewing change records of multiple warehouses and multiple branches, and comprises the following steps: Step S1, the storage module stores the information of the triggering node; Step S2, the interaction module receives the designated node information and transmits it to the storage module; Step S3, the management module acquires information, including first information and second information, through the designated node information and trigger node information of the storage module; Step S4, a comparison module compares the first information and the second information obtained in step S3 to obtain difference data; Step S5: The interaction module presents or displays the difference data in step S4.

[0009] As a preferred technical solution of the present invention, the first information is a submission record of a designated node, and the second information is a submission record of a triggering node.

[0010] As a preferred technical solution of the present invention, in step S3, when the management module obtains the first information and the second information, the outgoing parameters include the first parameter, the second parameter, the third parameter and the fourth parameter, wherein: The first parameter includes the warehouse ID, the second parameter includes the branch information, the third parameter includes the first hash value, and the fourth parameter includes the second hash value.

[0011] As a preferred technical solution of the present invention, the first Hash value is the Hash value of the designated node, and the second Hash value is the Hash value of the triggering node.

[0012] As a preferred technical solution of the present invention, the first parameter also includes a warehouse address, a warehouse key, and a warehouse type.

[0013] The present invention also provides an electronic device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the aforementioned method for viewing change records of multiple warehouses and multiple branches are implemented; The present invention also provides a medium storing a computer program that can be loaded by a processor and execute the aforementioned method for viewing change records of multiple warehouses and multiple branches.

[0014] The beneficial effects of the present invention are as follows: the present invention can compare multiple warehouses and multiple branches by analyzing the branch dependencies between different builds; thus, the differences between two builds can be compared, and the rationality of submissions and troubleshooting can be effectively checked; the key core can be prevented from being exploited by others, and the method of displaying and comparing before and after the project construction can be used in the form of multiple warehouses and multiple branches; the differences in submissions of different builds can be compared, and submissions of different types of warehouses and multiple branches can be combined and displayed at the same time, and the changes of large projects and multi-project combined builds can be viewed, which is convenient for testers, developers and managers to confirm the rationality and accuracy of the builds. For versions with problems, because the differences can be comprehensively viewed, effective data support is provided for troubleshooting. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a schematic diagram of the system of the present invention; Figure 2 The change record viewing interface constructed in Example 2 of the present invention; Figure 3 The change record viewing interface constructed before in Example 2 of the present invention; Figure 4 A viewing interface for viewing change records of related iteration requirements in a project management system in Example 2 of the present invention; Figure 5 This is a schematic diagram of the operation process in Example 2 of the present invention; Figure 6 for Figure 5 A partial enlarged view (1 / 3); Figure 7 for Figure 5 A partial enlarged view of (2 / 3); Figure 8 for Figure 5 A partial enlarged view of (3 / 3); In the figure: 1. Management module; 2. Storage module; 3. Comparison module; 4. Interaction module. DETAILED DESCRIPTION

[0016] The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0017] Example 1 like Figure 1 As shown, this embodiment provides a multi-warehouse and multi-branch change record viewing system, including a management module 1, a storage module 2, a comparison module 3 and an interaction module 4, wherein: Management module 1, used to connect to the warehouse to obtain information; Storage module 2, used to store information corresponding to the trigger node; Comparison module 3, used to compare the information of the trigger node with the specified node and return the difference data; The interaction module 4 is used to display the difference data returned by the comparison module 3 and / or receive the designated node information.

[0018] When the management module 1 obtains information, the outgoing parameters include a first parameter, a second parameter, a third parameter and a fourth parameter.

[0019] The designated node information received by the interaction module 4 includes information before or after construction.

[0020] The viewing system in this embodiment is implemented as shown in Example 2.

[0021] Example 2 This embodiment provides a method for viewing change records of multiple warehouses and multiple branches, which is applied to a system for viewing change records of multiple warehouses and multiple branches in Embodiment 1, and includes the following steps: Step S1, the storage module 2 stores the information of the triggering node, that is, the detailed information submitted when the triggering time node is constructed; Step S2, the interaction module 4 receives the designated node information and transmits it to the storage module 2; Step S3, the management module 1 obtains information, including first information and second information, through the designated node information and trigger node information of the storage module 2; Step S4, the comparison module 3 compares the first information and the second information obtained in step S3 to obtain difference data, that is, compares the submission record at the build triggering time stored in the storage module 2 with any submission record (specified node) specified by the user, obtains the difference between the two submission records, and returns a list of difference records; In step S5 , the interaction module 4 presents or displays the difference data in step S4 .

[0022] Preferably, the first information is the submission record of the designated node or the submission record of the triggering node, and the second information is the submission record of the triggering node or the submission record of the designated node. In this embodiment, preferably, the first information is the submission record of the designated node, and the second information is the submission record of the triggering node.

[0023] In step S3, when the management module 1 obtains the first information and the second information, the outgoing parameters include the first parameter, the second parameter, the third parameter and the fourth parameter, wherein: The first parameter includes the warehouse id, the second parameter includes the branch information, the third parameter includes the first hash value, and the fourth parameter includes the second hash value. The first hash value is the hash value of the specified node, and the second hash value is the hash value of the triggering node; in this embodiment, the first parameter is the warehouse id (repo_id), the second parameter is the submission branch (ref_name), the third parameter is the submission hash A (hashA), that is, the hash value of the submission record of the specified node (the first hash value), and the fourth parameter is the submission hash B (hashB), that is, the hash value of the submission node submission record (the second hash value).

[0024] Preferably, the first parameter also includes a warehouse address, a warehouse key, and a warehouse type.

[0025] Specifically, the management module 1 has the code repository management capability to meet the necessary requirements for connecting to various types of repositories, and can query and obtain the corresponding information in the corresponding repository according to the specified node or trigger node.

[0026] Specifically, the type of repository is known through repo_id and its corresponding repository information repo_data, because the three types of repositories (Gitlab, Subversion, Perforce) have different implementations for obtaining submission records (the three types of warehouses in this embodiment are only examples, and the actual warehouse type is configured and / or adjusted according to the actual situation). In order to better realize the viewing of multi-repository and multi-branch change records, we abstract it into a call for obtaining change records (obtained through the four outgoing parameters). This call can be used to simultaneously view multi-repository and multi-branch change records for different types of repositories.

[0027] Different queries can achieve different effects before and after the build time. For example, querying and comparing the specified node and the trigger node before the build can be used to prevent and remind incorrect submissions from being mixed in, causing those incorrect submissions to be built into the package. Figure 3 As shown; after the build, query and compare the specified node and the trigger node. This can be used to check the submission information of this build when the tester finds a problem, and assist in locating the problematic submission record, such as Figure 2 shown.

[0028] Preferably, the storage module can also be associated with the demand sheet and defect sheet of the project management system, so that all submissions of the associated sheets can be viewed, making the development content of each sheet clear and understandable, such as Figure 4 shown.

[0029] The above overall process diagram can be referred to Figure 5 shown.

[0030] Example 3 This embodiment provides an electronic device including a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of a method for viewing change records of multiple warehouses and multiple branches in Example 2 are implemented.

[0031] Example 4 This embodiment provides a medium storing a computer program that can be loaded by a processor and execute a method for viewing change records of multiple warehouses and multiple branches as in Embodiment 2.

[0032] The present invention can compare multiple warehouses and multiple branches by analyzing the branch dependency between different builds; thus, the difference between two builds can be compared, and the rationality of submission and problem solving can be effectively checked; the key core that can be used by others can be prevented, and the method of displaying and comparing before and after the project construction can be used in the form of multiple warehouses and multiple branches; the submission differences of different builds can be compared, and submissions of different types of warehouses and multiple branches can be combined and displayed at the same time, and the changes of large projects and multi-project combined builds can be viewed, which is convenient for testers, developers and managers to confirm the rationality and accuracy of the build. For versions with problems, because the differences can be comprehensively viewed, effective data support is provided for problem solving.

[0033] The basic principles, main features and advantages of the present invention are shown and described above. It should be understood by those skilled in the art that the present invention is not limited to the above embodiments. Without departing from the spirit and scope of the present invention, the present invention may have various changes and improvements, which fall within the scope of the present invention. The scope of the present invention is defined by the attached claims and their equivalents.

Claims

1. A multi-warehouse and multi-branch change record viewing system, characterized in that: It comprises a management module (1), a storage module (2), a comparison module (3) and an interaction module (4), wherein: The management module (1) is used to connect to the warehouse to obtain information; The storage module (2) is used to store information corresponding to the trigger node; The comparison module (3) is used to compare the information of the trigger node and the designated node and return the difference data; The interaction module (4) is used to display the difference data returned by the comparison module (3), and / or receive designated node information.

2. A multi-warehouse and multi-branch change record viewing system according to claim 1, characterized in that: When the management module (1) acquires information, the outgoing parameters include a first parameter, a second parameter, a third parameter and a fourth parameter.

3. A multi-warehouse and multi-branch change record viewing system according to claim 1, characterized in that: The designated node information received by the interaction module (4) includes information before construction or after construction.

4. A method for viewing change records of multiple warehouses and multiple branches, applied to a system for viewing change records of multiple warehouses and multiple branches as claimed in any one of claims 1 to 3, characterized in that: The steps include: Step S1, the storage module (2) stores the information of the triggering node; Step S2, the interaction module (4) receives the designated node information and transmits it to the storage module (2); Step S3, the management module (1) acquires information, including first information and second information, through the designated node information and trigger node information of the storage module (2); Step S4, the comparison module (3) compares the first information and the second information obtained in step S3 to obtain difference data; Step S5, the interaction module (4) presents or displays the difference data in step S4.

5. A method for viewing change records of multiple warehouses and multiple branches according to claim 4, characterized in that: The first information is a submission record of a designated node, and the second information is a submission record of a triggering node.

6. A method for viewing change records of multiple warehouses and multiple branches according to claim 4, characterized in that: In step S3, when the management module (1) acquires the first information and the second information, the outgoing parameters include the first parameter, the second parameter, the third parameter and the fourth parameter, wherein: The first parameter includes the warehouse ID, the second parameter includes the branch information, the third parameter includes the first hash value, and the fourth parameter includes the second hash value.

7. A method for viewing change records of multiple warehouses and multiple branches according to claim 6, characterized in that: The first hash value is the hash value of the specified node, and the second hash value is the hash value of the triggering node.

8. A method for viewing change records of multiple warehouses and multiple branches according to claim 4 or 6, characterized in that: The first parameter also includes the warehouse address, warehouse key, and warehouse type.

9. An electronic device, characterized in that: It includes a processor and a memory, the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of a multi-warehouse and multi-branch change record viewing method as described in any one of claims 4-8 are implemented.

10. A medium, characterized in that The computer program is stored which can be loaded by a processor and execute the method for viewing change records of multiple warehouses and multiple branches as claimed in any one of claims 4 to 8.

Images