WO2019200701A1

WO2019200701A1 - Configuration management method and apparatus, terminal device and storage medium

Info

Publication number: WO2019200701A1
Application number: PCT/CN2018/092560
Authority: WO
Inventors: 杨冬振
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-04-17
Filing date: 2018-06-25
Publication date: 2019-10-24
Also published as: CN108762803A; CN108762803B

Abstract

Disclosed in the present application are a configuration management method and apparatus, a terminal device and a storage medium, the configuration management method comprises the following steps executed by a client: receiving code submitting application information sent by a user; Acquiring, according to address identification information, a code to be submitted; performing static code inspection on the code to be submitted, and obtaining a static code inspection report; analyzing the static code inspection report, and extracting index result data in the static code inspection report according to a preset index; sending the index result data and identity identification information to a server; and sending a code submitting request to a configuration management platform, the code submitting request comprising the address identification information, the identity identification information and branch version information. The technical solution in the present application guarantees the code quality, reducing the code management risk and modification cost, increasing the code development efficiency.

Description

Configuration management method, device, terminal device and storage medium

The present application is based on the Chinese Patent Application No. 201810342227.2 filed on Apr. 17, 2018, entitled "A Configuration Management Method, Apparatus, Terminal Device, and Storage Medium", and claims priority.

Technical field

The present application relates to the field of computer technologies, and in particular, to a configuration management method, apparatus, terminal device, and storage medium.

Background technique

SVN, short for Subversion, is an open source, centralized version control management tool for submitting and managing software source code.

At present, the common SVN code management uses the "submit code----detection code" method to control the code quality. First, the code is submitted to the SVN code base, and then the code in the code base is statically checked, and the code is found to exist. The problem, if there is a problem, feedback to the developer to modify, and then resubmit, overwrite the problem code. This kind of code management method is difficult to effectively control the quality of the code. It is to modify the problem code after the code is submitted to the SVN official library. The implementation process is cumbersome, and it will also cause the risk of modification and the labor cost of the development test. At the same time, in SVN Code detection, modification and submission in the code base, especially when submitting code concurrently, is prone to overload of the SVN code base, resulting in performance bottleneck of the SVN code base, resulting in reduced code detection efficiency and development efficiency.

Summary of the invention

The embodiment of the present application provides a configuration management method, device, terminal device, and storage medium, so as to solve the problem that the risk of code modification is high and the labor cost of the development test is wasted, and the code development efficiency is low.

In a first aspect, the embodiment of the present application provides a configuration management method, including the following steps performed by a client:

Receiving code submission application information sent by the user, where the code submission application information includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

Obtaining the to-be-committed code according to the address identification information;

Performing static code check on the to-be-committed code to obtain a static code check report;

Parsing the static code check report, and extracting indicator result data in the static code check report according to a preset indicator;

Sending the indicator result data and the identity identification information to the server;

Sending a code submission request to the configuration management platform, where the code submission request includes the address identification information, the identity identification information, and the branch version information;

If the prompt information including the submission result sent by the configuration management platform is received, the prompt information is fed back to the user.

In a second aspect, the embodiment of the present application provides a configuration management method, including the following steps performed by the configuration management platform:

Receiving a code submission request sent by the client, where the code submission request includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

Sending a code indicator detection request to the server, so that the server performs index detection on the to-be-committed code, where the code indicator detection request includes the branch version information and the identity identification information;

Receiving an operation instruction returned by the server according to the result of the indicator detection;

If the operation instruction is to allow the submission, the code to be submitted is obtained according to the address identification information, and the code to be submitted is merged into the branch version corresponding to the branch version information, and is successfully sent to the client. Submitted prompt information;

If the operation instruction is to reject the submission, the client sends a prompt message rejecting the submission.

In a third aspect, the embodiment of the present application provides a configuration management method, including the following steps performed by a server:

Receiving the indicator result data of the static code check report sent by the client and the identity identification information of the user, and storing the indicator result data and the identity identification information in the indicator database;

And acquiring the branch version information and the identity identification information in the code indicator detection request, if the code indicator detection request sent by the configuration management platform is received;

Obtaining preset indicator standard data corresponding to the branch version information according to the branch version information;

Obtaining, by the indicator database, the indicator result data corresponding to the identity identification information;

If it is detected that the indicator result data satisfies the requirement of the indicator standard data, generating an operation instruction that is allowed to be submitted, otherwise generating an operation instruction that refuses to submit;

The operation instruction is sent to the configuration management platform.

In a fourth aspect, the embodiment of the present application provides a configuration management apparatus, including a client, where the client includes:

The application receiving module is configured to receive code submission application information sent by the user, where the code submission application information includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

a code obtaining module, configured to acquire the to-be-committed code according to the address identification information;

a code checking module, configured to perform static code check on the to-be-committed code to obtain a static code check report;

An indicator extraction module, configured to parse the static code inspection report, and extract indicator result data in the static code inspection report according to a preset indicator;

An indicator sending module, configured to send the indicator result data and the identity identification information to a server;

a request sending module, configured to send a code submission request to the configuration management platform, where the code submission request includes the address identification information, the identity identification information, and the branch version information;

The information feedback module is configured to: when receiving the prompt information that is sent by the configuration management platform and includes the submission result, feed the prompt information to the user.

In a fifth aspect, the embodiment of the present application provides a configuration management apparatus, including a configuration management platform, where the configuration management platform includes:

a request receiving module, configured to receive a code submission request sent by the client, where the code submission request includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

An indicator detection module, configured to send a code indicator detection request to the server, so that the server performs index detection on the to-be-committed code, where the code indicator detection request includes the branch version information and the identity identifier information;

An instruction receiving module, configured to receive an operation instruction returned by the server according to the result of the indicator detection;

a code submission module, configured to: obtain the to-be-committed code according to the address identification information, and merge the to-be-committed code into a branch version corresponding to the branch version information, and The client sends the prompt information successfully submitted;

And an information sending module, configured to send, to the client, prompt information that refuses to submit if the operation instruction is to reject the submission.

In a sixth aspect, the embodiment of the present application provides a configuration management apparatus, including a server, where the server includes:

The indicator receiving module is configured to receive the indicator result data of the static code check report sent by the client and the identity identification information of the user, and store the indicator result data and the identity identification information in the indicator database;

The information obtaining module is configured to: obtain the branch version information and the identity identification information in the code indicator detection request, if the code indicator detection request sent by the configuration management platform is received;

a data obtaining module, configured to acquire, according to the branch version information, preset indicator standard data corresponding to the branch version information;

An indicator obtaining module, configured to acquire the indicator result data corresponding to the identity identification information from the indicator database;

An instruction generating module, configured to generate an operation instruction that is allowed to be submitted if it is detected that the indicator result data satisfies the requirement of the indicator standard data, and otherwise generate an operation instruction that refuses to submit;

And an instruction sending module, configured to send the operation instruction to the configuration management platform.

In a seventh aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, where the processor executes the computer The steps of the configuration management method are implemented when the instruction is read.

In an eighth aspect, the embodiment of the present application provides one or more non-volatile readable storage media storing computer readable instructions, when the computer readable instructions are executed by one or more processors, such that the one or The steps of implementing the configuration management method when executed by a plurality of processors.

The details of one or more embodiments of the present invention are set forth in the accompanying drawings and the description of the claims.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present application. Other drawings may also be obtained from those of ordinary skill in the art based on these drawings without the inventive labor.

1 is a schematic diagram of a network structure of a configuration management system in a configuration management method provided in Embodiment 1 of the present application;

2 is a flowchart of an implementation of a configuration management method provided in Embodiment 1 of the present application;

3 is a diagram showing an example of a specific static code check result of the configuration management method provided in Embodiment 1 of the present application;

4 is a flowchart of implementing an application for a special grant permission of a client in a configuration management method provided in Embodiment 1 of the present application;

FIG. 5 is a flowchart of an implementation of step S117 in the configuration management method provided in Embodiment 1 of the present application;

6 is a schematic diagram of a configuration management apparatus provided in Embodiment 2 of the present application;

FIG. 7 is a schematic diagram of a terminal device provided in Embodiment 4 of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Example 1

The configuration management method of the embodiment of the present application is applied to a configuration management system. As shown in FIG. 1 , FIG. 1 is a schematic diagram of a network structure of a configuration management system, where the configuration management system includes a client, a configuration management platform, and a server.

The client may be a personal computer (PC) or other intelligent terminal device. The server may be a server, a server cluster composed of several servers, or a cloud computing service center.

The client and the configuration management platform, the client and the server, and the configuration management platform and the server are connected through a network communication medium, and the specific network propagation medium may be wired or wireless.

The configuration management method in the embodiment of the present application specifically includes the following steps performed by the client:

The configuration management method in the embodiment of the present application specifically includes the following steps performed by the configuration management platform:

The configuration management method in the embodiment of the present application further includes the following steps performed by the server:

The operation instruction is sent to the configuration management platform.

Referring to FIG. 2, FIG. 2 shows an implementation flow of the configuration management method provided by this embodiment. Details are as follows:

S101: The client receives the code submission application information sent by the user, where the code submission application information includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information.

In the embodiment of the present application, the address identification information is used to extract the code to be submitted, the identity identification information is used to uniquely mark the user of the client, and the branch version information is used to mark the version information of the code to be submitted.

It should be noted that the address identifier information may be a storage path of the code to be submitted, such as “D:\workspace\demo_svn”, or other forms, and is not limited herein.

The identity information may specifically be a registered user name or other forms, and is not limited herein.

S102: The client obtains the code to be submitted according to the address identification information.

In the embodiment of the present application, the code to be submitted is the code that the user applies to submit to the configuration management platform.

Specifically, the client finds the location of the to-be-committed code corresponding to the address identification information according to the address identification information in step S101, and acquires the code to be submitted.

S103: The client performs static code check on the submitted code to obtain a static code check report.

In the embodiment of the present application, the static code check refers to checking the submitted code according to a preset check indicator according to actual application requirements. The static code inspection report is a check result report obtained by static code checking of the submitted code.

The preset inspection indicator is an inspection indicator configured when the static code is checked according to actual business requirements, including unit testing, code specification checking, coverage rate, and circle complexity.

It should be noted that the static code check can be checked by Eclipse plug-in platform check or other plug-in set check. There is no restriction here.

Preferably, the Eclipse plugin is used to treat the submitted code for static code checking.

The Eclipse plugin is an open source, Java-based extensible development platform. For its part, it is just a framework and a set of services for building development environments through plug-in components. The Eclipse plug-in comes with a standard The set of plug-ins can check the code for multiple check indicators. The check indicators include unit test (JUnitTest), code bug check (FindBugs), code specification check (CheckSytle), coverage (coverage) and circle complexity ( Complexity) and so on.

Specifically, the client uses the Eclipse plug-in to perform the static code check on the to-be-submitted code obtained in step S102 according to the preset check indicator, and obtain a static code check report under each check indicator, and check the static code by submitting the code. The measurement of the quality of the code, the hidden dangers and errors of the detection code are realized, so that the user can timely modify the error code and the code that does not meet the specification according to the inspection result, and obtain the valid qualified code.

For example, as shown in FIG. 3, FIG. 3 shows an inspection report for the static code check according to the check indicators "coverage rate" and "code bug check" for the code to be submitted in the "D:\workspace\demo_svn" directory, the user. You can view the full static code scan report by clicking on "Details".

S104: The client parses the static code check report, and extracts the indicator result data in the static code check report according to the preset indicator.

In the embodiment of the present application, the client parses the static code check report by using the Eclipse plug-in to capture the static code check report, parsing the content of the static code check report, or parsing other plug-in sets, and not doing this. limit.

The preset indicator is the indicator result data in the content for extracting the static code check report, which is set according to the actual application requirement, and includes the number of unit test junit failures, the error code of the file stream not closed in the code, and the non-conformity. The code quality of the administrator configured is the bad taste code of the sonar specification and whether it conforms to the preset code writing style requirements, etc., wherein the preset code writing style requirement may be whether the braces are wrapped or other format requirements, and no limitation is imposed here.

The indicator result data is data extracted from the contents of the static code inspection report according to preset indicators.

Specifically, the client checks the report of the static code obtained in step S103, uses the Eclipse plug-in to parse the report content, and extracts the indicator result data in the static code check report according to the preset index.

S105: The client sends the indicator result data and the identity identification information to the server.

Specifically, the client sends the indicator result data of the user to be submitted in step S104 and the identity information of the user corresponding to the code to be submitted to the server, and can transmit the message through a real time message transmission protocol (RTMP).

S106: The server receives the indicator result data of the static code check report sent by the client and the identity identification information of the user, and stores the indicator result data and the identity identification information in the indicator database.

In the embodiment of the present application, the indicator database is used to store the indicator result data of the static code check report sent by the client received by the server and the identity identification information of the user.

It should be noted that the indicator result data of the code to be submitted in the indicator database and the identity information of the user corresponding to the code to be submitted are uniquely stored.

Specifically, the server receives the indicator result data of the static code check report sent by the client and the identity identification information of the user through the RTMP protocol.

S107: The client sends a code submission request to the configuration management platform, where the code submission request includes address identification information, identity identification information, and branch version information.

Specifically, the client sends a code submission request to the configuration management platform through the RTMP protocol.

S108: The configuration management platform receives a code submission request sent by the client, where the code submission request includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information.

Specifically, the configuration management platform receives the code submission request sent by the client through the RTMP protocol.

S109: The configuration management platform sends a code indicator detection request to the server, so that the server performs the indicator detection on the submitted code, where the code indicator detection request includes the branch version information and the identity identification information.

Specifically, the configuration management platform may send a code indicator detection request to the server by means of a hook function HOOK.

The hook function HOOK of the configuration management platform is a piece of logic triggered when receiving a code submission request sent by the client. The default is that there is no execution content, and the user can write a shell script or a batch bat script according to the application requirement. The script issues a code indicator detection request to the server's interface.

It should be noted that the configuration management platform may also send a code indicator detection request to the server by means of an interactive message, which may be set according to actual application requirements, and is not limited herein.

S110: If the server receives the code indicator detection request sent by the configuration management platform, the server obtains the branch version information and the identity identification information in the code indicator detection request.

Specifically, the server receives the code indicator detection request sent by the configuration management platform by using the RTMP protocol.

S111: The server obtains preset indicator standard data corresponding to the branch version information according to the branch version information.

In the embodiment of the present application, the preset indicator standard data is a detection standard set according to an actual service requirement, and is used to perform index detection on the indicator result data, where the preset indicator standard data includes a code detection indicator and a corresponding code detection indicator. The target value.

S112: The server obtains the indicator result data corresponding to the identity identification information from the indicator database.

Specifically, the server obtains, according to the code indicator detection request received in step S110, the indicator result data that is uniquely corresponding to the identity identification information, where the indicator result data includes the preset indicator in step S104 and the indicator. Corresponding values.

S113: If the server detects that the indicator result data meets the requirement of the indicator standard data, generates an operation instruction that is allowed to be submitted, and otherwise generates an operation instruction that refuses to submit.

Specifically, the index detection is performed on the indicator result data obtained in step S112 according to the indicator standard data obtained in step S111, wherein the indicator detection refers to the preset indicator in the detection index result data and the code detection according to the indicator standard data. The indicator has the same indicator, and the value corresponding to the preset indicator under the same indicator is compared with the value corresponding to the code detection index. If the comparison result satisfies the requirement of the indicator, an operation instruction allowing the submission is generated, otherwise the operation of rejecting the submission is generated. instruction.

For example, suppose the pre-configured code detection indicators include coverage rate and unit test. The target value is specifically 80% coverage rate, and the number of unit test failures is less than 3. If the actual coverage rate of the indicator result data is 70%, and the unit test If the number of actual failures is two, the server confirms that the actual coverage rate does not meet the target coverage requirement. The result of the indicator detection is that the indicator result data does not meet the requirements of the indicator standard data, and correspondingly generates an operation instruction that refuses to submit, if the indicator data The actual coverage rate is 86%, and the actual number of unit test failures is 2. The result of the server-side verification indicator detection is that the indicator result data meets the requirements of the indicator standard data, and correspondingly generates an operation instruction that is allowed to be submitted.

S114: The server sends an operation instruction to the configuration management platform.

Specifically, the server can send an operation instruction to the configuration management platform through a socket process communication.

It should be noted that, after the server sends an operation instruction that is allowed to be submitted to the configuration management platform, the server invalidates the indicator result data and the user identity information stored in the indicator database to ensure that the indicator is submitted every time the code is submitted. The indicator result data and the user's identity information stored in the database are the information corresponding to the code to be submitted.

S115: The configuration management platform receives an operation instruction returned by the server according to the result of the indicator detection.

Specifically, the configuration management platform may receive, by using the socket process communication, an operation instruction returned by the server according to the result of the indicator detection, where the operation instruction includes allowing submission and rejecting the submission.

S116: If the operation instruction received by the configuration management platform is allowed to be submitted, the configuration management platform acquires the to-be-submitted code according to the address identification information, merges the to-be-committed code into the branch version corresponding to the branch version information, and sends the successful submission to the client. Tip message.

Specifically, when the operation instruction is to allow the submission, the configuration management platform acquires the to-be-committed code according to the address identification information in step S108, and then merges the to-be-submitted code into the branch version corresponding to the branch version information according to the branch version information of the to-be-committed code. And send a prompt message to the client for successful submission.

The prompt information successfully submitted includes the identity identification information corresponding to the successfully submitted code and the time of successfully submitting the code.

S117: If the operation instruction received by the configuration management platform is to reject the submission, the configuration management platform sends the prompt information for rejecting the submission to the client.

In the embodiment of the present application, the prompt information for rejecting the submission includes the identity identification information corresponding to the code rejected by the submission, the time of rejecting the submission of the code, and the reason for rejecting the submission of the code, for example, the reason for rejecting the submission of the code may be “FAIL-CPH006”. -EMMA", indicating that the coverage of the unit test does not meet the requirements.

S118: If the client receives the prompt information sent by the configuration management platform and includes the submission result, the client feeds back the prompt information to the user.

Specifically, if the client receives the prompt information sent by the configuration management platform as the successful submission, the corresponding user is found according to the identity identification information corresponding to the successfully submitted code in the prompt information, and the prompt information is fed back to the user.

If the client receives the prompt information sent by the configuration management platform to reject the submission, the corresponding user is found according to the identity identification information corresponding to the code that is rejected in the prompt information, and the prompt information is fed back to the user.

In the embodiment corresponding to FIG. 2, when the client receives the code submission application sent by the user, before the code submission request is sent to the configuration management platform, the client uses the code detection tool to statically check the code, which is formal. Before submitting the source code, the system can automatically perform static code check to quickly obtain the inspection report and check result. After receiving the code submission request sent by the client, the configuration management platform requires the server to perform the indicator detection on the inspection result, only when the indicator is detected. When the code is allowed to pass, the code quality is measured, and the hidden dangers and errors of the code can be detected, so that the user can timely modify the error code and the code that does not meet the specification according to the inspection result, and obtain the valid qualified code, thereby Reduce the code risk in the SVN code base of the configuration management platform, reduce the modification cost after the code is uploaded to the formal management platform of the configuration management platform, save the time for manual review of the code, improve the efficiency of code development, and complete the static code check on the client side. And finished at the server The detection of the code indicator realizes that the cost of the configuration management platform is distributed to each client and server to complete, thereby reducing the load of the configuration management platform, especially when there are many users, and large concurrent code is submitted to the configuration management platform. The performance bottleneck of the configuration management platform can be effectively avoided, the performance level of the configuration management platform can be improved, the performance during the system running process and the scalability of the system can be improved, and the code development efficiency can be further improved.

Next, on the basis of the embodiment corresponding to FIG. 2, after receiving the application information sent by the user mentioned in step S101, the client further includes a process of processing the special approval request for the user.

In the embodiment of the present application, the code submission application information further includes a special batch application identifier of the user, and the special batch application identifier is identifier information used for applying the special approval authority to the code to be submitted.

Among them, the special batch permission means that before the code is submitted to the SVN code base of the configuration management platform, when the code to be submitted is rejected, the test result may be disregarded, the code is allowed to be submitted, and the branch version number is directly incorporated to satisfy the actual application. Need to improve the usability of the code.

Referring to FIG. 4, FIG. 4 shows a specific implementation process of the client-to-user special grant permission application provided by the embodiment of the present application, which is described in detail as follows:

S401: The client sends a special permission application to the preset approver according to the special approval application identifier.

In the embodiment of the present application, the preset approver is a preset staff member who sets the special approval authority, and the approver receives the special approval authority application, and according to the approval condition, the special pending application code corresponding to the special approval identifier is specially made. Approval of batch permissions, where the approval conditions are set according to actual application and business needs.

Specifically, when the client receives the special batch application identifier, if it is confirmed that the to-be-submitted code needs to be specially applied, the user's identity identification information and the branch version information are sent to the preset approver for special permission application.

The sending method may be a mail, an instant message, etc., and is not limited herein.

S402: If the client receives the approval result returned by the approver as a special batch application, the client sends the user's special permission identification information and the user identity information to the configuration management platform, so that the configuration management platform will be specially approved. The permission identification information is stored in the permission database corresponding to the identity identification information.

In the embodiment of the present application, the permission database is used to store the special authorization identification information of the user sent by the configuration management platform and the identity identification information of the user.

The special batch identification information includes branch version information that allows the code to be submitted to be directly joined.

Specifically, according to the special permission application sent to the approver in step S401, the examiner approves the special approval application and meets the approval conditions, the approval result is that the special application is successful, and the approval result is returned to the customer. end.

The client generates the special batch identification information corresponding to the special batch application identifier according to the approval result, and the special batch authorization identifier information is used to identify whether the user has the right to directly join the branch version corresponding to the submitted code, and the special batch permission The identifier information may specifically be the branch version information of the branch version corresponding to the code to be submitted.

The client sends the special permission identification information and the user identification information to the configuration management platform, so that the configuration management platform saves the special authorization identification information and the identity identification information in the permission database.

In the embodiment corresponding to FIG. 4, the client sends a special permission application to the preset approver according to the special application identifier, and sends the special authorization identification information and the user identification information of the successful application to the configuration management platform. The configuration management platform may save the special batch identification information and the identity identification information in the permission database, so that when the pending code to be submitted is rejected, if the special permission identification information exists, the detection result may be disregarded. Code submission, directly into the branch version, to meet the needs of the actual application, improve the usability of the code.

On the basis of the corresponding embodiment of FIG. 2, the configuration management platform sends a rejection submission to the client, if the operation instruction received by the configuration management platform mentioned in step S117 is rejected, by a specific embodiment. The specific implementation method of the prompt information is described in detail.

Referring to FIG. 5, FIG. 5 shows a specific implementation process of step S117 provided by the embodiment of the present application, which is described in detail as follows:

S501: When the operation instruction received by the configuration management platform is to reject the submission, the configuration management platform queries the permission database for the special batch identification information corresponding to the identity information of the user.

Specifically, when the operation instruction received by the configuration management platform is to reject the submission, the configuration management platform first confirms whether there is identity identification information corresponding to the to-be-committed code from the permission database, and if yes, continues to query the identity database and the identity identification information. Whether the corresponding special batch identification information is not empty.

S502: If the configuration management platform queries the privilege database to query the privilege identifier information corresponding to the identity information, the configuration management platform obtains the to-be-submitted code according to the address identification information, and the code to be submitted is merged into the branch version information. In the branch version, and send the prompt message to the client for the successful submission of the special batch permission.

Specifically, the configuration management platform queries the permission database for the special batch identification information corresponding to the identity identification information, and if the special permission identification information is not empty, obtaining the permission to directly join the special permission identification information. The branch version information, if the branch version information that is directly allowed to be merged is the same as the branch version information to be merged, the code to be submitted is obtained according to the address identification information in step S108, and the branch version information corresponding to the code to be submitted is used. The code to be submitted is merged into the branch version corresponding to the branch version information, and the prompt information successfully submitted by the special batch permission is sent to the client through the RTMP protocol.

The prompt information successfully submitted by the special batch permission includes the identity identification information corresponding to the special batch permission identification information, the special batch permission information, and the time of successfully submitting the code.

It should be noted that, after the configuration management platform sends the prompt information successfully submitted by the special batch permission to the client, the configuration management platform invalidates the special batch identification information corresponding to the identity identification information saved in the permission database to ensure The special batch identification information saved in the permission database each time the code is submitted is the permission information corresponding to the code to be submitted.

S503: If the configuration management platform does not query the identity information in the permission database, or if the special permission identification information corresponding to the identity identification information is empty, the configuration management platform sends the prompt information that the rejection submission is sent to the client.

Specifically, the identity identification information corresponding to the to-be-committed code is not queried, or the special batch identification information corresponding to the identity identification information does not exist in the permission database, and the submission of the to-be-submitted code is rejected, and the configuration management platform passes the RTMP protocol. Send a message to the client rejecting the submission.

In the embodiment corresponding to FIG. 5, when the operation instruction received by the configuration management platform is a rejection submission, the special batch identification information is not empty by querying the special authorization identification information corresponding to the user identification information from the permission database. If the branch version information that is allowed to be directly joined is the same as the branch version information to be merged, the code to be submitted is merged into the branch version information. In the corresponding branch version, the code submission is completed, and at the same time, the pending code that does not have the identity information or the special permission identification information is empty, the submission is rejected, and the code 瑕疵 acceptable range is realized under the condition that the actual application needs. Within the scope of the test, the code can be submitted and used without any consideration, which improves the usability and usability of the code, thereby promoting the efficiency of code development.

It should be understood that the size of the sequence of the steps in the above embodiments does not mean that the order of execution is performed. The order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

Example 2

Corresponding to the configuration management method in Embodiment 1, FIG. 6 shows a configuration management apparatus corresponding to the configuration management method provided in Embodiment 1, which includes a client, a configuration management platform, and a server. For the convenience of description, only the parts related to the embodiments of the present application are shown.

As shown in FIG. 6, the client of the configuration management apparatus includes: an application receiving module 601, a code obtaining module 602, a code checking module 603, an index extracting module 604, an index sending module 605, a request sending module 606, and an information feedback module 607. Each function module is described in detail as follows:

The application receiving module 601 is configured to receive code submission application information sent by the user, where the code submission application information includes address identification information of the code to be submitted, identity identification information of the user, and branch version information;

The code obtaining module 602 is configured to obtain a code to be submitted according to the address identification information.

The code checking module 603 is configured to perform static code check on the submitted code to obtain a static code check report;

The indicator extraction module 604 is configured to parse the static code inspection report, and extract the indicator result data in the static code inspection report according to the preset indicator;

The indicator sending module 605 is configured to send the indicator result data and the identity identification information to the server;

The request sending module 606 is configured to send a code submission request to the configuration management platform, where the code submission request includes address identification information, identity identification information, and branch version information;

The information feedback module 607 is configured to: when receiving the prompt information that is sent by the configuration management platform and including the submission result, feed the prompt information to the user.

Further, the code submission application information further includes a special application identifier of the user, and the client of the configuration management device further includes:

The permission application module 619 is configured to send a special permission application to the preset approver according to the special approval application identifier;

The permission sending module 620 is configured to: if the approval result returned by the approver is that the special batch application is successful, send the special authorization identification information of the user and the identity identification information of the user to the configuration management platform, so that the configuration management platform will The batch permission identification information is stored in the authority database corresponding to the identity identification information.

Referring to FIG. 6 , as shown in FIG. 6 , the configuration management platform of the configuration management apparatus includes: a request receiving module 608 , an indicator detecting module 609 , an instruction receiving module 610 , a code submitting module 611 , and an information sending module 612 . Each function module is described in detail as follows:

The request receiving module 608 is configured to receive a code submission request sent by the client, where the code submission request includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

The indicator detection module 609 is configured to send a code indicator detection request to the server, so that the server performs the indicator detection on the submitted code, where the code indicator detection request includes the branch version information and the identity identification information;

The instruction receiving module 610 is configured to receive an operation instruction returned by the server according to the result of the indicator detection;

The code submission module 611 is configured to: if the operation instruction is to allow the submission, obtain the code to be submitted according to the address identification information, merge the code to be submitted into the branch version corresponding to the branch version information, and send the prompt information successfully submitted to the client;

The information sending module 612 is configured to send the prompt information for rejecting the submission to the client if the operation instruction is to reject the submission.

Further, the information sending module 612 includes:

The permission query unit 6121 is configured to query the special batch authorization information corresponding to the identity information of the user from the permission database when the operation instruction is to reject the submission;

The code submitting unit 6122 is configured to: if the special batch identification information corresponding to the identity identification information is not empty in the permission database, obtain the to-be-submitted code according to the address identification information, and merge the to-be-committed code into the branch corresponding to the branch version information. In the version, and send a prompt message to the client that the special batch permission is successfully submitted;

The information sending unit 6123 is configured to send the prompt information that refuses to submit to the client if the identity identification information is not queried in the authority database, or the special batch identification information corresponding to the identity identification information is vacant.

Referring to FIG. 6 , as shown in FIG. 6 , the server of the configuration management apparatus includes: an indicator receiving module 613 , an information acquiring module 614 , a data acquiring module 615 , an index obtaining module 616 , an instruction generating module 617 , and an instruction sending module 618 . . Each function module is described in detail as follows:

The indicator receiving module 613 is configured to receive the indicator result data of the static code check report sent by the client and the identity identification information of the user, and store the indicator result data and the identity identification information in the indicator database;

The information obtaining module 614 is configured to: obtain the branch version information and the identity identification information in the code indicator detection request, if receiving the code indicator detection request sent by the configuration management platform;

The data obtaining module 615 is configured to obtain preset index standard data corresponding to the branch version information according to the branch version information.

The indicator obtaining module 616 is configured to obtain indicator result data corresponding to the identity identification information from the indicator database;

The instruction generating module 617 is configured to: if it is detected that the indicator result data meets the requirement of the indicator standard data, generate an operation instruction that is allowed to be submitted; otherwise, generate an operation instruction that rejects the submission;

The instruction sending module 618 is configured to send the operation instruction to the configuration management platform.

For the process of implementing the respective functions of the modules in the configuration management apparatus provided in this embodiment, refer to the description of the foregoing Embodiment 1, and details are not described herein again.

Example 3

The present embodiment provides one or more non-volatile readable storage media having computer readable instructions stored thereon, the one or more non-readable readable storage media storing computer readable instructions, the computer readable instructions being The configuration management method in Embodiment 1 is implemented when one or more processors are executed, when one or more processors are executed. To avoid repetition, we will not repeat them here. Alternatively, the functions of the modules/units in the configuration management apparatus in Embodiment 2 are implemented when the computer readable instructions are executed by the processor. To avoid repetition, we will not repeat them here.

It will be understood that one or more non-volatile readable storage media storing computer readable instructions comprise: any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a mobile hard disk, a magnetic Disc, optical disc, computer memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signals, and telecommunications signals.

Example 4

FIG. 7 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in FIG. 7, the terminal device 70 of this embodiment includes a processor 71, a memory 72, and a program readable by computer readable instructions 73, such as a configuration management method, stored in the memory 72 and executable on the processor 71. When the processor 71 executes the computer readable instructions 73, the steps in the above embodiments of the respective configuration management methods are implemented, such as steps S101 to S118 shown in FIG. Alternatively, when the processor 71 executes the computer readable instructions 73, the functions of the modules/units in the foregoing device embodiments are implemented, for example, the functions of the modules 601 to 607 of the client shown in FIG. 7, and the modules 608 to 612 of the configuration management platform are configured. The function, as well as the functionality of the module 613 to the module 618 on the server side.

Illustratively, computer readable instructions 73 may be partitioned into one or more modules/units, one or more modules/units being stored in memory 72 and executed by processor 71 to complete the application. The one or more modules/units may be an instruction segment of a series of computer readable instructions capable of performing a particular function, which is used to describe the execution of computer readable instructions 73 in the terminal device 70. For example, the computer readable instructions 73 may be divided into an application receiving module, a code acquisition module, a code checking module, an index extraction module, an indicator sending module, a request sending module, and an information feedback module. The specific functions of the modules are as shown in Embodiment 2. To avoid repetition, details are not described herein.

The computer readable instructions 73 may also be partitioned into a request receiving module, an indicator detecting module, an instruction receiving module, a code submitting module, and an information transmitting module. The specific functions of the modules are as shown in Embodiment 2. To avoid repetition, details are not described herein.

The computer readable instructions 73 may also be divided into an indicator receiving module, an information acquiring module, a data acquiring module, an index obtaining module, an instruction generating module, and an instruction sending module. The specific functions of the modules are as shown in Embodiment 2. To avoid repetition, details are not described herein.

The terminal device 70 can be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server. Terminal device 70 may include, but is not limited to, processor 71, memory 72. It will be understood by those skilled in the art that FIG. 7 is merely an example of the terminal device 70, and does not constitute a limitation of the terminal device 70, and may include more or less components than those illustrated, or may combine certain components or different components. For example, the terminal device 70 may further include an input/output device, a network access device, a bus, and the like.

The processor 71 may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

The memory 72 may be an internal storage unit of the terminal device 70, such as a hard disk or a memory of the terminal device 70. The memory 72 may also be an external storage device of the terminal device 70, such as a plug-in hard disk provided on the terminal device 70, a smart memory card (SMC), a Secure Digital (SD) card, and a flash memory card (Flash). Card) and so on. Further, the memory 72 may also include both an internal storage unit of the terminal device 70 and an external storage device. Memory 72 is used to store computer readable instructions as well as other programs and data required by terminal device 70. The memory 72 can also be used to temporarily store data that has been or will be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units as needed. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above.

The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.

Claims

A configuration management method, characterized in that the configuration management method comprises the following steps performed by a client:

Receiving code submission application information sent by the user, where the code submission application information includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

Obtaining the to-be-committed code according to the address identification information;

Performing static code check on the to-be-committed code to obtain a static code check report;

Parsing the static code check report, and extracting indicator result data in the static code check report according to a preset indicator;

Sending the indicator result data and the identity identification information to the server;

Sending a code submission request to the configuration management platform, where the code submission request includes the address identification information, the identity identification information, and the branch version information;

If the prompt information including the submission result sent by the configuration management platform is received, the prompt information is fed back to the user.
The configuration management method according to claim 1, wherein the code submission application information further includes a special batch application identifier of the user, and the configuration management method is performed after the code sent by the receiving user submits the application information. It also includes the following steps performed by the client:

Sending a special approval authority application to the preset approver according to the special approval application identifier;

And if the approval result returned by the approver is that the special batch application is successful, sending the special batch permission identification information of the user and the identity identification information of the user to the configuration management platform, so that the configuration management is performed. The platform saves the special batch identification information and the identity information in a permission database.
A configuration management method, characterized in that the configuration management method comprises the following steps performed by the configuration management platform:

Receiving a code submission request sent by the client, where the code submission request includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

Sending a code indicator detection request to the server, so that the server performs index detection on the to-be-committed code, where the code indicator detection request includes the branch version information and the identity identification information;

Receiving an operation instruction returned by the server according to the result of the indicator detection;

If the operation instruction is to allow the submission, the code to be submitted is obtained according to the address identification information, and the code to be submitted is merged into the branch version corresponding to the branch version information, and is successfully sent to the client. Submitted prompt information;

If the operation instruction is to reject the submission, the client sends a prompt message rejecting the submission.
The configuration management method according to claim 3, wherein if the operation instruction is to reject the submission, sending the prompt information to the client to reject the submission includes:

When the operation instruction is to reject the submission, the special permission identification information corresponding to the identity identification information of the user is queried from the permission database;

And if the privilege identifier information corresponding to the identifier information is not empty, the code to be submitted is obtained according to the address identifier information, and the code to be submitted is merged into the branch. In the branch version corresponding to the version information, and sending the prompt information successfully submitted by the special batch permission to the client;

If the identity information is not queried in the privilege database, or if the privilege identity information corresponding to the identity identifier information is vacant, the client sends a prompt message rejecting the submission.
A configuration management method, wherein the configuration management method includes the following steps performed by a server:

Receiving the indicator result data of the static code check report sent by the client and the identity identification information of the user, and storing the indicator result data and the identity identification information in the indicator database;

And acquiring the branch version information and the identity identification information in the code indicator detection request, if the code indicator detection request sent by the configuration management platform is received;

Obtaining preset indicator standard data corresponding to the branch version information according to the branch version information;

Obtaining, by the indicator database, the indicator result data corresponding to the identity identification information;

If it is detected that the indicator result data satisfies the requirement of the indicator standard data, generating an operation instruction that is allowed to be submitted, otherwise generating an operation instruction that refuses to submit;

The operation instruction is sent to the configuration management platform.
A configuration management apparatus, wherein the configuration management apparatus includes a client, and the client includes:

The application receiving module is configured to receive code submission application information sent by the user, where the code submission application information includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

a code obtaining module, configured to acquire the to-be-committed code according to the address identification information;

a code checking module, configured to perform static code check on the to-be-committed code to obtain a static code check report;

An indicator extraction module, configured to parse the static code inspection report, and extract indicator result data in the static code inspection report according to a preset indicator;

An indicator sending module, configured to send the indicator result data and the identity identification information to a server;

a request sending module, configured to send a code submission request to the configuration management platform, where the code submission request includes the address identification information, the identity identification information, and the branch version information;

The information feedback module is configured to: when receiving the prompt information that is sent by the configuration management platform and includes the submission result, feed the prompt information to the user.
The configuration management apparatus according to claim 6, wherein the client of the configuration management apparatus further comprises:

The permission application module is configured to send a special permission application to the preset approver according to the special application identifier;

a permission sending module, configured to send the special batch permission identification information of the user and the identity identification information of the user to the configuration management platform, if the approval result returned by the approver is that the special batch application is successful, The configuration management platform saves the special batch identification information and the identity identification information in a permission database.
A configuration management device, wherein the configuration management device includes a configuration management platform, and the configuration management platform includes:

a request receiving module, configured to receive a code submission request sent by the client, where the code submission request includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

An indicator detection module, configured to send a code indicator detection request to the server, so that the server performs index detection on the to-be-committed code, where the code indicator detection request includes the branch version information and the identity identifier information;

An instruction receiving module, configured to receive an operation instruction returned by the server according to the result of the indicator detection;

a code submission module, configured to: obtain the to-be-committed code according to the address identification information, and merge the to-be-committed code into a branch version corresponding to the branch version information, and The client sends the prompt information successfully submitted;

And an information sending module, configured to send, to the client, prompt information that refuses to submit if the operation instruction is to reject the submission.
The configuration management apparatus according to claim 8, wherein the information sending module comprises:

a permission query unit, configured to query the special batch permission information corresponding to the identity information of the user from the permission database when the operation instruction is to reject the submission;

a code submitting unit, configured to acquire the to-be-submitted code according to the address identification information, if the special batch identification information corresponding to the identity identification information is not empty in the permission database, and the to-be-submitted code is to be submitted The code is merged into the branch version corresponding to the branch version information, and the prompt information that the special batch permission is successfully submitted is sent to the client;

The information sending unit is configured to: if the identity identification information is not queried in the authority database, or if the special batch authorization information corresponding to the identity identification information is vacant, send the reject submission to the client Prompt message.
A configuration management device, wherein the configuration management device includes a server, and the server includes:

The indicator receiving module is configured to receive the indicator result data of the static code check report sent by the client and the identity identification information of the user, and store the indicator result data and the identity identification information in the indicator database;

The information obtaining module is configured to: obtain the branch version information and the identity identification information in the code indicator detection request, if the code indicator detection request sent by the configuration management platform is received;

a data obtaining module, configured to acquire, according to the branch version information, preset indicator standard data corresponding to the branch version information;

An indicator obtaining module, configured to acquire the indicator result data corresponding to the identity identification information from the indicator database;

An instruction generating module, configured to generate an operation instruction that is allowed to be submitted if it is detected that the indicator result data satisfies the requirement of the indicator standard data, and otherwise generate an operation instruction that refuses to submit;

And an instruction sending module, configured to send the operation instruction to the configuration management platform.
A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operative on the processor, wherein the processor implements the client when the computer readable instructions are executed The following steps are performed:

Receiving code submission application information sent by the user, where the code submission application information includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

Obtaining the to-be-committed code according to the address identification information;

Performing static code check on the to-be-committed code to obtain a static code check report;

Parsing the static code check report, and extracting indicator result data in the static code check report according to a preset indicator;

Sending the indicator result data and the identity identification information to the server;

Sending a code submission request to the configuration management platform, wherein the code submission request includes the address identification information, the identity identification information, and the branch version information;

If the prompt information including the submission result sent by the configuration management platform is received, the prompt information is fed back to the user.
The terminal device according to claim 11, wherein the code submission application information further includes a special batch application identifier of the user, and after the code sent by the receiving user submits the application information, the processor executes the The following steps are also implemented when the computer readable instructions are described:

Sending a special approval authority application to the preset approver according to the special approval application identifier;

And if the approval result returned by the approver is that the special batch application is successful, sending the special batch permission identification information of the user and the identity identification information of the user to the configuration management platform, so that the configuration management is performed. The platform saves the special batch identification information and the identity information in a permission database.
A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, wherein the processor implements the configuration when the computer readable instructions are executed The following steps are performed by the management platform:

Receiving a code submission request sent by the client, where the code submission request includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

Sending a code indicator detection request to the server, so that the server performs index detection on the to-be-committed code, where the code indicator detection request includes the branch version information and the identity identification information;

Receiving an operation instruction returned by the server according to the result of the indicator detection;

If the operation instruction is to allow the submission, the code to be submitted is obtained according to the address identification information, and the code to be submitted is merged into the branch version corresponding to the branch version information, and is successfully sent to the client. Submitted prompt information;

If the operation instruction is to reject the submission, the client sends a prompt message rejecting the submission.
The terminal device according to claim 13, wherein if the operation instruction is to reject the submission, sending the prompt information to the client to reject the submission includes:

When the operation instruction is to reject the submission, the special permission identification information corresponding to the identity identification information of the user is queried from the permission database;

And if the privilege identifier information corresponding to the identifier information is not empty, the code to be submitted is obtained according to the address identifier information, and the code to be submitted is merged into the branch. In the branch version corresponding to the version information, and sending the prompt information successfully submitted by the special batch permission to the client;

If the identity identification information is not queried in the privilege database, or the privilege identification information corresponding to the identity identification information is vacant, the prompt information that is rejected is sent to the client.
A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operative on the processor, wherein the processor implements the service when the computer readable instructions are executed The following steps are performed:

Receiving the indicator result data of the static code check report sent by the client and the identity identification information of the user, and storing the indicator result data and the identity identification information in the indicator database;

And acquiring the branch version information and the identity identification information in the code indicator detection request, if the code indicator detection request sent by the configuration management platform is received;

Obtaining preset indicator standard data corresponding to the branch version information according to the branch version information;

Obtaining, by the indicator database, the indicator result data corresponding to the identity identification information;

If it is detected that the indicator result data satisfies the requirement of the indicator standard data, generating an operation instruction that is allowed to be submitted, otherwise generating an operation instruction that refuses to submit;

The operation instruction is sent to the configuration management platform.
One or more non-transitory readable storage mediums storing computer readable instructions, wherein when the computer readable instructions are executed by one or more processors, cause the one or more processors to execute The following steps are implemented when the client performs:

Receiving code submission application information sent by the user, where the code submission application information includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

Obtaining the to-be-committed code according to the address identification information;

Performing static code check on the to-be-committed code to obtain a static code check report;

Parsing the static code check report, and extracting indicator result data in the static code check report according to a preset indicator;

Sending the indicator result data and the identity identification information to the server;

Sending a code submission request to the configuration management platform, where the code submission request includes the address identification information, the identity identification information, and the branch version information;

If the prompt information including the submission result sent by the configuration management platform is received, the prompt information is fed back to the user.
The configuration management method according to claim 16, wherein the code submission application information further includes a special batch application identifier of the user, and the computer is readable after the code sent by the receiving user submits the application information. When the instructions are executed by one or more processors, the one or more processors further perform the following steps:

Sending a special approval authority application to the preset approver according to the special approval application identifier;

And if the approval result returned by the approver is that the special batch application is successful, sending the special batch permission identification information of the user and the identity identification information of the user to the configuration management platform, so that the configuration management is performed. The platform saves the special batch identification information and the identity information in a permission database.
One or more non-transitory readable storage mediums storing computer readable instructions, wherein when the computer readable instructions are executed by one or more processors, cause the one or more processors to execute The following steps are implemented to implement the configuration management platform:

Receiving a code submission request sent by the client, where the code submission request includes address identification information of the to-be-committed code, identity identification information of the user, and branch version information;

Sending a code indicator detection request to the server, so that the server performs index detection on the to-be-committed code, where the code indicator detection request includes the branch version information and the identity identification information;

Receiving an operation instruction returned by the server according to the result of the indicator detection;

If the operation instruction is to allow the submission, the code to be submitted is obtained according to the address identification information, and the code to be submitted is merged into the branch version corresponding to the branch version information, and is successfully sent to the client. Submitted prompt information;

If the operation instruction is to reject the submission, the client sends a prompt message rejecting the submission.
The non-volatile readable storage medium according to claim 18, wherein if the operation instruction is to reject the submission, sending the prompt information to the client to reject the submission comprises:

When the operation instruction is to reject the submission, the special permission identification information corresponding to the identity identification information of the user is queried from the permission database;

And if the privilege identifier information corresponding to the identifier information is not empty, the code to be submitted is obtained according to the address identifier information, and the code to be submitted is merged into the branch. In the branch version corresponding to the version information, and sending the prompt information successfully submitted by the special batch permission to the client;

If the identity identification information is not queried in the privilege database, or the privilege identification information corresponding to the identity identification information is vacant, the prompt information that is rejected is sent to the client.
One or more non-transitory readable storage mediums storing computer readable instructions, wherein when the computer readable instructions are executed by one or more processors, cause the one or more processors to execute The following steps are implemented to implement the server:

Receiving the indicator result data of the static code check report sent by the client and the identity identification information of the user, and storing the indicator result data and the identity identification information in the indicator database;

And acquiring the branch version information and the identity identification information in the code indicator detection request, if the code indicator detection request sent by the configuration management platform is received;

Obtaining preset indicator standard data corresponding to the branch version information according to the branch version information;

Obtaining, by the indicator database, the indicator result data corresponding to the identity identification information;

If it is detected that the indicator result data satisfies the requirement of the indicator standard data, generating an operation instruction that is allowed to be submitted, otherwise generating an operation instruction that refuses to submit;

The operation instruction is sent to the configuration management platform.