CN113553262A - Code auditing method and device, electronic equipment and storage medium - Google Patents
Code auditing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113553262A CN113553262A CN202110831476.XA CN202110831476A CN113553262A CN 113553262 A CN113553262 A CN 113553262A CN 202110831476 A CN202110831476 A CN 202110831476A CN 113553262 A CN113553262 A CN 113553262A
- Authority
- CN
- China
- Prior art keywords
- code
- subtask
- task
- user
- review
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/101—Collaborative creation, e.g. joint development of products or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides a code auditing method, a code auditing device, electronic equipment and a storage medium, wherein the method comprises the following steps: responding to a code review subtask submitted by a first user, and inquiring the associated code review task based on the identification of a team cooperation list carried in the code review subtask; the code review sub-task corresponds to the unique identifier of the team cooperation order; if the associated first code auditing task is inquired, adding the code auditing subtask into the first code auditing task; and notifying the message of newly adding the code review subtask in the first code review task to at least one second user so that the at least one second user reviews the code to be reviewed carried in the code review subtask. According to the method and the device, the plurality of code review subtasks corresponding to the team cooperation list can be merged into the first code review task, and the first user can be informed to at least one second user when submitting a new code review subtask.
Description
Technical Field
The present application relates to the field of code auditing technologies, and in particular, to a code auditing method and apparatus, an electronic device, and a storage medium.
Background
At present, as internet technology enterprises pay more and more attention to developing operation and maintenance integration modes and practices thereof, how to continuously improve the quality of codes and software products also becomes a key determinant factor for continuously and flexibly delivering values. In the whole development activity of software products, code auditing is a main measure for improving the internal quality of software. Code review (review) is a method commonly used for discovering hidden errors or design defects in code when code written by a certain function development is reviewed by other programs.
At present, a scheme for code auditing by using a code auditing tool (e.g., update) is that a user submits a code to be audited to the code auditing tool for management, and the user can select the code to be audited to establish a review. However, this solution cannot establish a single review for a certain requirement, and requires the user to manually merge all code submissions of a requirement into a review. Also, when a reviewed user submits a new code, the reviewed user is unaware that the reviewed user has submitted the new code on top of the demand.
Disclosure of Invention
In view of the above, an object of the present application is to provide a code review method, apparatus, electronic device and storage medium, which can merge a plurality of code review subtasks corresponding to a team collaboration list into a first code review task, and notify at least one second user when the first user submits a new code review subtask.
According to a first aspect of the present application, an embodiment of the present application provides a code auditing method, including:
responding to a code review subtask submitted by a first user, and inquiring the associated code review task based on the identification of a team cooperation list carried in the code review subtask; wherein the code review subtask corresponds to a unique identifier of the team collaboration ticket;
if the associated first code auditing task is inquired, adding the code auditing subtask into the first code auditing task;
and notifying at least one second user of the message of newly adding the code auditing subtask in the first code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask.
In one possible implementation manner, in response to a code review subtask submitted by a first user, the step of querying an associated code review task based on an identifier of a team cooperation sheet carried in the code review subtask includes:
responding to a code audit subtask submitted by a first user, and triggering the operation of a preset program;
when the preset program runs, inquiring the identification of the team cooperation list carried in the code review subtask;
querying an associated code review task based on the identification of the team collaboration ticket.
In one possible embodiment, the method further comprises:
if the associated first code auditing task is not inquired, a second code auditing task is newly established; wherein the second code audit task is associated with an identification of the team collaboration ticket;
and adding the code auditing subtask into the second code auditing task.
In one possible embodiment, the method further comprises:
and notifying at least one second user of the message of adding the code auditing subtask in the second code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask.
In one possible embodiment, the method further comprises:
determining a team cooperation order carried in the code review subtask based on an identification of the team cooperation order;
and inquiring the name of at least one second user configured by the first user in the team cooperation list.
In one possible embodiment, the method further comprises: and generating a code auditing subtask based on the identification of the team cooperation list and the code to be audited submitted by the first user through the code version tool.
In one possible embodiment, the method further comprises: and displaying the audit state of each code audit subtask in the first code audit task/the second code audit task to the at least one second user.
According to a second aspect of the present application, an embodiment of the present application further provides a code auditing apparatus, including:
the query module is used for responding to a code review subtask submitted by a first user and querying a related code review task based on an identifier of a team cooperation list carried in the code review subtask; wherein the code review subtask corresponds to a unique identifier of the team collaboration ticket;
the adding module is used for adding the code review subtask into the first code review task if the associated first code review task is inquired;
and the notification module is used for notifying at least one second user of a message of newly adding the code review subtask in the first code review task so that the at least one second user reviews the code to be reviewed carried in the code review subtask.
According to a third aspect of the present application, an embodiment of the present application further provides an electronic device, including: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, and when the electronic device runs, the processor communicates with the storage medium through the bus, and the processor executes the machine-readable instructions to perform the steps in the first aspect or any possible implementation manner of the first aspect.
According to a fourth aspect of the present application, this application embodiment further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps in the first aspect or any possible implementation manner of the first aspect.
According to the code auditing method provided by the embodiment of the application, the code auditing subtask submitted by the first user is responded, and whether the code auditing task is established aiming at the team cooperation order can be searched through the identifier of the team cooperation order because the code auditing subtask corresponds to the unique identifier of the team cooperation order. Then, if a first code auditing task is established aiming at the team cooperation list, adding the code auditing subtask into the first code auditing task; in this way, a plurality of code review subtasks corresponding to the team cooperation sheet can be merged into the first code review task. And finally, notifying at least one second user of a message of newly adding the code auditing subtask in the first code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask. In this way, at least one second user may be notified when a new code review subtask is submitted by the first user. Therefore, the multiple code review subtasks corresponding to the team cooperation sheet can be merged into the first code review task, and the at least one second user can be notified when the first user submits a new code review subtask.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
FIG. 1 is a flowchart illustrating a code auditing method provided by an embodiment of the present application;
FIG. 2 shows a schematic diagram of a team collaboration sheet;
FIG. 3 is a schematic diagram illustrating an updated first code audit task;
FIG. 4 is a schematic diagram illustrating a message notification for adding a new code review subtask to a first code review task;
FIG. 5 is a diagram illustrating an audit status presentation for each code audit subtask of the first code audit task;
fig. 6 is a schematic structural diagram illustrating a code auditing apparatus according to an embodiment of the present application;
fig. 7 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for illustrative and descriptive purposes only and are not used to limit the scope of protection of the present application. Additionally, it should be understood that the schematic drawings are not necessarily drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be performed out of order, and steps without logical context may be performed in reverse order or simultaneously. One skilled in the art, under the guidance of this application, may add one or more other operations to, or remove one or more operations from, the flowchart.
In addition, the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that in the embodiments of the present application, the term "comprising" is used to indicate the presence of the features stated hereinafter, but does not exclude the addition of further features.
In the prior art, a scheme for code review by using a code review tool (e.g., an upgrade) is considered that a user submits a code to be reviewed to the code review tool for management, and the user can select the code to be reviewed to establish a review. However, this solution cannot establish a single review for a certain requirement, and requires the user to manually merge all code submissions of a requirement into a review. Also, when a reviewed user submits a new code, the reviewed user is unaware that the reviewed user has submitted the new code on top of the demand. Based on this, embodiments of the present application provide a code auditing method, apparatus, electronic device and storage medium, which are described below by way of embodiments.
To facilitate understanding of the present embodiment, a detailed description will be given first of all of a code auditing method disclosed in the embodiments of the present application.
Referring to fig. 1, fig. 1 is a flowchart illustrating a code auditing method according to an embodiment of the present disclosure. As shown in fig. 1, the method may include the steps of:
s101, responding to a code review subtask submitted by a first user, and inquiring a related code review task based on an identifier of a team cooperation order carried in the code review subtask; wherein the code review subtask corresponds to a unique identifier of the team collaboration ticket;
s102, if the associated first code auditing task is inquired, adding the code auditing subtask into the first code auditing task;
and S103, notifying at least one second user of a message of newly adding the code auditing subtask in the first code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask.
In step S101, the first user refers to a reviewed user, the second user refers to a review user, and the code review platform may be an update or other code review platforms, which is not specifically limited in this embodiment.
The team cooperation sheet is made by the first user as a maker, and the team cooperation sheet may be an easy cooperation sheet as shown in fig. 2, or may be another type of team cooperation sheet, which is not specifically limited in this embodiment. The team collaboration sheet has a unique identification, which may include a sheet number of the team collaboration sheet, such as the sheet number "101916" of the easy collaboration sheet shown in FIG. 2. In this embodiment, a plurality of second user options may be provided in the team collaborative flyer for the first user to select from, from which the first user may select one or more second users.
The code review subtask refers to a task generated by submitting one code review. Specifically, a code review subtask is generated based on the identification of the team collaboration list and the code to be reviewed submitted by the first user through the code version tool. The code version tool may refer to an SVN (version control system) or may be another code version tool, which is not specifically limited in this embodiment.
The code review task refers to the overall code review task created for the team work order, which may include one or more code review subtasks. In other words, the team collaboration sheet characterizes a requirement for which one or more code review subtasks are merged into the code review task.
In this step, in response to the code review subtask submitted by the first user, since the code review subtask corresponds to the unique identifier of the team collaboration list, it is possible to search whether a code review task has been created for the team collaboration list through the identifier of the team collaboration list.
Specifically, step S101 may include the following sub-steps:
s1011, responding to the code audit subtask submitted by the first user, and triggering the operation of a preset program;
s1012, inquiring the identification of the team cooperation list carried in the code review subtask when the preset program runs;
and S1013, inquiring the associated code auditing task based on the identification of the team cooperation bill.
In step S1011, a web application, i.e. a preset program, is configured, and the web application is triggered to run whenever the code to be reviewed is submitted. The preset program may refer to webhook of the upsource, but the embodiment is not limited thereto, and may be other hooks, such as svnhook, githiook, and the like.
In step S1012, assuming that the team cooperation form is an easy-to-cooperate form, when the web application runs, the easy-to-cooperate form is queried by using an easy-to-cooperate interface according to the log in the svn code submitted by the user, for example: the log at submission is "# 10001xxx function development", then the query easy collaboration ticket is 10001.
In step S1013, assuming that the code review platform is an update, and the team cooperation form is an easy cooperation form, querying whether a form number of the easy cooperation form is carried in a code review task through an interface provided by the update, so as to query whether the easy cooperation form has a code review task created.
In step S102, if the associated first code audit task is found, which indicates that the first code audit task has been created for the team cooperation sheet, the code audit subtask is added to the first code audit task. As shown in fig. 3, if an associated trunk is queried, the trunk associates a single number "101916" of the collaboration-ready list, and multiple code auditing subtasks have been created in the trunk for the collaboration-ready list, a new code auditing subtask "G-CR-11 #10196 [ program-independent ] V2006 engine" is updated into the trunk. And if a new code auditing subtask is submitted subsequently, continuing to combine the new code auditing subtask into the first code auditing task.
In step S103, preferably, a message of newly adding the code review subtask in the first code review task may be notified to at least one second user by using an automatic mail sending method. The embodiment is not limited to this, and other message notification manners, such as voice notification, short message notification, application notification, and the like, may also be adopted.
In this step, as shown in fig. 4, a message that the new code review subtask "G-CR-11 #10196 [ program-independent ] V2006 engine" is updated into the trunk may be notified to the at least one second user in an automatic mail sending manner, so that the at least one second user reviews the code of the new code review subtask "G-CR-11 #10196 [ program-independent ] V2006 engine".
In one possible implementation, the audit status of each code audit subtask among the first/second code audit tasks is presented to the at least one second user. As shown in fig. 5, each circle represents a code review subtask, an open circle represents that the code review subtask has been reviewed, and a solid circle represents that the code review subtask has not been reviewed. The embodiment is not limited to this, and the audit state of each code audit subtask in the first code audit task/the second code audit task may also be presented to the at least one second user in other presentation manners.
In a possible implementation mode, if the related first code auditing task is not inquired, a second code auditing task is newly established; wherein the second code audit task is associated with an identification of the team collaboration ticket; and adding the code auditing subtask into the second code auditing task. And notifying at least one second user of the message of adding the code auditing subtask in the second code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask. In this embodiment, the first code audit task is not queried, which means that a code audit task has not been created for the team cooperation ticket, and then a second code audit task is created for the team cooperation ticket, and the code audit subtask is added to the second code audit task and notified to at least one second user.
In a possible implementation manner, before step S103, the method further includes: firstly, determining a team cooperation order based on the identification of the team cooperation order carried in the code review subtask; and inquiring the name of at least one second user configured by the first user in the team cooperation list. The embodiment can read the easy collaboration list based on the list number of the easy collaboration list, and query the name of at least one second user pre-configured by the first user from the easy collaboration list, so that the second user needing to be notified by the message can be determined.
According to the code auditing method provided by the embodiment of the application, the code auditing subtask submitted by the first user is responded, and whether the code auditing task is established aiming at the team cooperation order can be searched through the identifier of the team cooperation order because the code auditing subtask corresponds to the unique identifier of the team cooperation order. Then, if a first code auditing task is established aiming at the team cooperation list, adding the code auditing subtask into the first code auditing task; in this way, a plurality of code review subtasks corresponding to the team cooperation sheet can be merged into the first code review task. And finally, notifying at least one second user of a message of newly adding the code auditing subtask in the first code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask. In this way, at least one second user may be notified when a new code review subtask is submitted by the first user. Therefore, the multiple code review subtasks corresponding to the team cooperation sheet can be merged into the first code review task, and the at least one second user can be notified when the first user submits a new code review subtask.
Based on the same technical concept, embodiments of the present application further provide a code auditing apparatus, an electronic device, a computer storage medium, and the like, which can be specifically referred to in the following embodiments.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a code auditing apparatus according to an embodiment of the present application. As shown in fig. 6, the apparatus may include:
the query module 10 is configured to respond to a code review subtask submitted by a first user, and query a related code review task based on an identifier of a team cooperation form carried in the code review subtask; wherein the code review subtask corresponds to a unique identifier of the team collaboration ticket;
the adding module 20 is configured to add the code review subtask to the first code review task if the associated first code review task is queried;
and the notifying module 30 is configured to notify at least one second user of a message that the code review subtask is newly added to the first code review task, so that the at least one second user reviews the code to be reviewed, which is carried in the code review subtask.
In one possible implementation, the query module 10 may include:
the triggering unit is used for responding to the code audit subtask submitted by the first user and triggering the operation of a preset program;
the first query unit is used for querying the identifier of the team cooperation list carried in the code review subtask when the preset program runs;
and the second query unit is used for querying the associated code auditing task based on the identification of the team cooperation sheet.
In one possible embodiment, the joining module 20 is further configured to:
if the associated first code auditing task is not inquired, a second code auditing task is newly established; wherein the second code audit task is associated with an identification of the team collaboration ticket;
and adding the code auditing subtask into the second code auditing task.
In one possible implementation, notification module 30 is further configured to:
and notifying at least one second user of the message of adding the code auditing subtask in the second code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask.
In one possible implementation, notification module 30 is further configured to:
determining a team cooperation order carried in the code review subtask based on an identification of the team cooperation order;
and inquiring the name of at least one second user configured by the first user in the team cooperation list.
In one possible embodiment, the query module 10 is further configured to: and generating a code auditing subtask based on the identification of the team cooperation list and the code to be audited submitted by the first user through the code version tool.
In one possible implementation, notification module 30 is further configured to: and displaying the audit state of each code audit subtask in the first code audit task/the second code audit task to the at least one second user.
An embodiment of the present application discloses an electronic device, as shown in fig. 7, including: a processor 701, a memory 702 and a bus 703, wherein the memory 702 stores machine-readable instructions executable by the processor 701, when the electronic device is operated, the processor 701 and the memory 702 communicate with each other through the bus 703, and the processor 701 executes the machine-readable instructions to perform the following steps:
responding to a code review subtask submitted by a first user, and inquiring the associated code review task based on the identification of a team cooperation list carried in the code review subtask; wherein the code review subtask corresponds to a unique identifier of the team collaboration ticket;
if the associated first code auditing task is inquired, adding the code auditing subtask into the first code auditing task;
and notifying at least one second user of the message of newly adding the code auditing subtask in the first code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask.
In one possible implementation, the step of querying, by the processor 701, an associated code review task based on an identification of a team collaboration list carried in a code review subtask in response to the code review subtask submitted by a first user includes:
responding to a code audit subtask submitted by a first user, and triggering the operation of a preset program;
when the preset program runs, inquiring the identification of the team cooperation list carried in the code review subtask;
querying an associated code review task based on the identification of the team collaboration ticket.
In one possible implementation, the processor 701 is further configured to perform:
if the associated first code auditing task is not inquired, a second code auditing task is newly established; wherein the second code audit task is associated with an identification of the team collaboration ticket;
and adding the code auditing subtask into the second code auditing task.
In one possible implementation, the processor 701 is further configured to perform:
and notifying at least one second user of the message of adding the code auditing subtask in the second code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask.
In one possible implementation, the processor 701 is further configured to perform:
determining a team cooperation order carried in the code review subtask based on an identification of the team cooperation order;
and inquiring the name of at least one second user configured by the first user in the team cooperation list.
In one possible implementation, the processor 701 is further configured to perform: and generating a code auditing subtask based on the identification of the team cooperation list and the code to be audited submitted by the first user through the code version tool.
In one possible implementation, the processor 701 is further configured to perform: and displaying the audit state of each code audit subtask in the first code audit task/the second code audit task to the at least one second user.
The computer program product of the code auditing method provided by the embodiment of the present application includes a computer readable storage medium storing a nonvolatile program code executable by a processor, where instructions included in the program code may be used to execute the method described in the foregoing method embodiment, and specific implementation may refer to the method embodiment, and is not described herein again.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system and the apparatus described above may refer to corresponding processes in the method embodiments, and are not described in detail in this application. In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and there may be other divisions in actual implementation, and for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or modules through some communication interfaces, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A code auditing method, comprising:
responding to a code review subtask submitted by a first user, and inquiring the associated code review task based on the identification of a team cooperation list carried in the code review subtask; wherein the code review subtask corresponds to a unique identifier of the team collaboration ticket;
if the associated first code auditing task is inquired, adding the code auditing subtask into the first code auditing task;
and notifying at least one second user of the message of newly adding the code auditing subtask in the first code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask.
2. The method of claim 1, wherein the step of querying the associated code review task based on an identification of a team collaborative form carried in the code review subtask in response to the code review subtask submitted by the first user comprises:
responding to a code audit subtask submitted by a first user, and triggering the operation of a preset program;
when the preset program runs, inquiring the identification of the team cooperation list carried in the code review subtask;
querying an associated code review task based on the identification of the team collaboration ticket.
3. The method of claim 1, further comprising:
if the associated first code auditing task is not inquired, a second code auditing task is newly established; wherein the second code audit task is associated with an identification of the team collaboration ticket;
and adding the code auditing subtask into the second code auditing task.
4. The method of claim 3, further comprising:
and notifying at least one second user of the message of adding the code auditing subtask in the second code auditing task, so that the at least one second user audits the code to be audited carried in the code auditing subtask.
5. The method of claim 1, further comprising:
determining a team cooperation order carried in the code review subtask based on an identification of the team cooperation order;
and inquiring the name of at least one second user configured by the first user in the team cooperation list.
6. The method of claim 1, further comprising:
and generating a code auditing subtask based on the identification of the team cooperation list and the code to be audited submitted by the first user through the code version tool.
7. The method of claim 1, further comprising:
and displaying the audit state of each code audit subtask in the first code audit task/the second code audit task to the at least one second user.
8. A code auditing apparatus, comprising:
the query module is used for responding to a code review subtask submitted by a first user and querying a related code review task based on an identifier of a team cooperation list carried in the code review subtask; wherein the code review subtask corresponds to a unique identifier of the team collaboration ticket;
the adding module is used for adding the code review subtask into the first code review task if the associated first code review task is inquired;
and the notification module is used for notifying at least one second user of a message of newly adding the code review subtask in the first code review task so that the at least one second user reviews the code to be reviewed carried in the code review subtask.
9. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is operating, the processor executing the machine-readable instructions to perform the steps of the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, is adapted to carry out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110831476.XA CN113553262B (en) | 2021-07-22 | 2021-07-22 | Code auditing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110831476.XA CN113553262B (en) | 2021-07-22 | 2021-07-22 | Code auditing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113553262A true CN113553262A (en) | 2021-10-26 |
| CN113553262B CN113553262B (en) | 2023-08-11 |
Family
ID=78132463
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110831476.XA Active CN113553262B (en) | 2021-07-22 | 2021-07-22 | Code auditing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113553262B (en) |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090210860A1 (en) * | 2008-02-15 | 2009-08-20 | Microsoft Corporation | Tagging and logical grouping of items in source code change lists |
| US20160224337A1 (en) * | 2015-02-04 | 2016-08-04 | Steven Qian Xia | Supporting developer-user collaborative software review in ide |
| WO2016149555A1 (en) * | 2015-03-18 | 2016-09-22 | Open Source Storage Llc | System and method for gamification of community software development |
| US20170075790A1 (en) * | 2015-09-15 | 2017-03-16 | Linkedln Corporation | Integrating quality analysis with a code review tool |
| US20170123790A1 (en) * | 2015-11-04 | 2017-05-04 | International Business Machines Corporation | User profile based code review |
| CN106844730A (en) * | 2017-02-10 | 2017-06-13 | 网易（杭州）网络有限公司 | The display methods and device of file content |
| US20170243463A1 (en) * | 2016-02-18 | 2017-08-24 | GRZ Pharma, LLC | Systems, methods, and devices for using a code to track task completion |
| CN108073394A (en) * | 2018-02-27 | 2018-05-25 | 西安闻泰电子科技有限公司 | Code administration method, apparatus, code administration server and storage medium |
| CN108089984A (en) * | 2017-12-14 | 2018-05-29 | 泰康保险集团股份有限公司 | Implementation method, device, storage medium and the electronic equipment of code review |
| CN109542769A (en) * | 2018-10-25 | 2019-03-29 | 武汉精立电子技术有限公司 | A kind of automated testing method of continuous integrating |
| CN109783128A (en) * | 2018-12-13 | 2019-05-21 | 平安普惠企业管理有限公司 | Code change notification method, equipment, storage medium and device |
| US10482005B1 (en) * | 2017-09-26 | 2019-11-19 | EMC IP Holding Company LLC | Method and apparatus for developer code risk assessment |
| US20200019493A1 (en) * | 2018-06-27 | 2020-01-16 | Accenture Global Solutions Limited | Automating testing and deployment of software code changes |
| CN110866730A (en) * | 2018-12-29 | 2020-03-06 | 北京安妮全版权科技发展有限公司 | Code assessment system and method |
| US20200226054A1 (en) * | 2019-01-15 | 2020-07-16 | International Business Machines Corporation | Determining Reviewers for Software Inspection |
| CN112445514A (en) * | 2019-09-05 | 2021-03-05 | 腾讯科技（深圳）有限公司 | Code evaluation method and related product |
| US20210124561A1 (en) * | 2017-08-22 | 2021-04-29 | Codestream, Inc. | System and method for in-ide code review |
| CN112748950A (en) * | 2021-01-15 | 2021-05-04 | 国能日新科技股份有限公司 | Software code examination method and device |
-
2021
- 2021-07-22 CN CN202110831476.XA patent/CN113553262B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090210860A1 (en) * | 2008-02-15 | 2009-08-20 | Microsoft Corporation | Tagging and logical grouping of items in source code change lists |
| US20160224337A1 (en) * | 2015-02-04 | 2016-08-04 | Steven Qian Xia | Supporting developer-user collaborative software review in ide |
| WO2016149555A1 (en) * | 2015-03-18 | 2016-09-22 | Open Source Storage Llc | System and method for gamification of community software development |
| US20170075790A1 (en) * | 2015-09-15 | 2017-03-16 | Linkedln Corporation | Integrating quality analysis with a code review tool |
| US20170123790A1 (en) * | 2015-11-04 | 2017-05-04 | International Business Machines Corporation | User profile based code review |
| US20170243463A1 (en) * | 2016-02-18 | 2017-08-24 | GRZ Pharma, LLC | Systems, methods, and devices for using a code to track task completion |
| CN106844730A (en) * | 2017-02-10 | 2017-06-13 | 网易（杭州）网络有限公司 | The display methods and device of file content |
| US20210124561A1 (en) * | 2017-08-22 | 2021-04-29 | Codestream, Inc. | System and method for in-ide code review |
| US10482005B1 (en) * | 2017-09-26 | 2019-11-19 | EMC IP Holding Company LLC | Method and apparatus for developer code risk assessment |
| CN108089984A (en) * | 2017-12-14 | 2018-05-29 | 泰康保险集团股份有限公司 | Implementation method, device, storage medium and the electronic equipment of code review |
| CN108073394A (en) * | 2018-02-27 | 2018-05-25 | 西安闻泰电子科技有限公司 | Code administration method, apparatus, code administration server and storage medium |
| US20200019493A1 (en) * | 2018-06-27 | 2020-01-16 | Accenture Global Solutions Limited | Automating testing and deployment of software code changes |
| CN109542769A (en) * | 2018-10-25 | 2019-03-29 | 武汉精立电子技术有限公司 | A kind of automated testing method of continuous integrating |
| CN109783128A (en) * | 2018-12-13 | 2019-05-21 | 平安普惠企业管理有限公司 | Code change notification method, equipment, storage medium and device |
| CN110866730A (en) * | 2018-12-29 | 2020-03-06 | 北京安妮全版权科技发展有限公司 | Code assessment system and method |
| US20200226054A1 (en) * | 2019-01-15 | 2020-07-16 | International Business Machines Corporation | Determining Reviewers for Software Inspection |
| CN112445514A (en) * | 2019-09-05 | 2021-03-05 | 腾讯科技（深圳）有限公司 | Code evaluation method and related product |
| CN112748950A (en) * | 2021-01-15 | 2021-05-04 | 国能日新科技股份有限公司 | Software code examination method and device |
Non-Patent Citations (3)
| Title |
|---|
| 和征;: "大型软件项目管理业务协同的研究与实现", 机械设计与制造, no. 06 * |
| 曾新励;: "基于SonarQube平台提升企业软件项目质量的应用研究", 电脑知识与技术, no. 11 * |
| 赵海燕;李敏;陈庆奎;曹健;: "开源软件开发中的代码评审", 小型微型计算机系统, no. 04 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113553262B (en) | 2023-08-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7725352B2 (en) | Method and system for enterprise-wide migration | |
| US20080262860A1 (en) | System and Method for Supporting Software | |
| KR100500622B1 (en) | System and method for working management | |
| JP2009104229A (en) | Input check device and input check method | |
| US6796486B2 (en) | Document review apparatus, a document review system, and a computer product | |
| CN113706022A (en) | Business process execution method and device, storage medium and electronic equipment | |
| CN101650804A (en) | Method for managing process of third generation mobile communication operating and maintaining system | |
| CN115630835A (en) | Activity-based workflow general parameter configuration method and system | |
| CN111371645A (en) | Method, system, computer equipment and storage medium for testing service connectivity | |
| US7617462B2 (en) | Graphical user interface (GUI) for displaying software component availability as determined by a messaging infrastructure | |
| KR100671146B1 (en) | Interface apparatus of Manufacturing Execution System | |
| KR20120126692A (en) | System and method for production management of partners in ship fabrication and computer readable recording medium | |
| CN112052262A (en) | Method and device for displaying payment order processing line and electronic equipment | |
| EP2629250A1 (en) | A system and method for providing enterprise information technology lifecycle tools synchronization platform | |
| CN113553262A (en) | Code auditing method and device, electronic equipment and storage medium | |
| JP4027804B2 (en) | Method for changing the role of starting an application service, computer executable program, and computer system | |
| CN112099783A (en) | Flow creation method and device, electronic equipment and storage medium | |
| JP4909811B2 (en) | Dynamic integrated monitoring system for business processes | |
| US20110047001A1 (en) | Method and system for creating an instance of an adaptable business object | |
| JP2014059666A (en) | Task input screen customization system | |
| CN116643794B (en) | Information processing method and device and electronic equipment | |
| JP6364569B1 (en) | Information processing program, information processing apparatus, and information processing method | |
| US20080235653A1 (en) | System and method for defining and dynamically invoking polymorphic call flows | |
| JP2013097716A (en) | Information processor, information processing method, and program | |
| CN114116730B (en) | Interface management method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |