A code submission management system

Abstract

The present application relates to the field of code management technology, and in particular to a code submission management system, which includes: a server, a client, a processor, and a memory storing a computer program, wherein the server includes a critical path and a password book, and when the computer program is executed by the processor, the following steps are implemented: if there is a critical path consistent with the target path, the change number corresponding to the target code is queried, and when the change number is not empty and the password book contains the change number, the password information is determined, and if the code description information contains the password information, the target code is submitted to the target path in the server. It can be seen that by setting the critical path, the review process is only carried out when the target path of the code submission is the critical path, and the change number and code description information are detected in the review process to ensure that the submitted code is in a state that has been reviewed by the target personnel, thereby improving the flexibility and efficiency of code submission management.

Description

Technical Field

[0001] The present invention relates to the technical field of code management, and in particular to a code submission management system. Background Art

[0002] Usually, the code base of a task needs to be written and updated by multiple task members, and the use of a code management system can facilitate the maintenance of the code base. The code management system usually includes a server and several clients. The server can be used to maintain the code base. Task members can submit code to the server through any client, and then the server will update the submitted code to the code base. Code updates can include operations such as adding, changing, and deleting codes in the code base, thereby realizing distributed code management. For example, the code management system can use the Perforce system.

[0003] However, in the code management scenario, different paths in the code base may have different importance levels. Paths with lower importance can be submitted directly when code is submitted, while paths with higher importance require target personnel to review when code is submitted. Existing code management systems can usually only be used to standardize the code submission process. When there is a need to review code submission, it is difficult to accurately and promptly notify the target personnel, and the code submission review process has a low degree of automation, resulting in low flexibility and efficiency in code submission management.

[0004] Therefore, how to improve the flexibility and efficiency of code submission management has become an urgent problem to be solved. Summary of the invention

[0005] In view of the above technical problems, the technical solution adopted by the present invention is:

[0006] A code submission management system, the system comprising: a server, a client, a processor and a memory storing a computer program, wherein the server comprises a plurality of key paths and a code book, and when the computer program is executed by the processor, the following steps are implemented:

[0007] S101, when the client submits the target code to the target path of the server, it is detected whether there is a key path consistent with the target path, and the target code corresponds to a change sequence number and code description information.

[0008] S102: If there is a key path that is consistent with the target path, query the change sequence number corresponding to the target code.

[0009] S103, when the change number is not empty, parse the change number to obtain the task corresponding to the change number.

[0010] S104, obtaining a target personnel set corresponding to the task, wherein the target personnel set includes a plurality of target personnel for the task.

[0011] S105, query whether the code book contains the change sequence number.

[0012] S106: If the password book does not contain the change number, a character string is randomly generated as the password information of the change number.

[0013] S107, adding the change sequence number and its corresponding password information to the password book.

[0014] S108, sending the change sequence number and its corresponding password information to the target personnel set.

[0015] S109: If the code book contains the change sequence number, determine the code information corresponding to the change sequence number in the code book.

[0016] S110, detecting whether the code description information includes the password information.

[0017] S111, if the code description information does not contain the password information, a first feedback information is sent to the client, and the first feedback information is used to remind the client to apply for the password information from the target personnel set, so as to update the password information to the code description information and resubmit the target code.

[0018] S112: If the code description information includes the password information, submit the target code to the target path in the server.

[0019] Compared with the prior art, the present invention has obvious beneficial effects. By means of the above technical solution, a code submission management system provided by the present invention can achieve considerable technical advancement and practicality, and has wide industrial utilization value, and has at least the following beneficial effects:

[0020] The present invention provides a code submission management system, the system comprising: a server, a client, a processor and a memory storing a computer program, wherein the server comprises a plurality of key paths and a code book, and when the computer program is executed by the processor, the following steps are implemented: when the client submits a target code to a target path of the server, detecting whether there is a key path consistent with the target path, the target code corresponds to a change sequence number and code description information, if there is a key path consistent with the target path, querying the change sequence number corresponding to the target code, when the change sequence number is not empty, parsing the change sequence number, obtaining a task corresponding to the change sequence number, obtaining a target personnel set corresponding to the task, the target personnel set comprising a plurality of target personnel for the task, querying whether the code book contains the change sequence number, if the code book contains the change sequence number If the password book does not contain the change number, a character string is randomly generated as the password information of the change number, the change number and its corresponding password information are added to the password book, and the change number and its corresponding password information are sent to the target personnel set. If the password book contains the change number, the password information corresponding to the change number is determined in the password book, and it is detected whether the code description information contains the password information. If the code description information does not contain the password information, a first feedback information is sent to the client, and the first feedback information is used to remind the client to apply for the password information from the target personnel set, so as to update the password information to the code description information and resubmit the target code. If the code description information contains the password information, the target code is submitted to the target path in the server.

[0021] It can be seen that by setting the critical path, the review process is only carried out when the target path of the code submission is the critical path, and the change sequence number and code description information are detected in the review process to ensure that the submitted code is in a state that has passed the review of the target personnel, which improves the flexibility of code submission management, and promptly notifies the target personnel of the code that needs to be reviewed, thereby improving the efficiency of code submission management. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0023] Figure 1 A flowchart of a computer program executed by a processor in a code submission management system provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0025] This embodiment provides a code submission management system, the system comprising: a server, a client, a processor and a memory storing a computer program, wherein the server comprises several key paths and a code book, see Figure 1 , is a flow chart of a computer program executed by a processor in a code submission management system provided by an embodiment of the present invention. When the computer program is executed by the processor, the following steps are implemented:

[0026] S101, when the client submits the target code to the target path of the server, detecting whether there is a key path consistent with the target path, the target code corresponding to the change sequence number and code description information;

[0027] S102, if there is a key path that is consistent with the target path, query the change sequence number corresponding to the target code;

[0028] S103, when the change sequence number is not empty, parsing the change sequence number to obtain a task corresponding to the change sequence number;

[0029] S104, obtaining a target personnel set corresponding to the task, wherein the target personnel set includes a plurality of target personnel for the task;

[0030] S105, querying whether the code book contains the change sequence number;

[0031] S106, if the password book does not contain the change sequence number, randomly generate a character string as the password information of the change sequence number;

[0032] S107, adding the change sequence number and its corresponding password information to the password book;

[0033] S108, sending the change sequence number and its corresponding password information to the target personnel set;

[0034] S109, if the code book contains the change sequence number, determine the code information corresponding to the change sequence number in the code book;

[0035] S110, detecting whether the code description information includes the password information;

[0036] S111, if the code description information does not include the password information, sending first feedback information to the client, the first feedback information is used to remind the client to apply for the password information from the target personnel set, so as to update the password information to the code description information and resubmit the target code;

[0037] S112: If the code description information includes the password information, submit the target code to the target path in the server.

[0038] The code submission management system provided in this embodiment may be based on an existing code management system, and the existing code management system may adopt, for example, a Perforce system.

[0039] The code submission management system may include several clients. This embodiment takes a single client for code submission as an example. Users may use any client for code submission according to actual conditions.

[0040] The server may include a code library, which may include several code libraries corresponding to different tasks. Each code library may include several code paths. The critical path may be configured by the implementer. The code submission under the critical path is the code submission that needs to be reviewed.

[0041] The password book can be stored in the server, and the password book can be used to detect whether the target code has been reviewed by the target personnel.

[0042] The target path may refer to the corresponding path in the server when the client submits the code to the server, the change number may refer to the version number of the code, and the code description information may be used to describe the basic properties of the code. In this embodiment, the code description information includes password information. When the client does not enter the password information, the password information is empty.

[0043] Specifically, when the client submits the target code for the first time, the password book must not contain the change number. Therefore, after the client submits the target code for the first time, the password information corresponding to the change number will be generated, and the change number and its corresponding password information will be added to the password book, and the change number and its corresponding password information will be sent to the target personnel set.

[0044] Since the password information is a randomly generated string, the client must go through the target person to obtain the password information. Therefore, after the target person fails to submit the target code for the first time, it is necessary to apply for the password information from any target person. The application process is the review process. The target person can inform the client of the password information after the target code is reviewed and passed.

[0045] After applying for the password information, the client updates the password information to the code description information and submits the target code again. At this time, the password book already contains the change number, so the password information corresponding to the change number can be determined in the password book, and the detection code description information also contains the password information, so the target code can be submitted to the target path in the server normally.

[0046] In a specific implementation, the server includes a plurality of paths, and at least one path is configured as a critical path.

[0047] Among them, the critical path can be configured by the implementer. When all paths are not critical paths, the code submission management system in this embodiment is consistent with the conventional code management system. Therefore, this embodiment is described as a case where there is at least one path configured as a critical path.

[0048] In a specific implementation, when the computer program is executed by a processor, the following steps are also implemented:

[0049] S201: If there is no key path consistent with the target path, submit the target code to the target path in the server.

[0050] Among them, when all paths are not critical paths, the code submission management system in this embodiment is consistent with the conventional code management system, and the target code can be directly submitted to the target path in the server without review.

[0051] In a specific implementation, when the computer program is executed by a processor, the following steps are also implemented:

[0052] S301: When the change sequence number is empty, send second feedback information to the client.

[0053] When the change sequence number is empty, it indicates that the target code is not standardized, and the submission fails, and the second feedback information is sent to the client.

[0054] In a specific implementation manner, the second feedback information is used to remind the client to update the change sequence number and resubmit the target code.

[0055] In a specific implementation, step S103 includes the following steps:

[0056] S1031, when the change sequence number is not empty, parse the change sequence number to obtain the task name corresponding to the change sequence number;

[0057] S1032: Determine that the task corresponding to the task name is the task corresponding to the change sequence number.

[0058] The change number at least includes a task name. By parsing the change number, the task name corresponding to the change number can be obtained, and then the task corresponding to the task name can be determined, thereby determining the target personnel set corresponding to the task.

[0059] In a specific implementation, when the computer program is executed by a processor, the following steps are also implemented:

[0060] S401: If the code book does not include the change sequence number, send third feedback information to the client.

[0061] When the code book does not contain the change sequence number, it means that this submission is the first submission of the target code, and the target code has not been reviewed, so the submission fails, and the third feedback information is sent to the client.

[0062] In a specific implementation, the third feedback information is used to remind the client to resubmit the target code.

[0063] Among them, when the password book does not contain the change number, the client will receive the first feedback information and the third feedback information, thereby reminding the client to apply for password information from any target person in the target person set. After the application for password information is successful, the password information will be updated to the code description information and the target code will be resubmitted.

[0064] In this embodiment, by setting the critical path, the review process is only carried out when the target path of the code submission is the critical path, and the change number and code description information are detected in the review process to ensure that the submitted code is in a state that has passed the review of the target personnel, thereby improving the flexibility of code submission management, and notifying the target personnel of the code that needs to be reviewed in a timely manner, thereby improving the efficiency of code submission management.

[0065] Although some specific embodiments of the present invention have been described in detail by way of example, it will be appreciated by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present invention. It will also be appreciated by those skilled in the art that various modifications may be made to the embodiments without departing from the scope and spirit of the present invention. The scope of the present invention is defined by the appended claims.

Claims

1. A code submission management system, characterized in that: The system includes: a server, a client, a processor, and a memory storing a computer program, wherein the server includes a plurality of key paths and a code book, and when the computer program is executed by the processor, the following steps are implemented: S101, when the client submits the target code to the target path of the server, detecting whether there is a key path consistent with the target path, the target code corresponding to the change sequence number and code description information; S102, if there is a key path that is consistent with the target path, query the change sequence number corresponding to the target code; S103, when the change sequence number is not empty, parsing the change sequence number to obtain a task corresponding to the change sequence number; S104, obtaining a target personnel set corresponding to the task, wherein the target personnel set includes a plurality of target personnel for the task; S105, querying whether the code book contains the change sequence number; S106, if the password book does not contain the change sequence number, randomly generate a character string as the password information of the change sequence number; S107, adding the change sequence number and its corresponding password information to the password book; S108, sending the change sequence number and its corresponding password information to the target personnel set; S109, if the code book contains the change sequence number, determine the code information corresponding to the change sequence number in the code book; S110, detecting whether the code description information includes the password information; S111, if the code description information does not include the password information, sending first feedback information to the client, the first feedback information is used to remind the client to apply for the password information from the target personnel set, so as to update the password information to the code description information and resubmit the target code, wherein after any target personnel in the target personnel set reviews the target code and passes it, the password information is notified to the client; S112: If the code description information includes the password information, submit the target code to the target path in the server.

2. The code submission management system according to claim 1, characterized in that: The server includes several paths, and at least one path is configured as a critical path.

3. The code submission management system according to claim 1, characterized in that: When the computer program is executed by a processor, the following steps are also implemented: S201: If there is no key path consistent with the target path, submit the target code to the target path in the server.

4. The code submission management system according to claim 1, characterized in that: When the computer program is executed by a processor, the following steps are also implemented: S301: When the change sequence number is empty, send second feedback information to the client.

5. The code submission management system according to claim 4, characterized in that: The second feedback information is used to remind the client to update the change sequence number and resubmit the target code.

6. The code submission management system according to claim 1, characterized in that: Step S103 includes the following steps: S1031, when the change sequence number is not empty, parse the change sequence number to obtain the task name corresponding to the change sequence number; S1032: Determine that the task corresponding to the task name is the task corresponding to the change sequence number.

7. The code submission management system according to claim 1, characterized in that: When the computer program is executed by a processor, the following steps are also implemented: S401: If the code book does not include the change sequence number, send third feedback information to the client.

8. The code submission management system according to claim 7, characterized in that: The third feedback information is used to remind the client to resubmit the target code.

Images