Configuration library information specification checking method and device, equipment and storage medium

Abstract

This application provides a method, apparatus, device, and storage medium for checking the standardization of configuration library information. It relates to the field of big data processing technology. The method includes: acquiring the field information of the item to be checked, performing a standardization check on the field information based on preset standardization rules, and, if the field information conforms to the standardization, obtaining the target field information corresponding to the item to be checked from the configuration library through a configuration library interface; and determining the standardization of the item to be checked in the configuration library based on the field information and the target field information. This method can automatically check the standardization of the field information based on standardization rules, and since it obtains the field information through an interface for checking without needing to fetch code, it can save manpower and time costs and improve the efficiency of configuration library standardization checks.

Description

Technical Field

[0001] This application relates to the field of big data processing technology, and in particular to a method, apparatus, device and storage medium for checking the standardization of configuration library information. Background Technology

[0002] With the development of computer technology, software code versions are constantly iterating and updating. Currently, configuration repositories are typically used to manage various version information, so the standardization of these repositories directly impacts version management efficiency. Currently, the standardization of information in the configuration repository is generally checked manually. Furthermore, the process of checking configuration repository standardization involves downloading code repositories or pulling code from Jenkins for analysis, resulting in long transmission times and high resource consumption. Therefore, the efficiency of existing configuration repository standardization checking methods needs improvement. Summary of the Invention

[0003] This application provides a method, apparatus, device, and storage medium for checking the standardization of configuration library information, aiming to at least partially solve one of the technical problems in related technologies.

[0004] Firstly, this application provides a method for checking the standardization of configuration library information, including: obtaining the field information to be filled in for the item to be checked; performing a standardization check on the field information based on preset standardization rules; if the field information conforms to the standardization, obtaining the target field information corresponding to the item to be checked from the configuration library through the configuration library interface; and determining the standardization of the item to be checked in the configuration library based on the field information and the target field information.

[0005] Secondly, this application provides a configuration library information standardization checking device, comprising: a first acquisition module for acquiring field information of the item to be checked; an inspection module for performing standardization checks on the field information based on preset standardization rules; a second acquisition module for acquiring target field information corresponding to the item to be checked from the configuration library through the configuration library interface when the field information conforms to the standardization; and a determination module for determining the standardization of the item to be checked in the configuration library based on the field information and the target field information.

[0006] Thirdly, this application provides an electronic device, including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to execute instructions to implement a configuration library information conformity check method.

[0007] Fourthly, this application provides a computer-readable storage medium that, when the instructions in the computer-readable storage medium are executed by the processor of an electronic device, enables the electronic device to perform a configuration library information conformity check method.

[0008] Fifthly, this application provides a computer program product, including a computer program, wherein the computer program is executed by a processor using a method for checking the conformity of configuration library information.

[0009] The configuration library information standardization checking method, apparatus, device, and storage medium provided in this application obtain the field information of the item to be checked, and perform standardization checks on the field information based on preset standardization rules. If the field information conforms to the standard, the target field information corresponding to the item to be checked is obtained from the configuration library through the configuration library interface. Based on the field information and the target field information, the standardization of the item to be checked in the configuration library is determined. It can automatically check the standardization of the information based on the standardization rules, and the field information is obtained through the interface for checking without the need to pull code. Therefore, it can save manpower and time costs and improve the efficiency of configuration library standardization checking. Attached Figure Description

[0010] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0011] Figure 1 This is a flowchart illustrating the configuration library information conformity check method according to the first embodiment of this application;

[0012] Figure 2 This is a schematic diagram of the structure of an automated configuration library checking system according to an embodiment of this application;

[0013] Figure 3 This is a flowchart illustrating the configuration library information conformity check method according to the second embodiment of this application;

[0014] Figure 4 This is a schematic diagram illustrating the configuration library information conformity check process according to an embodiment of this application;

[0015] Figure 5 This is a block diagram of a configuration library information conformity check device according to this application;

[0016] Figure 6 A block diagram of an exemplary electronic device suitable for implementing embodiments of the present application is shown.

[0017] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0018] The embodiments of this application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application. Rather, the embodiments of this application include all variations, modifications, and equivalents falling within the spirit and scope of the appended claims.

[0019] It should be noted that the execution subject of the configuration library information standardization check method in this embodiment can be a configuration library information standardization check device. This device can be implemented by software and / or hardware. This device can be configured in an electronic device, which may include, but is not limited to, a terminal, a server, etc.

[0020] Figure 1 This is a flowchart illustrating the configuration library information conformity check method according to the first embodiment of this application, as shown below. Figure 1 As shown, the method includes:

[0021] S101: Obtain the information of the fields to be filled in for the item to be inspected.

[0022] As described in the background section, a configuration repository is used to manage various information about project versions. In this embodiment, the configuration repository may include, for example, a code repository, a documentation repository, and any other possible information repository. The various information (information items) managed by the configuration repository may include, for example, project deployment tags, delivery documents, the master branch, merged branches of the master branch, and any other possible information, without limitation. In practical applications, before a project is deployed, it is necessary to check the standardization of project-related information in the configuration repository. For example, whether the deployment tag naming conforms to the standard, whether the development branch code has been merged into the master branch, whether the delivery document naming conforms to the standard, and whether the delivery document has been submitted completely. Therefore, this embodiment first obtains the field information of the items to be checked.

[0023] In this system, any information item in the configuration library can be used as an item to be checked. Examples of items to be checked include the production tag name, the delivery document name, the code branch name, and whether the development branch code has been merged into the main branch. Furthermore, there can be one or more items to be checked; this is not limited. In some embodiments, one or more items to be checked can be pre-set for the user to choose from.

[0024] The field information filled in by the user (project leader) for the item to be inspected can be called the field information (or project production information). For example, if the item to be inspected is the production label name, then the field information is the project production label name; or if the item to be inspected is the delivery document name, then the field information is the project delivery document name. There are no restrictions on this.

[0025] To implement the method for checking the standardization of configuration library information, this disclosure also provides an automated configuration library checking system. Figure 2 This is a schematic diagram of the structure of an automated configuration library checking system according to an embodiment of this application, as shown below. Figure 2 As shown, the system consists of a front-end and a back-end. The front-end includes an information entry list page (containing one or more items to be checked), a standard rule setting interface, and a configuration interface, while the back-end includes a database module and an inspection and judgment module.

[0026] In practical applications, items to be checked can be pre-configured on the information entry list page, allowing users to fill in information for these items. Specifically, the information entry list page supports functions such as adding, querying, canceling, exporting, editing, and checking. Clicking "Add" leads to the entry page, where users can fill in information for one or more items to be checked (e.g., production tag naming, delivery document naming, and whether development branch code has been merged into the main branch). After submission, the information is displayed in a list format, and clicking on the list data allows viewing details. Users can also select the "Cancel" option for one or more items to be checked, thus preventing that item from undergoing candidate standardization checks. After completion, clicking "Edit" allows modification of the entered information. Users can also query entered information based on filter criteria. Furthermore, clicking the "Export" function allows exporting the entered information. In this case, the system can retrieve the entered information.

[0027] S102: Perform a standardization check on the information in the fields filled in based on preset standardization rules.

[0028] In this embodiment, a standard rule (also called a standard parameter) is pre-configured for each item to be inspected. This standard rule can be any rule, and there are no restrictions on it.

[0029] In some embodiments, the specification rules can be format rules for the items to be checked; that is, a format specification is configured for each item to be checked. For example, if the item to be checked is a code branch name, the specification format for code branch naming is like "dev_year / month / day", that is, "dev_year / month / day" is used as the specification rule for code branch naming (item to be checked); or, for example, if the delivery document naming (item to be checked) requires the document extension to be ".doc", then the specification rule corresponding to this item to be checked is "filename.doc". In this embodiment, the specification rules can be stored in the system's backend database.

[0030] It is understood that different specification rules can be configured for different items to be inspected, and this embodiment can configure corresponding specification rules for new items to be inspected without limitation.

[0031] In this embodiment, after obtaining the field information, the system (inspection and judgment module) first obtains the standard rules corresponding to the items to be inspected from the database, and then performs a standardization check on the field information based on the preset standard rules, that is, to determine whether the field information conforms to the standard rules.

[0032] For example, if a user enters "project document.pdf" as the field for naming the delivered document (item to be checked), but the standard rule for this item is "filename.doc", then the entered field does not conform to the standard rule and therefore fails the standardization check. On the other hand, if a user enters "dev_20220902" as the field for naming the code branch (item to be checked), which conforms to the standard rule of "dev_year / month / day", then this entered field passes the standardization check.

[0033] The system can filter and mark items that fail the standardization check, allowing users to correct errors in the fields they enter.

[0034] This embodiment can automatically check the conformity of the information filled in based on the standard rules, thus replacing manual checking and saving labor costs.

[0035] S103: If the field information is in compliance with the specifications, retrieve the target field information corresponding to the item to be checked from the configuration library through the configuration library interface.

[0036] In this embodiment of the disclosure, an interface can be configured for the configuration library, namely: the configuration library interface. For example, the environment can be configured for the configuration library interface address in the configuration interface, and information such as the configuration library system address and token can be filled in.

[0037] Among them, the field information corresponding to the item to be checked obtained from the configuration library can be referred to as the target field information.

[0038] For example, if the item to be checked is the name of the delivery document, this embodiment can obtain the name of the project's delivery document from the configuration library (specifically from the document library) through the configuration library interface. The obtained delivery document name is called the target field information.

[0039] This embodiment obtains field information through an interface for inspection instead of fetching all the code, thus saving manpower and time costs.

[0040] S104: Based on the information entered and the target field information, determine the standardization of the items to be checked in the configuration library.

[0041] In some embodiments, the field information corresponding to each item to be checked can be matched with the target field information. Since the field information passes the standardization check, if the field information and the target field information are consistent, it can be determined that the item to be checked in the configuration library also conforms to the standard. Otherwise, it is determined that the item to be checked in the configuration library does not conform to the standard, and the item to be checked that does not conform to the standard is marked.

[0042] In this embodiment, the information of the fields to be checked is obtained, and the information is checked for compliance based on preset standard rules. If the information conforms to the standard, the target field information corresponding to the item to be checked is obtained from the configuration library through the configuration library interface. Based on the information of the fields to be checked and the target field information, the compliance of the item to be checked in the configuration library is determined. The compliance of the information can be automatically checked based on the standard rules, and the field information is obtained through the interface for checking without the need to pull code. Therefore, it can save manpower and time costs and improve the efficiency of configuration library compliance checking.

[0043] It should be noted that the acquisition, storage, and application of data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0044] Figure 3 This is a flowchart illustrating the configuration library information conformity check method according to the second embodiment of this application, as shown below. Figure 3 As shown, the method includes:

[0045] S301: Obtain the information of the fields to be filled in for the item to be inspected.

[0046] S302: Perform a standardization check on the information in the fields filled in based on preset standardization rules.

[0047] S303: If the field information is in compliance with the specifications, retrieve the target field information corresponding to the item to be checked from the configuration library via the configuration library interface.

[0048] For detailed descriptions of S301-303, please refer to the above embodiments, which will not be repeated here.

[0049] S304: Traverse the target field information based on the information entered into the field.

[0050] In the operation of determining the standardization of the items to be checked in the configuration library based on the filled field information and the target field information, the embodiments of this disclosure can traverse the target field information based on the filled field information to determine whether the target field information contains the filled field information.

[0051] In some embodiments, the items to be checked include, for example, the production label name. The user can fill in the production label name of the project. The filled production label name is used as the field information. Correspondingly, the production label name obtained from the configuration library is used as the target field information. This embodiment can traverse the obtained production label names based on the filled production label name to determine whether the production label names in the configuration library contain the filled production label name.

[0052] In other embodiments, the items to be checked may include, for example, delivery document names. In this case, the user can fill in one or more delivery document names for the project (i.e., at least one delivery document name). The filled delivery document name is used as the field information, and the corresponding delivery document names obtained from the configuration library are used as the target field information. In this embodiment, based on the filled at least one delivery document name, the obtained delivery document names are traversed to determine whether the delivery document names in the configuration library contain all the filled delivery document names.

[0053] In other embodiments, the items to be checked include, for example, whether the branch has been merged, that is, whether the target branch has been merged into the project's master branch. In the traversal process, this embodiment uses the first code of the most recent commit of the target branch to traverse and obtain the second code of the master branch having merged multiple branches.

[0054] Specifically, users can fill in the commit ID of the most recent commit on the target branch on the page. This commit ID is referred to as the first code. It's understood that each time a branch is committed to the configuration repository, it is merged into the main branch. Therefore, this embodiment can obtain the commit IDs of multiple (n) branches merged into the project's main branch (master branch) from the configuration repository (specifically, from the code repository). These commit IDs can be referred to as the second code. In practical applications, the second codes of the branches merged into the master branch in the most recent n merges can be obtained, and these n second codes are used as the target field information. In this case, this embodiment can, based on the filled-in first code, traverse the second codes of multiple branches (n branches) to determine whether the first code is included among the n second codes.

[0055] S305: If the information in the fields to be filled in is found, determine that the items to be checked in the configuration library meet the specifications; otherwise, determine that the items to be checked in the configuration library do not meet the specifications and mark them.

[0056] In other words, if the information in the field to be filled is reached during the iteration (and the iteration yields results), such as the production tag name, and / or all delivery document names, and / or the first code, it means that there is a corresponding item to be checked in the configuration library and the item to be checked also conforms to the specifications. That is, the project's production tag, delivery documents, and target branch have been submitted to the configuration library and conform to the specifications.

[0057] If no information is found in the fields to be filled in (i.e., no results are found during the iteration), it means that there are no production tags, delivery documents, or target branches for the project in the configuration library, or that the production tags, delivery documents, or target branches for the project do not conform to the specifications. In this case, it is determined that the items to be checked in the configuration library do not conform to the specifications and are marked accordingly.

[0058] In some embodiments, if there are multiple items to be checked (e.g., production tag naming, delivery document naming, and whether branches are merged), this embodiment determines that the items to be checked in the configuration library conform to the specifications if all the fields of the items to be checked have been traversed; if at least one field of the items to be checked has not been traversed, that is, if at least one does not conform to the specifications, then it is determined that the items to be checked in the configuration library do not conform to the specifications, and the non-conforming items are marked so that users can find out the cause and correct it in time.

[0059] Therefore, the embodiments of this disclosure perform a fast and efficient standardization check on the configuration library by traversing the library, thereby improving the check speed and reducing computational complexity.

[0060] In this embodiment, the information of the fields to be checked is obtained, and the information is checked for compliance based on preset standardization rules. If the information conforms to the standards, the target field information corresponding to the item to be checked is retrieved from the configuration library via a configuration library interface. Based on the information of the fields to be checked and the target field information, the compliance of the item to be checked in the configuration library is determined. This allows for automatic checking of the compliance of the information based on standardization rules. Furthermore, since the check is performed by retrieving field information through an interface without needing to fetch code, it saves manpower and time costs and improves the efficiency of configuration library compliance checks. In addition, this embodiment uses a traversal approach to quickly check the compliance of the configuration library, improving the checking speed and reducing computational complexity.

[0061] In practical applications, Figure 4 This is a schematic diagram illustrating the configuration library information conformity check process according to an embodiment of this application, such as... Figure 4As shown, the project team fills in the production configuration library information (filled field information) in the system, and the configuration administrator sets the standard format parameters (standard rules) and configures the interface environment information (configuration library interface). Further, the filled information is batch-checked and verified according to the standard parameters (standardization check). If it conforms to the standard (i.e., passes the standardization check), the relevant configuration library information (target field information) is obtained from the webpage through the interface based on the filled information; otherwise, information that does not conform to the standard is filtered out and corrected. Further, the naming standard is checked, with the rule: relevant information obtained from the configuration library is compared with the filled information; if it conforms to the standard, the check ends; otherwise, information that does not conform to the standard is filtered out and corrected. Similarly, code branch merging is checked, with the rule: the most recent commit ID of the current production development branch is obtained and the master branch IDs are traversed; if found, it indicates conformity to the standard, and the check ends; otherwise, correction is performed. Similarly, document submission integrity is checked, with the rule: document name information is obtained from the document repository and compared with the filled information; if it conforms to the standard, the check ends; otherwise, information that does not conform to the standard is filtered out and corrected.

[0062] Figure 5 This is a block diagram of a configuration library information conformity checking device according to this application, such as... Figure 5 As shown, the configuration library information conformity check device 50 includes:

[0063] The first acquisition module 501 is used to acquire the information of the fields to be filled in for the item to be inspected;

[0064] The inspection module 502 is used to perform a standardization check on the information in the fields filled in based on preset standardization rules;

[0065] The second acquisition module 503 is used to obtain the target field information corresponding to the item to be checked from the configuration library through the configuration library interface when the field information filled in conforms to the specification.

[0066] The determination module 504 is used to determine the standardization of the items to be checked in the configuration library based on the information entered in the fields and the target fields.

[0067] In some embodiments, determining module 504 includes:

[0068] The traversal submodule is used to traverse the target field information based on the information entered into the field;

[0069] The determination submodule is used to determine whether the items to be checked in the configuration library conform to the specifications when the information of the fields to be filled in is traversed; otherwise, it determines that the items to be checked in the configuration library do not conform to the specifications and marks them.

[0070] In some embodiments, the items to be checked include production label naming and / or delivery document naming. The traversal submodule is specifically used for: traversing the obtained production label names based on the filled-in production label names; and / or traversing the obtained delivery document names based on at least one filled-in delivery document name, wherein the filled-in production label names and at least one delivery document name are used as filled-in field information, and the obtained production label names and delivery document names are used as target field information.

[0071] In some embodiments, the items to be checked include whether the branch has been merged. The traversal submodule is specifically used to: based on the first code of the most recent commit of the target branch, traverse to obtain the second code of the main branch that has merged multiple branches, wherein the first code is used as the field information to be filled in, and the second code is used as the target field information.

[0072] In some embodiments, the determination submodule is specifically used for: determining that the items to be checked in the configuration library conform to the specifications when all the fields of the items to be checked have been traversed; and determining that the items to be checked in the configuration library do not conform to the specifications and marking them when the fields of at least one item to be checked have not been traversed.

[0073] In this embodiment, the information of the fields to be checked is obtained, and the information is checked for compliance based on preset standard rules. If the information conforms to the standard, the target field information corresponding to the item to be checked is obtained from the configuration library through the configuration library interface. Based on the information of the fields to be checked and the target field information, the compliance of the item to be checked in the configuration library is determined. The compliance of the information can be automatically checked based on the standard rules, and the field information is obtained through the interface for checking without the need to pull code. Therefore, it can save manpower and time costs and improve the efficiency of configuration library compliance checking.

[0074] According to embodiments of this application, this application also provides an electronic device, a readable storage medium, and a computer program product.

[0075] Figure 6 This is a block diagram of an electronic device according to this application. For example, electronic device 500 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0076] Reference Figure 6 The electronic device 500 may include one or more of the following components: processing component 502, memory 504, power supply component 506, multimedia component 508, audio component 510, input / output (I / O) interface 512, sensor component 514, and communication component 516.

[0077] Processing component 502 typically controls the overall operation of electronic device 500, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 502 may include one or more processors 620 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 502 may include one or more modules to facilitate interaction between processing component 502 and other components. For example, processing component 502 may include a multimedia module to facilitate interaction between multimedia component 508 and processing component 502.

[0078] Memory 504 is configured to store various types of data to support the operation of electronic device 500. Examples of such data include instructions for any application or method operating on electronic device 500, contact data, phonebook data, messages, pictures, videos, etc. Memory 504 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0079] Power supply component 506 provides power to various components of electronic device 500. Power supply component 506 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 500.

[0080] Multimedia component 508 includes a touch display screen that provides an output interface between electronic device 500 and user. In some embodiments, the touch display screen may include a liquid crystal display (LCD) and a touch panel (TP). The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 508 includes a front-facing camera and / or a rear-facing camera. When electronic device 500 is in an operating mode, such as a shooting mode or video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0081] Audio component 510 is configured to output and / or input audio signals. For example, audio component 510 includes a microphone (MIC) configured to receive external audio signals when electronic device 500 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 504 or transmitted via communication component 516.

[0082] In some embodiments, the audio component 510 further includes a speaker for outputting audio signals.

[0083] I / O interface 512 provides an interface between processing component 502 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0084] Sensor assembly 514 includes one or more sensors for providing state assessments of various aspects of electronic device 500. For example, sensor assembly 514 may detect the on / off state of electronic device 500, the relative positioning of components such as the display and keypad of electronic device 500, changes in position of electronic device 500 or a component of electronic device 500, the presence or absence of user contact with electronic device 500, orientation or acceleration / deceleration of electronic device 500, and temperature changes of electronic device 500. Sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 514 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0085] Communication component 516 is configured to facilitate wired or wireless communication between electronic device 500 and other devices. Electronic device 500 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 516 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 516 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0086] In an exemplary embodiment, the electronic device 500 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above-described configuration library information conformity check method.

[0087] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 504 including instructions, which can be executed by a processor 920 of an electronic device 500 to perform the above-described method. Optionally, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0088] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0089] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for checking the standardization of configuration library information, characterized in that, include: Obtain the field information of the items to be inspected, wherein the items to be inspected include at least one of the following: production tag naming, delivery document naming, or branch merging status; The information in the fields to be filled in is checked for compliance based on preset standard rules; If the filled field information conforms to the specifications, the target field information corresponding to the item to be checked is obtained from the configuration library through the configuration library interface. The target field information is the field information corresponding to the item to be checked stored in the configuration library, including at least one of the production tag name, delivery document name or branch commit code. Based on the filled-in field information and the target field information, the standardization of the item to be checked in the configuration library is determined, including: Based on the information filled in the fields, the target field information is traversed. The item to be checked includes whether the branch has been merged. This includes: based on the first code of the most recent commit of the target branch, the second code of the main branch that has merged multiple branches is obtained through traversal. The first code is used as the information filled in the fields, and the second code is used as the target field information. Each time a branch is committed to the configuration repository, it is merged into the main branch. The commit codes of the project's main branch that have merged multiple branches are obtained from the configuration repository. The commit codes are called the second codes. If all the fields filled in for inspection are traversed, it is determined that the items to be inspected in the configuration library conform to the specifications. If the information in the fields of at least one item to be inspected is not traversed, it is determined that the item to be inspected in the configuration library does not conform to the specification, and the item to be inspected that does not conform to the specification is marked.

2. The method according to claim 1, characterized in that, in, The items to be inspected include production label naming and / or delivery document naming. The step of traversing the target field information based on the filled-in field information includes: Based on the submitted production label name, iterate through the obtained production label names; and / or Based on the at least one delivery document name filled in, the obtained delivery document names are traversed, wherein the filled-in production tag name and the at least one delivery document name are used as the filling field information, and the obtained production tag name and delivery document name are used as the target field information.

3. A device for checking the standardization of configuration library information, characterized in that, include: The first acquisition module is used to acquire the field information of the items to be inspected, wherein the items to be inspected include at least one of the following: production tag naming, delivery document naming, or branch merging status. The inspection module is used to perform a standardization check on the information in the fields to be filled in based on preset standard rules; The second acquisition module is used to acquire target field information corresponding to the item to be inspected from the configuration library through the configuration library interface when the filled field information conforms to the specification. The target field information is the field information corresponding to the item to be inspected stored in the configuration library, including at least one of production tag name, delivery document name or branch commit code. The determination module is used to determine the standardization of the items to be checked in the configuration library based on the information filled in the fields and the target field information; The determining module includes: The traversal submodule is used to traverse the target field information based on the filled-in field information, wherein the item to be checked includes whether the branch is merged. Specifically, the traversal submodule is used for: Based on the first code of the most recent commit of the target branch, the second code of the main branch that has been merged with multiple branches is obtained by traversing. The first code is used as the field information to be filled in, and the second code is used as the target field information. Each time a branch is committed to the configuration repository, it is merged into the main branch. The commit codes of the project's main branch that have been merged with multiple branches are obtained from the configuration repository. The commit codes are called the second codes. The determination submodule is used to determine whether the items to be checked in the configuration library conform to the specifications when all the fields of the items to be checked have been traversed; and to determine whether the items to be checked in the configuration library do not conform to the specifications when the fields of at least one item to be checked have not been traversed, and to mark the items to be checked that do not conform to the specifications.

4. The apparatus according to claim 3, characterized in that, in, The items to be inspected include production label naming and / or delivery document naming. The traversal submodule is specifically used for: Based on the submitted production label name, iterate through the obtained production label names; and / or Based on the at least one delivery document name filled in, the obtained delivery document names are traversed, wherein the filled-in production tag name and the at least one delivery document name are used as the filling field information, and the obtained production tag name and delivery document name are used as the target field information.

5. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-2.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-2.

7. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-2.

Images