Development quality management method and device, electronic equipment and storage medium

Abstract

The invention provides a development quality management method and device, electronic equipment and a storage medium. The method comprises the following steps: monitoring development information of a development event on a project platform and / or a code warehouse through a monitoring application program interface; wherein the development information at least comprises developer information and field information of the development event; the field information is used for indicating whether the development event meets a preset development quality management requirement or not; and if the field information does not meet the preset development quality management requirement, sending a reminding message to the developer through the project platform. According to the scheme provided by the invention, the development information of the development event on the project platform and / or the code warehouse is monitored through the monitoring application program interface, so that the developer information and the field information corresponding to the development event are obtained; when the field information does not meet the preset development quality management requirement, a reminding message can be sent to a corresponding developer; therefore, development event monitoring and risk reminding in the whole development process are realized.

Description

Technical Field

[0001] The present disclosure relates to the technical field of development quality management, and in particular to a development quality management method and apparatus, an electronic device, and a storage medium. Background Art

[0002] In related technologies, software development for specific needs often requires the collaboration of multiple people. Before multiple people complete the development collaboratively, a standard operating procedure (SOP) for the project is usually established in advance on a project platform (such as the Feishu project platform). The SOP includes multiple development milestones for the requirements, such as the pre-launch, launch, and post-launch milestones of the software.

[0003] However, related technologies do not provide monitoring and risk reminders for development events with specific requirements. Summary of the Invention

[0004] The present disclosure provides a development quality management method and device, an electronic device, and a storage medium.

[0005] According to a first aspect of the present disclosure, a development quality management method is provided, comprising:

[0006] Monitoring development information of development events on the project platform and / or the code repository through a monitoring application program interface; wherein the development information includes at least developer information and field information of the development event; the field information is used to indicate whether the development event meets the preset development quality management requirements;

[0007] If the field information does not meet the preset development quality management requirements, a reminder message is sent to the developer through the project platform.

[0008] In one embodiment, monitoring development information of development events on a project platform through a monitoring application program interface includes:

[0009] Monitoring development information of development events corresponding to pre-launch nodes on the project platform through a monitoring application program interface; the development events corresponding to pre-launch nodes include at least one of a technical solution link event or a functional test case event;

[0010] Alternatively, the development information of the development event corresponding to the launch node on the project platform is monitored through the monitoring application program interface; the development event corresponding to the launch node includes at least one of a high-priority defect event, an acceptance standard event, a review event, or a personnel event corresponding to the requirement;

[0011] Alternatively, development information of development events corresponding to the post-launch node is monitored on the project platform by monitoring the application program interface; the development events corresponding to the post-launch node include at least one of the demand arrival at the online node event, the online document event, the online event notification event or the test event.

[0012] In one embodiment, the field information does not meet the preset development quality management requirements, including:

[0013] When the technical solution link uploaded by the developer corresponding to the field information in the development information of the technical solution link event is invalid, the preset development quality management requirement is not met; when the functional test case uploaded by the developer corresponding to the field information in the development information of the required functional test case event is invalid, the preset development quality management requirement is not met;

[0014] When there is a high-priority defect in the technical solution uploaded by the developer corresponding to the field information in the development information of the high-priority defect event, the preset development quality management requirement is not met; when the acceptance standard of the technical solution uploaded by the developer corresponding to the field information in the development information of the acceptance standard event is unclear, the preset development quality management requirement is not met; when the technical solution uploaded by the developer corresponding to the field information in the development information of the review event has not been reviewed, the preset development quality management requirement is not met; when the developer corresponding to the field information in the development information of the personnel event corresponding to the requirement is not related to the technical personnel in the technical solution, the preset development quality management requirement is not met;

[0015] When the field information requirement in the development information of the demand reaching the online node event does not reach the online node, the preset development quality management requirement is not met; when the field information in the development information of the online document event does not have an online document, the preset development quality management requirement is not met; when the field information in the development information of the online event notification event does not send an online notification, the preset development quality management requirement is not met; when the field information in the development information of the test event does not pass the test before going online, the preset development quality management requirement is not met.

[0016] In one embodiment, monitoring development information of development events on a code repository through a monitoring application program interface includes:

[0017] Listen to at least one of the following events: push rule configuration events, pipeline merge specification events, merge request approval comment events, code base and requirement association events, request code review comment validity events, or code base allowed merge default branch events through the listening application interface.

[0018] In one embodiment, the field information does not meet the preset development quality management requirements, including:

[0019] When the field information in the development information of the push rule configuration event is not configured with a push rule, the preset development quality management requirement is not met;

[0020] When the field information in the development information of the pipeline merging specification event does not open the pipeline merging specification, the preset development quality management requirement is not met;

[0021] When the field information in the development information of the merge request approval comment event does not contain a merge request approval comment, the preset development quality management requirement is not met;

[0022] When the field information code repository in the development information of the code repository and requirement association event is not associated with the requirement, the preset development quality management requirement is not met;

[0023] When the field information in the development information of the code review comment validity event is invalid, the preset development quality management requirement is not met;

[0024] The code library allows the field information in the development information of the default branch event to be merged. When the code library allows the default branch to be merged, the preset development quality management requirement is not met.

[0025] In one embodiment, sending a reminder message to the developer through the project platform includes:

[0026] Determine whether a development event that does not currently meet the preset development quality management requirements has received a repair notification;

[0027] If the judgment result is yes, a repair notification is sent to the developer through the project platform;

[0028] If the judgment result is no, a repair-required notification is sent to the developer via the project platform.

[0029] In one embodiment, after sending a reminder message to the developer via the project platform, the method further includes:

[0030] Development events that do not meet the preset development quality management requirements are written into the corresponding database.

[0031] According to a second aspect of the present disclosure, there is provided a development quality management apparatus, comprising:

[0032] A monitoring unit, configured to monitor development information of development events on a project platform and / or a code repository via a monitoring application program interface; wherein the development information includes at least developer information and field information of the development event; and the field information is used to indicate whether the development event meets the preset development quality management requirements.

[0033] A sending unit is used to send a reminder message to the developer through the project platform if the field information does not meet the preset development quality management requirements.

[0034] According to a third aspect of the present disclosure, there is provided an electronic device, including:

[0035] at least one processor; and

[0036] a memory communicatively connected to the at least one processor; wherein,

[0037] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to perform the method described in the first aspect.

[0038] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to enable the computer to execute the method described in the first aspect.

[0039] The present disclosure provides a development quality management method and apparatus, an electronic device, and a storage medium. The method comprises: monitoring development information of development events on a project platform and / or a code repository via an application program interface; wherein the development information includes at least developer information and field information of the development event; the field information is used to indicate whether the development event meets preset development quality management requirements; and if the field information does not meet the preset development quality management requirements, sending a reminder message to the developer via the project platform.

[0040] The solution provided by the present invention monitors the development information of development events on the project platform and / or the code repository through the monitoring of the application program interface, thereby obtaining the developer information and field information of the corresponding development event; and then, when the field information does not meet the preset development quality management requirements, it can send a reminder message to the corresponding developer; thereby realizing development event monitoring and risk reminders throughout the entire development process.

[0041] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings are provided to facilitate a better understanding of the present invention and do not constitute a limitation of the present disclosure.

[0043] Figure 1 A flowchart of a development quality management method provided by an embodiment of the present disclosure;

[0044] Figure 2 A schematic diagram of the structure of a development quality management device provided by an embodiment of the present disclosure;

[0045] Figure 3 A schematic block diagram of an exemplary electronic device provided for an embodiment of the present disclosure. DETAILED DESCRIPTION

[0046] The following description of exemplary embodiments of the present disclosure is made in conjunction with the accompanying drawings, including various details of the embodiments of the present disclosure to facilitate understanding. These details should be considered as merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present disclosure. Similarly, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0047] The present disclosure provides a development quality management method, device, electronic device, and storage medium. The method monitors development information of development events on a project platform and / or a code repository via an Application Programming Interface (API), thereby acquiring developer information and field information corresponding to the development event. Furthermore, when the field information does not meet preset development quality management requirements, a reminder message can be sent to the corresponding developer, thereby enabling development event monitoring and risk reminders throughout the entire development process.

[0048] Based on this, an embodiment of the present disclosure provides a development quality management method.

[0049] like Figure 1 As shown, the development quality management method provided by the embodiment of the present disclosure includes the following steps:

[0050] Step 101: monitor first development information of development events on a project platform through a first monitoring API, and / or monitor second development information of development events on a code repository through a second monitoring API; monitor development information of development events on the project platform and / or on the code repository through the monitoring API;

[0051] In one embodiment, the development information includes at least developer information and field information of the development event.

[0052] In one embodiment, the field information is used to indicate whether the development event meets the preset development quality management requirements;

[0053] In one embodiment, the development event refers to a development event for a specific requirement; each specific requirement can be associated with multiple development events. For example, on project platforms such as Lark, a standard operating procedure (SOP) for specific requirements can be pre-implemented. The development events for a specific requirement can include development events for the node before uploading, the node during uploading, and the node after uploading.

[0054] In one embodiment, the development events of the development node before uploading may include technical solution link events or test case events; the development events of the node during uploading may include high-priority defect events, acceptance standard events, review events or personnel events corresponding to requirements; the development events of the node after uploading include requirements reaching the online node event, online document event, online event notification event or test event.

[0055] In one embodiment, the developer refers to the developer corresponding to each development event, or the person who mainly develops the corresponding event, wherein different development events may correspond to the same developer.

[0056] In one embodiment, different developers can be identified and distinguished by their IDs registered on the project platform.

[0057] In one embodiment, the ID corresponding to the developer corresponding to a development event may represent a specific person or a group consisting of multiple people.

[0058] In one embodiment, the field information of a development event is used to indicate the audit result information of the development event after the reviewer of the corresponding node has reviewed the development event. For example, in a technical solution link event, the field information corresponding to the technical solution link event is the field information indicating whether the technical solution link is valid. Specifically, when a developer uploads a technical solution link to the project platform for the first time, the reviewer verifies whether the technical solution link is valid. If valid, the field flag corresponding to the technical solution link is updated to indicate valid; if invalid, the field flag corresponding to the technical solution link is updated to indicate invalid.

[0059] In one embodiment, code repository configuration information may include at least one of the following: Push Rule configuration information for the code repository, Pipeline merge specification information, Merge Request (MR) approval comment information, code repository and requirement association information, Code Review (CR) comment validity information, or code repository merge-allowed default branch information. Correspondingly, code repository development events include at least one of the following: Push Rule configuration events, Pipeline merge specification events, MR approval comment events, code repository and requirement association events, CR comment validity events, or code repository merge-allowed default branch events.

[0060] Step 102: If the field information does not meet the preset development quality management requirements, a reminder message is sent to the developer through the project platform.

[0061] In one embodiment, taking the Feishu project platform as an example, if the field information does not meet the preset development quality management requirements, a reminder message can be sent to the corresponding developer in the form of a dialogue based on the developer information of the corresponding development event obtained in step 101.

[0062] In one embodiment, taking the technical solution link event as an example, the reminder information may be in the form of "Illegal Operation Reminder Notice - Technical Solution Link is Non-compliant". The reminder information may also include the name of the corresponding specific requirement, the address of the invalid technical solution link, etc.

[0063] In one embodiment, if the corresponding developer has fixed the corresponding violation, for example, the field identifier corresponding to the technical solution link has been updated from an invalid identifier to a valid identifier, a reminder message that the violation has been fixed can be sent to the corresponding developer.

[0064] In one embodiment, the reminder message that the illegal operation has been repaired may also include the name of the corresponding specific requirement, the address of the invalid technical solution link, the address of the repaired technical solution link, etc.

[0065] The development quality management method provided by the present disclosure includes: monitoring the development information of development events on the project platform and / or the code repository through a monitoring API; wherein the development information includes at least the developer information and field information of the development event; the field information is used to indicate whether the development event meets the preset development quality management requirements; if the field information does not meet the preset development quality management requirements, a reminder message is sent to the developer through the project platform.

[0066] The solution provided by the present invention obtains the developer information and field information of the corresponding development event by monitoring the API, monitoring the project platform and / or monitoring the development information of the development event on the code repository; and then, when the field information does not meet the preset development quality management requirements, it can send a reminder message to the corresponding developer, thereby realizing development event monitoring and risk reminders throughout the entire development process.

[0067] In one embodiment, monitoring development information of development events on a project platform through a monitoring API includes:

[0068] Monitoring development information of development events corresponding to pre-launch nodes on the project platform through a monitoring application program interface; the development events corresponding to pre-launch nodes include at least one of a technical solution link event or a functional test case event;

[0069] In one embodiment, taking the Feishu project platform as an example, the monitoring API may be a monitoring interface for accessing the storage space corresponding to Feishu.

[0070] In one embodiment, the field information in the development information of the technical solution link event is used to indicate whether the technical solution link uploaded by the corresponding developer is valid, and the field information in the development information of the requirement function test case event is used to indicate whether the corresponding developer uploads a function test case.

[0071] In one embodiment, the field information in the development information of the technical solution link event indicates that the preset development quality management requirement is satisfied when the technical solution link uploaded by the corresponding developer is valid, and the field information in the development information of the requirement function test case event indicates that the preset development quality management requirement is satisfied when the function test case uploaded by the corresponding developer is valid;

[0072] Alternatively, the development information of the development event corresponding to the launch node on the project platform is monitored through the monitoring application program interface; the development event corresponding to the launch node includes at least one of a high-priority defect event, an acceptance standard event, a review event, or a personnel event corresponding to the requirement;

[0073] In one embodiment, the field information in the development information of the high-priority defect event is used to indicate whether there are high-priority defects in the technical solution uploaded by the corresponding developer, the field information in the development information of the acceptance standard event is used to indicate whether the acceptance standards in the technical solution uploaded by the corresponding developer are clear, the field information in the development information of the review event is used to indicate whether the technical solution uploaded by the corresponding developer has been reviewed, and the field information in the development information of the personnel event corresponding to the demand is used to indicate whether the corresponding developer is related to the technical personnel in the technical solution.

[0074] In one embodiment, the field information in the development information of the high-priority defect event indicates that the preset development quality management requirement is met when there are no high-priority defects in the technical solution uploaded by the corresponding developer; the field information in the development information of the acceptance standard event indicates that the preset development quality management requirement is met when the acceptance standard in the technical solution uploaded by the corresponding developer is clear; the field information in the development information of the review event indicates that the preset development quality management requirement is met when the technical solution uploaded by the corresponding developer is reviewed; and the field information in the development information of the personnel event corresponding to the requirement indicates that the preset development quality management requirement is met when the corresponding developer is related to the technical personnel in the technical solution.

[0075] Alternatively, development information of development events corresponding to the post-launch node is monitored on the project platform by monitoring the application program interface; the development events corresponding to the post-launch node include at least one of the demand arrival at the online node event, the online document event, the online event notification event or the test event.

[0076] In one embodiment, the field information in the development information of the demand reaching the online node event is used to indicate whether the online node has been reached, the field information in the development information of the online document event is used to indicate whether there is an online document, the field information in the development information of the online event notification event is used to indicate whether an online notification is sent, and the field information in the development information of the test event is used to indicate whether the test has passed before going online.

[0077] In one embodiment, the field information in the development information of the demand arriving at the online node event indicates that the preset development quality management requirement is met when the online node is reached, the field information in the development information of the online document event indicates that the preset development quality management requirement is met when the online document exists, the field information in the development information of the online event notification event indicates that the preset development quality management requirement is met when the online notification is sent, and the field information in the development information of the test event indicates that the preset development quality management requirement is met when the test is passed before going online.

[0078] In one embodiment, the field information does not meet the preset development quality management requirements, including:

[0079] When the technical solution link uploaded by the developer corresponding to the field information in the development information of the technical solution link event is invalid, the preset development quality management requirement is not met; when the functional test case uploaded by the developer corresponding to the field information in the development information of the required functional test case event is invalid, the preset development quality management requirement is not met;

[0080] When there is a high-priority defect in the technical solution uploaded by the developer corresponding to the field information in the development information of the high-priority defect event, the preset development quality management requirement is not met; when the acceptance standard of the technical solution uploaded by the developer corresponding to the field information in the development information of the acceptance standard event is unclear, the preset development quality management requirement is not met; when the technical solution uploaded by the developer corresponding to the field information in the development information of the review event has not been reviewed, the preset development quality management requirement is not met; when the developer corresponding to the field information in the development information of the personnel event corresponding to the requirement is not related to the technical personnel in the technical solution, the preset development quality management requirement is not met;

[0081] When the field information requirement in the development information of the demand reaching the online node event does not reach the online node, the preset development quality management requirement is not met; when the field information in the development information of the online document event does not have an online document, the preset development quality management requirement is not met; when the field information in the development information of the online event notification event does not send an online notification, the preset development quality management requirement is not met; when the field information in the development information of the test event does not pass the test before going online, the preset development quality management requirement is not met.

[0082] In one embodiment, when developing for a specific requirement, the corresponding software developed by the developer usually needs to be uploaded to a code repository. Common code repositories usually have version control functions, such as the gitlab code repository, so that developers can update the version of the corresponding code at any time.

[0083] In order to enhance the adaptability of this disclosure, the parameters in the code repository should also be monitored, and risk warnings should be issued for non-compliant parameters.

[0084] Based on this, in one embodiment,

[0085] Use the monitoring API to monitor development events in the code repository, including:

[0086] Listen to at least one of the following events: code repository push rule configuration events, pipeline merge specification events, merge request approval comment events, code repository and requirement association events, request code review comment validity events, or code repository default branch merge allowed events through the listening API.

[0087] In one embodiment, different interfaces for accessing specific fields of the code repository may be pre-created, and the project management platform may access the specific fields of the code repository through the interfaces, thereby obtaining associated data information of development events on the code repository.

[0088] In one embodiment, the code repository manager refers to the code repository manager corresponding to each development event, wherein different development events may correspond to the same developer.

[0089] In one embodiment, the field information does not meet the preset development quality management requirements, including:

[0090] When the field information in the development information of the push rule configuration event is not configured with a push rule, the preset development quality management requirement is not met; when the field information in the development information of the pipeline merging specification event does not open the pipeline merging specification, the preset development quality management requirement is not met; when the field information in the development information of the merge request approval comment event does not have a merge request approval comment, the preset development quality management requirement is not met; when the field information in the development information of the code library and requirement association event indicates that the code library is not associated with the requirement, the preset development quality management requirement is not met; when the field information in the development information of the request code review comment validity event indicates that the request code review comment is invalid, the preset development quality management requirement is not met; when the field information in the development information of the code library allows merging into the default branch event, the preset development quality management requirement is not met when the code library allows merging into the default branch.

[0091] In one embodiment, taking the development event as an example of a push rule configuration event for a code repository, the field information of the development event indicates whether the code repository is configured with push rules. If the field information indicates that the code repository has configured push rules, it is determined that the data corresponding to the development information meets the preset development quality management requirements; otherwise, it is determined that it does not meet the requirements.

[0092] In one embodiment, taking the development event as an example of a pipeline merging specification event of a code repository, the field information of the development event indicates whether the code repository has opened the pipeline merging specification. If the field information indicates that the code repository has opened the pipeline merging specification, it is determined that the data corresponding to the development information meets the preset development quality management requirements; otherwise, it is determined that it does not meet the requirements.

[0093] In one embodiment, taking the development event as a merge request approval comment event as an example, the field information of the development event indicates whether there is a merge request approval comment. If the field information indicates that there is a merge request approval comment, it is determined that the data corresponding to the associated data information meets the preset development quality management requirements; otherwise, it is determined that it does not meet the requirements.

[0094] In one embodiment, taking the development event as an example of a code library and requirement association event of a code warehouse, the field information of the development event indicates whether the code library is associated with the requirement. If the field information indicates that the code library is associated with the requirement, it is determined that the data corresponding to the associated data information meets the preset development quality management requirements; otherwise, it is determined that it does not meet the requirements.

[0095] In one embodiment, taking the development event as a request code review comment validity event as an example, the field information of the development event indicates whether the request code review comment is valid. If the field information indicates that the request code review comment is valid, it is determined that the data corresponding to the associated data information meets the preset development quality management requirements; otherwise, it is determined that it does not meet the requirements.

[0096] In one embodiment, sending a reminder message to the corresponding developer through the project platform includes:

[0097] Determine whether a development event that does not currently meet the preset development quality management requirements has received a repair notification;

[0098] If the judgment result is yes, a repair notification is sent to the corresponding developer through the project platform;

[0099] If the judgment result is no, a repair-required notification is sent to the corresponding developer through the project platform.

[0100] In one embodiment, after step 102, the development quality management method provided by the present disclosure further includes:

[0101] Development events that do not meet the preset development quality management requirements are written into the corresponding database.

[0102] In one embodiment, the database may be divided into different violation tables, such as a project platform violation table and a code repository violation table.

[0103] In one embodiment, different rows in the violation table may represent different development events, and different columns may represent the developer corresponding to the row, field information, whether it is a violation, whether it is repaired, whether it is notified, etc.

[0104] In order to implement the development quality management method provided by the embodiment of the present disclosure, the embodiment of the present disclosure also provides a development quality management device.

[0105] like Figure 2 As shown, the development quality management device 200 provided by the embodiment of the present disclosure includes:

[0106] The listening unit 201 is configured to listen to development information of a development event on a project platform and / or a code repository by using a listening API; the development information at least includes developer information and field information of the development event; the field information is used to indicate whether the development event meets the preset development quality management requirement.

[0107] The sending unit 202 is configured to send a reminding message to the developer through the project platform if the field information does not meet the preset development quality management requirement.

[0108] In an embodiment, the listening unit 201 is specifically configured to:

[0109] The listening unit 201 is configured to listen to development information of a development event corresponding to a pre-online node on the project platform by using the listening API; the development event corresponding to the pre-online node includes at least one of a technical solution link event or a function test case event.

[0110] Alternatively, the listening unit 201 is configured to listen to development information of a development event corresponding to an online node on the project platform by using the listening API; the development event corresponding to the online node includes at least one of a high-priority defect event, an acceptance standard event, a review event or a demand corresponding personnel event.

[0111] Alternatively, the listening unit 201 is configured to listen to development information of a development event corresponding to a post-online node on the project platform by using the listening API; the development event corresponding to the post-online node includes at least one of a demand reaching an online node event, an online document event, an online event notification event or a test event.

[0112] In an embodiment, the listening unit 201 is specifically configured to:

[0113] The field information in the development information of the technical solution link event corresponds to an invalid technical solution link uploaded by a developer, and the preset development quality management requirement is not met; the field information in the development information of the demand function test case event corresponds to an invalid function test case uploaded by a developer, and the preset development quality management requirement is not met.

[0114] When there is a high-priority defect in the technical solution uploaded by the developer corresponding to the field information in the development information of the high-priority defect event, the preset development quality management requirement is not met; when the acceptance standard of the technical solution uploaded by the developer corresponding to the field information in the development information of the acceptance standard event is unclear, the preset development quality management requirement is not met; when the technical solution uploaded by the developer corresponding to the field information in the development information of the review event has not been reviewed, the preset development quality management requirement is not met; when the developer corresponding to the field information in the development information of the personnel event corresponding to the requirement is not related to the technical personnel in the technical solution, the preset development quality management requirement is not met;

[0115] When the field information requirement in the development information of the demand reaching the online node event does not reach the online node, the preset development quality management requirement is not met; when the field information in the development information of the online document event does not have an online document, the preset development quality management requirement is not met; when the field information in the development information of the online event notification event does not send an online notification, the preset development quality management requirement is not met; when the field information in the development information of the test event does not pass the test before going online, the preset development quality management requirement is not met.

[0116] In one embodiment, the monitoring unit 201 is specifically configured to:

[0117] Use the monitoring API to monitor at least one of the following events: code repository push rule configuration events, pipeline merge specification events, merge request approval comment events, code repository and requirement association events, request code review comment validity events, or code repository default branch merge allowed events.

[0118] In one embodiment, the monitoring unit 201 is specifically configured to:

[0119] When the field information in the development information of the push rule configuration event is not configured with a push rule, the preset development quality management requirement is not met;

[0120] When the field information in the development information of the pipeline merging specification event does not open the pipeline merging specification, the preset development quality management requirement is not met;

[0121] When the field information in the development information of the merge request approval comment event does not contain a merge request approval comment, the preset development quality management requirement is not met;

[0122] When the field information code repository in the development information of the code repository and requirement association event is not associated with the requirement, the preset development quality management requirement is not met;

[0123] When the field information in the development information of the code review comment validity event is invalid, the preset development quality management requirement is not met;

[0124] The code library allows the field information in the development information of the default branch event to be merged. When the code library allows the default branch to be merged, the preset development quality management requirement is not met.

[0125] In one embodiment, the sending unit 202 is specifically configured to:

[0126] Determine whether a development event that does not currently meet the preset development quality management requirements has received a repair notification;

[0127] If the judgment result is yes, a repair notification is sent to the developer through the project platform;

[0128] If the judgment result is no, a repair-required notification is sent to the developer via the project platform.

[0129] In one embodiment, the development quality management apparatus 200 provided by the embodiment of the present disclosure further includes a storage unit; the storage unit is configured to:

[0130] Development events that do not meet the preset development quality management requirements are written into the corresponding database.

[0131] It should be noted that the above explanation of the method embodiment is also applicable to the device of this embodiment, and the principles are the same, which is not limited in this embodiment.

[0132] According to an embodiment of the present disclosure, the present disclosure also provides an electronic device and a non-transitory computer-readable storage medium storing computer instructions.

[0133] Specifically, an embodiment of the present disclosure provides an electronic device, including:

[0134] at least one processor; and

[0135] a memory communicatively connected to the at least one processor; wherein,

[0136] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to perform the steps of the aforementioned development quality management method.

[0137] An embodiment of the present disclosure provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to execute the steps of the aforementioned development quality management method.

[0138] Figure 3A schematic block diagram of an example electronic device 300 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, in-vehicle devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are provided as examples only and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0139] like Figure 3 As shown, the electronic device 300 includes a computing unit 301, which can perform various appropriate actions and processes according to a computer program stored in a ROM (Read-Only Memory) 302 or a computer program loaded from a storage unit 308 into a RAM (Random Access Memory) 303. Various programs and data required for the operation of the device 300 can also be stored in the RAM 303. The computing unit 301, ROM 302, and RAM 303 are connected to each other via a bus 304. An I / O (Input / Output) interface 305 is also connected to the bus 304.

[0140] Multiple components in device 300 are connected to I / O interface 305, including: input unit 304, such as a keyboard, mouse, etc.; output unit 307, such as various types of displays, speakers, etc.; storage unit 308, such as a magnetic disk, optical disk, etc.; and communication unit 309, such as a network card, modem, wireless communication transceiver, etc. Communication unit 309 allows device 300 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0141] The computing unit 301 can be a variety of general-purpose and / or specialized processing components with processing and computing capabilities. Some examples of the computing unit 301 include, but are not limited to, a CPU (Central Processing Unit), a GPU (Graphic Processing Unit), various specialized AI (Artificial Intelligence) computing chips, various computing units that run machine learning model algorithms, a DSP (Digital Signal Processor), and any suitable processor, controller, microcontroller, etc. The computing unit 301 performs the various methods and processes described above, such as the development quality management method. For example, in some embodiments, the development quality management method can be implemented as a computer software program that is tangibly embodied in a machine-readable medium, such as the storage unit 308. In some embodiments, part or all of the computer program can be loaded and / or installed on the device 300 via the ROM 302 and / or the communication unit 309. When the computer program is loaded into the RAM 303 and executed by the computing unit 301, one or more steps of the method described above can be performed. Alternatively, in other embodiments, the computing unit 301 may be configured to execute the aforementioned development quality management method in any other appropriate manner (for example, by means of firmware).

[0142] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, FPGAs (Field Programmable Gate Arrays), ASICs (Application-Specific Integrated Circuits), ASSPs (Application-Specific Standard Products), SOCs (System on Chips), CPLDs (Complex Programmable Logic Devices), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special-purpose or general-purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0143] The program code for implementing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0144] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or apparatus. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing. More specific examples of machine-readable storage media may include an electrical connection based on one or more wires, a portable computer disk, a hard disk, RAM, ROM, EPROM (Electrically Programmable Read-Only-Memory) or flash memory, optical fiber, CD-ROM (Compact Disc Read-Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0145] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved. This is not a limitation herein.

[0146] The above specific embodiments do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure shall be included within the scope of protection of this disclosure.

Claims

1. A development quality management method, characterized in that: include: Monitoring development information of development events on the project platform and / or the code repository through a monitoring application program interface; wherein the development information includes at least developer information and field information of the development event; the field information is used to indicate whether the development event meets the preset development quality management requirements; If the field information does not meet the preset development quality management requirements, a reminder message is sent to the developer through the project platform.

2. The method according to claim 1, characterized in that Monitor development events on the project platform through the monitoring API, including: Monitoring development information of development events corresponding to pre-launch nodes on the project platform through a monitoring application program interface; the development events corresponding to pre-launch nodes include at least one of a technical solution link event or a functional test case event; Alternatively, the development information of the development event corresponding to the launch node on the project platform is monitored through the monitoring application program interface; the development event corresponding to the launch node includes at least one of a high-priority defect event, an acceptance standard event, a review event, or a personnel event corresponding to the requirement; Alternatively, development information of development events corresponding to the post-launch node is monitored on the project platform by monitoring the application program interface; the development events corresponding to the post-launch node include at least one of the demand arrival at the online node event, the online document event, the online event notification event or the test event.

3. The method according to claim 2, characterized in that The field information does not meet the preset development quality management requirements, including: When the technical solution link uploaded by the developer corresponding to the field information in the development information of the technical solution link event is invalid, the preset development quality management requirement is not met; When the functional test case uploaded by the developer corresponding to the field information in the development information of the required functional test case event is invalid, the preset development quality management requirement is not met; When there is a high-priority defect in the technical solution uploaded by the developer corresponding to the field information in the development information of the high-priority defect event, the preset development quality management requirement is not met; when the acceptance standard of the technical solution uploaded by the developer corresponding to the field information in the development information of the acceptance standard event is unclear, the preset development quality management requirement is not met; when the technical solution uploaded by the developer corresponding to the field information in the development information of the review event has not been reviewed, the preset development quality management requirement is not met; When the developer corresponding to the field information in the development information of the personnel event corresponding to the requirement is not related to the technical personnel in the technical solution, the preset development quality management requirement is not met; When the field information requirement in the development information of the demand reaching the online node event does not reach the online node, the preset development quality management requirement is not met; when the field information in the development information of the online document event does not have an online document, the preset development quality management requirement is not met; When the field information in the development information of the online event notification event does not send the online notification, the preset development quality management requirements are not met; when the field information in the development information of the test event does not pass the test before going online, the preset development quality management requirements are not met.

4. The method according to claim 1, wherein Monitor development events on the code repository through the monitoring API, including: Listen to at least one of the following events: push rule configuration events, pipeline merge specification events, merge request approval comment events, code base and requirement association events, request code review comment validity events, or code base allowed merge default branch events through the listening application interface.

5. The method according to claim 4, characterized in that The field information does not meet the preset development quality management requirements, including: When the field information in the development information of the push rule configuration event is not configured with a push rule, the preset development quality management requirement is not met; When the field information in the development information of the pipeline merging specification event does not open the pipeline merging specification, the preset development quality management requirement is not met; When the field information in the development information of the merge request approval comment event does not contain a merge request approval comment, the preset development quality management requirement is not met; When the field information code repository in the development information of the code repository and requirement association event is not associated with the requirement, the preset development quality management requirement is not met; When the field information in the development information of the code review comment validity event is invalid, the preset development quality management requirement is not met; The code library allows the field information in the development information of the default branch event to be merged. When the code library allows the default branch to be merged, the preset development quality management requirement is not met.

6. The method according to claim 1, characterized in that The sending of a reminder message to the developer through the project platform includes: Determine whether a development event that does not currently meet the preset development quality management requirements has received a repair notification; If the judgment result is yes, a repair notification is sent to the developer through the project platform; If the judgment result is no, a repair-required notification is sent to the developer via the project platform.

7. The method according to claim 1, characterized in that After sending the reminder message to the developer through the project platform, the method further includes: Development events that do not meet the preset development quality management requirements are written into the corresponding database.

8. A development quality management device, characterized in that: include: A monitoring unit, configured to monitor development information of development events on a project platform and / or a code repository via a monitoring application program interface; wherein the development information includes at least developer information and field information of the development event; and the field information is used to indicate whether the development event meets the preset development quality management requirements. A sending unit is used to send a reminder message to the developer through the project platform if the field information does not meet the preset development quality management requirements.

9. An electronic device comprising: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 7.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein: The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 7.

Images