Code warehousing management method and device and electronic equipment
By using the target pre-flight configuration table in the code inlet management method for focus review, the problem of low code development efficiency in the existing technology is solved, and the flexibility and efficiency of code inlet management is achieved.
Patent Information
- Application Number
- CN202411033646.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-30
- Publication Date
- 2024-12-13
AI Technical Summary
In the prior art, during the pre-checking process of submitting codes, focus review cannot be carried out according to different stages of the code, resulting in inefficient development.
By obtaining the target pre-flight configuration table in the preset configuration table library, the code pre-flight tasks are determined based on the current stage information of the code, including static code review, dynamic access review, physical implementation review and custom review. If the results meet the access The policy executes the code into the library.
It realizes review of code with different focus at different stages, improving the efficiency of code development and flexibility of code library management.
Smart Images
Figure CN119127663A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of code management, and in particular to a code storage management method, device and electronic equipment. Background Art
[0002] In order to improve the quality of the code merged into the main branch, currently, in software development projects, it is common to pre-check the submitted code before the code is submitted (pre-commit) or pushed to the remote repository (pre-push) to avoid merging low-quality code into the main branch. The way to pre-check the submitted code is generally to execute a custom check script. The custom check script performs the same check on the code at different stages, and cannot focus on reviewing the code at different stages. As a result, users need to modify non-critical errors at the current stage, resulting in relatively low development efficiency. Summary of the invention
[0003] The present application provides a code repository management method, device and electronic device to solve the defect of performing the same check on codes at different stages in the prior art, and can improve the efficiency of code development.
[0004] The present application provides a code warehousing management method, comprising: obtaining the code to be submitted based on the user's submission instruction, and obtaining the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, the preset configuration table library includes multiple pre-check configuration tables, the pre-check configuration table corresponds to the stage information of the code to be submitted, and the target pre-check configuration table includes a code pre-check strategy and a code access determination strategy; determining a code pre-check task according to the code pre-check strategy; performing a target review on the code to be submitted based on the code pre-check task, and obtaining a target review result; if the target review result meets the code access determination strategy, executing code warehousing.
[0005] According to a code repository management method provided by the present application, the code pre-check task includes a static code review task; based on the code pre-check task, a target test is performed to obtain a target test result, including: obtaining the code to be submitted in the temporary storage area; based on the static code review task, a first target interface is called to perform a static code check on the code to be submitted to obtain a static code check result; based on a target keyword in a preset quality keyword library, corresponding prompt information is obtained from the static code check result to obtain a static code review result.
[0006] According to a code warehousing management method provided by the present application, the code pre-check task also includes a dynamic access review task; based on the code pre-check task, the target is tested to obtain the target test result, and it also includes: obtaining the code to be submitted in the temporary storage area; based on the dynamic access test task, calling the second target interface, loading the target test vector in the preset dynamic access test vector set, simulating the code to be submitted, and obtaining the dynamic access review result.
[0007] According to a code warehousing management method provided by the present application, the code pre-check task also includes a physical implementation review task; based on the code pre-check task, a target test is performed to obtain a target test result, and it also includes: obtaining the code to be submitted in the temporary storage area; based on the physical implementation review task, a third target interface is called to perform a physical implementation evaluation on the code to be submitted to obtain a physical implementation evaluation result; and the physical implementation evaluation result is compared with the target indicator in the preset indicator library to obtain a physical implementation review result.
[0008] According to a code warehousing management method provided by the present application, the code pre-check task also includes a custom review task; based on the code pre-check task, a target test is performed to obtain a target test result, and it also includes: obtaining the code to be submitted in the temporary storage area; based on the custom review task, a file compliance review is performed on the code to be submitted to obtain a custom review result.
[0009] According to a code warehousing management method provided by the present application, if the target review result complies with the code access determination policy, code warehousing is executed, including: if the static code review result, the dynamic access review result, the physical implementation review result and the custom review result comply with the code access determination policy, code warehousing is executed.
[0010] According to a code warehousing management method provided by the present application, the code to be submitted and the target pre-inspection configuration table are obtained based on the user's submission instruction, and before the code to be submitted is stored in a temporary storage area, the method also includes: turning on log recording to record the user's submission instruction history, as well as the pre-inspection process of the code to be submitted corresponding to the submission instruction and the target review result, and generating a pre-inspection log.
[0011] According to a code warehousing management method provided by the present application, based on the user's submission instruction, the code to be submitted and the target pre-check configuration table are obtained, and after the code to be submitted is stored in a temporary storage area, the method further includes: returning a notification to the user that the code to be submitted has entered the pre-check; based on the code pre-check task, the code to be submitted is subjected to a target review, and after the target review result is obtained, the method further includes: if the target review result does not comply with the code admission determination policy, returning a notification of rejecting code admission and the pre-check log to the user; if the target review result complies with the code admission determination policy, after executing the code admission, the method further includes: returning a notification to the user that the code to be submitted has executed the code admission and the pre-check log.
[0012] The present application also provides a code warehousing management device, including a target pre-check configuration table acquisition module, which is used to obtain the code to be submitted based on the user's submission instruction, and obtain the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, the preset configuration table library includes multiple pre-check configuration tables, the pre-check configuration table corresponds to the stage information of the code to be submitted, and the target pre-check configuration table includes a code pre-check strategy and a code access determination strategy; a code pre-check task determination module, which is used to determine the code pre-check task according to the code pre-check strategy; a target review result acquisition module, which is used to perform a target review on the code to be submitted based on the code pre-check task and obtain a target review result; a code warehousing execution module, which is used to execute code warehousing if the target review result meets the code access determination strategy.
[0013] The present application also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of any of the above-mentioned code storage management methods are implemented.
[0014] The code warehousing management method, device and storage medium provided by the present application obtain the code to be submitted based on the user's submission instruction, and obtain the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, determine the code pre-check task according to the code pre-check strategy in the target pre-check configuration table, perform a target review on the code to be submitted based on the code pre-check task, and obtain the target review result; if the target review result meets the code access determination strategy, execute code warehousing, and by using different pre-check configuration tables to review the code to be submitted at different stages, it is possible to facilitate the review of the code to be submitted with different focuses at different stages, so that the code warehousing management is flexible and the code development efficiency is improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] In order to more clearly illustrate the technical solutions in the present application or the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0016] Figure 1 This is one of the flow charts of the code storage management method provided by this application.
[0017] Figure 2 It is a module diagram of the code storage management system of the application code storage management method provided in this application.
[0018] Figure 3 This is the second flowchart of the code storage management method provided by this application.
[0019] Figure 4 It is a structural diagram of the code storage management device provided by this application.
[0020] Figure 5 It is a structural schematic diagram of the electronic device provided by this application. DETAILED DESCRIPTION
[0021] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions in this application will be clearly and completely described below in conjunction with the drawings in this application. Obviously, the described embodiments are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0022] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0023] Combine the following Figure 1-Figure 5 The code storage management method, device and electronic device of the present application are described.
[0024] Figure 1This is a flowchart of the code storage management method provided by this application, such as Figure 1 As shown, the method includes the following: Step 110: obtaining the code to be submitted based on the user's submission instruction, and obtaining the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, wherein the preset configuration table library includes multiple pre-check configuration tables, and the pre-check configuration table corresponds to the stage information of the code to be submitted, and the target pre-check configuration table includes a code pre-check strategy and a code access determination strategy.
[0025] The stage information of the code to be submitted may include information such as the development stage and / or development level of the code to be submitted. The development stage may include stages such as initial design, development iteration, design delivery and design freeze, and the development level may include development levels such as module level, subsystem level and chip level. In one embodiment, the stage information of the code to be submitted is that the code to be submitted is in the initial design stage. In another embodiment, the stage information of the code to be submitted is that the code to be submitted is in the module-level development level. In yet another embodiment, the stage information of the code to be submitted is that the code to be submitted is in the module-level development level of the initial design stage.
[0026] Each pre-check configuration table includes a code pre-check strategy and a code admission judgment strategy. The code pre-check strategies in different pre-check configuration tables are different, and the code pre-check strategy and the code admission judgment strategy in each pre-check configuration table correspond to each other. The pre-check strategy is a strategy that performs a series of automated checks and tests on the code to be submitted before submitting it to the version library. The code admission judgment strategy is a strategy that determines whether the results of the aforementioned series of automated checks and tests meet the predetermined standards. The combination of the code pre-check strategy and the code admission judgment strategy can ensure that the quality of the code submitted to the version library meets the predetermined standards.
[0027] Step 120: Determine a code pre-check task according to the code pre-check strategy.
[0028] The code pre-check task is a specific task item for performing a series of automated checks and tests on the submitted code. Among them, the code pre-check strategies in different pre-check configuration tables are different, and the code pre-check tasks corresponding to different code pre-check strategies are also different.
[0029] Step 130: Perform a target review on the code to be submitted based on the code pre-check task to obtain a target review result.
[0030] Target review is the execution of a series of automated checks and tests, and the target review results are the results obtained by executing a series of automated checks and tests.
[0031] Step 140: If the target review result meets the code access determination policy, the code is stored in the database.
[0032] For example, if the target review results of a preset ratio of code pre-check tasks meet the preset standards of the code admission judgment strategy, the code will be put into the repository. Alternatively, if the target review results of each code pre-check task fall within the preset standard range of the code admission judgment strategy, the code will be put into the repository, etc.
[0033] The code warehousing management method provided in the embodiment of the present application obtains the code to be submitted based on the user's submission instruction, and obtains the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, determines the code pre-check task according to the code pre-check strategy in the target pre-check configuration table, performs a target review on the code to be submitted based on the code pre-check task, and obtains the target review result; if the target review result meets the code access determination strategy, the code warehousing is executed, and by using different pre-check configuration tables to review the code to be submitted at different stages, it is convenient to review the code to be submitted with different emphases at different stages, so that the code warehousing management is flexible and the code development efficiency is improved.
[0034] In one embodiment, before obtaining the code to be submitted based on the user's submission instruction and obtaining the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, the method further includes: determining whether to perform a review judgment; if so, obtaining the code to be submitted based on the user's submission instruction, and obtaining the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted; if not, obtaining the code to be submitted based on the user's submission instruction and executing code entry. Direct execution of code entry can adapt to some special situations, such as when the code in the current version library has an error that needs to be fixed urgently. By determining whether to perform a review judgment, the flexibility of the code entry management method can be increased.
[0035] In one embodiment, in order to facilitate the storage of the phased developed code in the library, step 110 can specifically monitor the user's code submission action in real time, and obtain the code to be submitted based on the hooks function after monitoring the user's submission instruction. Exemplarily, the user can be a developer of target code such as HDL, and the code to be submitted can be target code such as HDL code. Based on the hook function of GIT, before the code is submitted (pre-commit) or pushed to the remote warehouse (pre-push), the code to be submitted can be obtained based on the user's submission instruction. According to the code hierarchy mapping table, a corresponding directory is established in the temporary storage area according to the tree relationship to store the code to be submitted. The code hierarchy mapping table is mapped and arranged according to the hierarchical call relationship of the code to be submitted.
[0036] Among them, GIT's hook function or GIT Hooks or GIT hooks is a mechanism provided by the GIT version control system that allows users to automatically execute custom scripts when specific events in the GIT workflow occur. GIT is an open source distributed version control system based on Github, which can effectively and quickly handle version management of projects of different sizes.
[0037] HDL is a hardware description language for integrated circuit design, which can be used to describe the hardware behavior, structure, and data flow of electronic systems. Through the design of HDL digital circuit systems, the design concept can be described layer by layer from top to bottom (from abstract to concrete), and a series of hierarchical modules can be used to represent extremely complex digital systems. Electronic design automation (EDA) tools can be used to perform simulation verification layer by layer, and then the module combination that needs to be transformed into an actual circuit is converted into a gate-level circuit netlist through automatic synthesis tools.
[0038] Based on the above embodiment, the code pre-check task includes a static code review task; based on the code pre-check task, a target test is performed to obtain a target test result, including: obtaining the code to be submitted in the temporary storage area; based on the static code review task, a first target interface is called to perform a static code check on the code to be submitted to obtain a static code check result; based on the target keyword in the preset quality keyword library, corresponding prompt information is obtained from the static code check result to obtain a static code review result.
[0039] Static code review tasks are tasks that perform static analysis on the code to be submitted or compiled code to be submitted without executing it, checking the code style, feasibility, etc., to determine potential errors in the code to be submitted. For example, static code review tasks may include syntax compilation, signal definition, multi-driver error checks, and style checks such as whether the code style is not allowed.
[0040] Exemplarily, calling the first target interface may be transmitting the code to be submitted to the target service and performing static code checking on the code to be submitted. The target service may be a third-party tool such as Lint, FindBugs, Cppcheck, or a built-in preset rule.
[0041] The static code checking result may also be referred to as a static code checking result report, including multiple prompt messages. The preset quality keyword library includes multiple keywords, and one keyword may correspond to one prompt message in the static code checking result.
[0042] The target keyword can be determined based on the static code review task. For example, whether each keyword in the preset quality keyword library is valid can be set based on the static code review task, and the valid keyword is set as the target keyword.
[0043] The static code review result is a summary of the prompt information corresponding to the target keyword in the static code inspection result. For example, the keyword can correspond to the keyword of the prompt information, so that the static code inspection result can be searched based on the target keyword, and the static code review result can be obtained by summarizing the search results.
[0044] It is understandable that the target keywords in the preset quality keyword library are different at different stages. In this embodiment, the first target interface is called at different stages to perform static code check on the code to be submitted to obtain the static code check result. However, at different stages, the corresponding prompt information is obtained from the static code check result through the corresponding target keywords in the preset quality keyword library to obtain different static code review results. In this way, there is no need to adjust the target service corresponding to the first target interface. Only the target keywords in the preset quality keyword library are configured to perform focused static code check on the code to be submitted, which is convenient for realizing flexible configuration of static code review.
[0045] Based on any of the above embodiments, the code pre-check task also includes a dynamic access review task; based on the code pre-check task, the target is tested and the target test result is obtained, which also includes: obtaining the code to be submitted in the temporary storage area; based on the dynamic access test task, calling the second target interface, loading the target test vector in the preset dynamic access test vector set, simulating the code to be submitted, and obtaining the dynamic access review result.
[0046] The dynamic access review task is to perform dynamic simulation tests on the code to be submitted to verify the functions of the code to be submitted. The dynamic access review task may include parameters such as the simulation mode, level, grade, quantity, and load vector type corresponding to the simulation of the code to be submitted.
[0047] The working principle and technical effect of calling the second target interface are basically the same as those of calling the first target interface, and will not be repeated here. When the target service when calling the second target interface is a third-party tool, those skilled in the art can select it according to actual conditions.
[0048] There are multiple test vectors in the dynamic access test vector set, and the target test vectors in the dynamic access test vector set may be different in different stages. For example, in the development iteration stage, basic smoke test vectors or flow test vectors can be loaded to verify the basic functions of the code to be submitted to ensure that the basic functions of the code to be submitted are correct. In the design delivery stage, the delivery access vector set can be loaded to comprehensively verify the functions of the code to be submitted to ensure that the functions of the code to be submitted are correct. The working principle and technical effect of determining the target test vector are basically the same as the working principle and technical effect of determining the target keyword, which will not be repeated here.
[0049] As mentioned above, the target test vectors are different in different stages. In this embodiment, the second target interface is called at different stages to obtain the code to be submitted and the target test vector to be loaded, and different target test vectors are loaded to simulate the code to be submitted to obtain the corresponding dynamic access review result. In this way, there is no need to adjust the target service corresponding to the second target interface. Only the target test vector in the preset dynamic access test vector set needs to be configured, so as to perform a focused dynamic access review on the code to be submitted, thereby facilitating the flexible configuration of the dynamic access review.
[0050] Based on any of the above embodiments, the code pre-check task also includes a physical implementation review task; based on the code pre-check task, the target is tested to obtain the target test result, and it also includes: obtaining the code to be submitted in the temporary storage area; based on the physical implementation review task, calling a third target interface, performing a physical implementation evaluation on the code to be submitted, and obtaining a physical implementation evaluation result; comparing the physical implementation evaluation result with the target indicator in the preset indicator library to obtain the physical implementation review result.
[0051] The physical implementation review task is a task to perform a physical level evaluation on the hardware implementation of the code to be submitted. For example, the physical implementation review task may include reviewing and evaluating the performance, power consumption, area, and low power consumption indicators of the code to be submitted. For example, the performance evaluation may be based on the highest frequency, and the low power consumption indicator may be based on the gated clock ratio.
[0052] The working principle and technical effect of calling the third target interface are basically the same as those of calling the first target interface, and will not be described in detail here. When the target service when calling the third target interface is a third-party tool, technicians in this field can select it according to actual conditions. The working principle and technical effect of determining the target indicator are basically the same as those of determining the target keyword, and will not be described in detail here.
[0053] The physical implementation evaluation result can also be called the physical implementation evaluation result report, which includes multiple physical parameters. The preset indicator library includes multiple indicators, and one indicator can correspond to one physical parameter. The physical implementation evaluation result is the physical parameter obtained by performing a physical implementation evaluation on the submitted code. For example, the physical implementation evaluation result may include performance, power consumption, area, and low power consumption indicators.
[0054] Exemplarily, the target indicators in the preset indicator library may correspond to the physical implementation evaluation results, so that the target indicators can be compared with performance, power consumption, area, and low power consumption indicators, etc., and the physical implementation review results can be obtained based on the comparison results.
[0055] It is understandable that the target indicators in the preset indicator library are different at different stages. In this embodiment, the third target interface is called at different stages to perform physical implementation evaluation on the code to be submitted, and the physical implementation evaluation results are obtained. In combination with different target indicators in the preset indicator library at different stages, the corresponding physical implementation review results are obtained. In this way, there is no need to adjust the target service corresponding to the third target interface. Only the target indicators in the preset indicator library are configured, and the physical implementation evaluation with emphasis on the code to be submitted can be performed, which is convenient for realizing the flexible configuration of physical implementation review.
[0056] Based on any of the above embodiments, the code pre-check task also includes a custom review task; based on the code pre-check task, the target is tested to obtain the target test result, and it also includes: obtaining the code to be submitted in the temporary storage area; based on the custom review task, the code to be submitted is reviewed for file compliance to obtain a custom review result.
[0057] Custom review tasks are tasks that users customize based on project-specific requirements and project specifications. Custom review tasks may be different at different stages. For example, during the development stage, the submitted code may be reviewed for code lines, file header comments, and other file specifications. During the development iteration stage, the submitted code may be reviewed for code lines, file header comments, file names, module names, repeated calls, and other file specifications.
[0058] It is understandable that the file standardization requirements for submitted code are different at different stages. For example, the file standardization requirements for submitted code at the development stage are looser than those for submitted code at the design delivery stage. If the same file standardization review is performed on the submitted code at the development stage and the design delivery stage, it will cause the development stage to spend more time on tasks that are not important at the current stage, reducing code development efficiency. In this embodiment, different numbers and types of file standardization reviews are performed on the submitted code at different stages, and a focused customized review can be performed on the submitted code, which facilitates the flexible configuration of customized reviews and improves code development efficiency.
[0059] Based on any of the above embodiments, if the target review result complies with the code access determination policy, code storage is executed, including: if the static code review result, the dynamic access review result, the physical implementation review result and the custom review result comply with the code access determination policy, code storage is executed.
[0060] It is understandable that if the review result of the code pre-check task determined by the code pre-check strategy of the target pre-check configuration table meets the code admission judgment strategy, the code storage is executed. The target pre-check configuration table corresponding to the code to be submitted at different stages is different. For example, the code pre-check task determined by the code pre-check strategy of the target pre-check configuration table corresponding to the development stage may include static code review tasks and custom review tasks. In this way, if the static code review task and the custom review task meet the code admission judgment strategy of the target pre-check configuration table, the code storage is executed.
[0061] In addition, the target pre-check configuration table may have different code pre-check strategies and corresponding code admission determination strategies, or may have different code pre-check strategies and different code admission determination strategies. Exemplarily, when the code pre-check task determined by the code pre-check strategy of the target pre-check configuration table is a physical implementation review task, in the design delivery stage, the physical implementation review result can be obtained by comparing the physical implementation evaluation result based on the PPA (Power, power consumption; Performance, performance; Area, area) indicator in the preset indicator library. In the design freeze stage, the physical implementation review result is also obtained by comparing the physical implementation evaluation result based on the PPA indicator in the preset indicator library.
[0062] The code admission decision strategy in the design delivery stage can be that the physical implementation evaluation results and the PPA indicator requirements in the preset indicator library can have a preset floating margin, wherein the specific value of the preset margin can be determined according to actual needs. The code admission decision strategy in the design freeze stage can be that the physical implementation evaluation results meet the PPA indicator requirements in the preset indicator library.
[0063] In this way, by adjusting the code access decision strategy in the target pre-inspection configuration table at different stages, the submitted code can be reviewed with focus, which facilitates the flexible configuration of target review.
[0064] In some currently used code management methods, if the user's code to be submitted does not comply with the code access judgment policy, it will be rejected in the pre-commit stage, resulting in the user's submission request not being recorded by GIT, and the code will be returned to the local computer, which is not convenient for further troubleshooting of quality issues. To solve the above technical problems, based on any of the above embodiments, the code to be submitted and the target pre-check configuration table are obtained based on the user's submission instruction, and before the code to be submitted is stored in a temporary storage area, the method also includes: turning on log recording to record the user's submission instruction history, as well as the pre-check process of the code to be submitted corresponding to the submission instruction and the target review result, and generating a pre-check log.
[0065] To facilitate users to understand and grasp the submission process of the code to be submitted, based on any of the above embodiments, the code to be submitted and the target pre-check configuration table are obtained based on the user's submission instruction, and after the code to be submitted is stored in a temporary storage area, the method also includes: returning a notification to the user that the code to be submitted has entered the pre-check.
[0066] To facilitate users to understand and grasp the admission judgment results of the code to be submitted, based on any of the above embodiments, the code to be submitted is subject to a target review based on the code pre-check task. After obtaining the target review result, the method further includes: if the target review result does not comply with the code admission judgment policy, a notification of rejection of code entry and the pre-check log are returned to the user; if the target review result complies with the code admission judgment policy, after executing the code entry, the method further includes: returning a notification of execution of the code entry for the code to be submitted and the pre-check log to the user.
[0067] In order to specifically illustrate the functions of the code storage management method provided by this application, the following Figure 2-Figure 3 Provide a specific example.
[0068] like Figure 2 As shown, the code repository management method provided by the present application is applied to a code repository management system, which integrates a flexible configuration management module, a submission monitoring and pre-inspection startup module, a code mapping and storage management module, a static code review module and a preset quality keyword library, a dynamic access review module and a preset dynamic access test vector set, a physical implementation review module and a preset indicator library, a custom review module, an access determination module, a log generation module and a push module.
[0069] Among them, the code repository management system can be implemented based on the Hooks of the GIT version management system, and a pre-commit script set can be created under git / hooks of the GIT version management system to implement the hook.
[0070] The submitted code may be an HDL code, and the stage information of the submitted code may include a development level of the HDL code, a development stage of the HDL code, and a cross-combination of the development level and the development stage of the HDL code.
[0071] There are differences in the quality requirements and emphasis of code review at different stages of code submission. For example, at the module-level development level, code review focuses on the coding style, realizability, functional correctness, simulation readiness, feasibility of simulation and synthesis, rough design size limit, etc. of a single module; as the RTL-level code design matures, the focus of code review evolves to performance, testability, and functional integrity that meets delivery requirements; at the subsystem or chip-level development level, the focus is on reviews related to integration issues between modules and IPs, such as signal bit width matching, input and output dangling, simulation of system-level functions, physical realizability after integration, and PPA balance.
[0072] Among them, RTL (Register-Transfer Level) is a level of HDL modeling. RTL does not focus on the details of registers and combinational logic, or how many logic gates are used, the connection topology between logic gates, etc. It describes the HDL level of the circuit by describing the logic function between registers. The RTL level is a higher level of abstraction than the gate level.
[0073] like Figure 3 As shown, the flexible configuration management module can be a TCL script program and parameter text. TCL (Tool Command Language) is a scripting language. TCL has simple syntax rules, compact code and is easy to maintain. Everything is a command. TCL includes syntax structures (such as for, if, etc.), is platform-independent, and can run on Win32, UNIX, Mac and other operating systems.
[0074] The flexible configuration management module may include multiple configuration management templates of different dimensions. For example, each configuration management template may include a review strategy and result determination strategy of a review module in one dimension. The flexible configuration management module may enable a target configuration management template or a combined target configuration management template in advance according to the stage information of the submitted code, and generate a pre-inspection configuration table with a corresponding pre-inspection task amount.
[0075] Different pre-check configuration tables can open and close corresponding review modules, and enable the same review module to perform different review tasks, thereby reviewing submitted codes at different stages with different quality requirements and different emphases.
[0076] Specifically, in the project development phase or the initial design phase, the HDL code has just been created and is still in the improvement stage. The target configuration management template can be enabled in the flexible configuration management module to open the static code review module and the custom review module for static code review and custom review.
[0077] Static code review can mainly perform basic error reviews such as basic syntax compilation, signal definition, and multiple drivers to obtain static code inspection results. The preset quality keyword library can open keywords for some key errors such as Error (error) of the corresponding compilation, TFIPC (port not connected) and IWNF (input signal not driven) in Warning (warning), CombLoop (combinatorial logic loop) and InferLatch (latch description) in the lint tag of the third-party static inspection tool. Custom review can mainly perform file standardization review such as the number of code lines and the comments in the file header.
[0078] During the development iteration phase, further functional improvement and design optimization are performed based on the initial version of the HDL code. The target configuration management template can be enabled in the flexible configuration management module to open the static code review module, dynamic access review module, physical implementation review module and custom review module to perform static code review, dynamic access review, physical implementation review and custom review.
[0079] Static code review can implement more stringent quality requirements than the initial design stage on the basis of performing basic error reviews such as basic syntax compilation, signal definition, and multiple drivers. The preset quality keyword library can further open keywords corresponding to rules such as if statement hierarchy, case statement integrity, expression bit width matching, simulation, comprehensive consistency style check, and clock reset correctness. Dynamic access review can load the preset dynamic access test vector set, basic smoke test vectors or flow test vectors to ensure the correctness of basic functions. Physical implementation review can set a looser indicator range to perform an initial assessment of the physical implementation of the HDL code. The preset indicator library can only open the parameter range related to area scale such as the number of instances for rough restrictions. Custom review can further perform file standardization reviews such as file name and module name compliance checks and repeated calls.
[0080] During the design delivery phase, after the HDL code is submitted to the version library, it will be delivered for verification and delivered to downstream departments such as the backend. The target configuration management template can be enabled in the flexible configuration management module to open the static code review module, dynamic access review module, physical implementation review module and custom review module to perform static code review, dynamic access review, physical implementation review and custom review.
[0081] Static code review will be strictly reviewed according to the delivery standards. The preset quality keyword library will open the tags corresponding to all lint Errors and key Warning keywords, such as the keyword corresponding to IWNF (Implicit Wire Has NoFanin). Dynamic access review loads the preset delivery access vector set to fully verify the basic functions of the HDL code. The specific vectors of the preset delivery access vector set can be set by the user according to actual needs, and no further explanation is given here. The physical implementation review can perform an initial evaluation according to the actual physical implementation strategy of the HDL code. The preset indicator library can open indicators with a small margin range of PPA fluctuations corresponding to the actual physical implementation strategy. Custom review can further perform more delivery-related file standardization reviews such as file integrity, storage location, call relationship, and comment ratio.
[0082] In the design freeze phase, the HDL code has been fully verified and preliminarily physically implemented. The code is updated only when there are functional or performance defects or physical implementation difficulties. The target configuration management template can be enabled in the flexible configuration management module to open the static code review module, dynamic access review module, physical implementation review module and custom review module to perform static code review, dynamic access review, physical implementation review and custom review.
[0083] Static code review will implement a stricter review based on the delivery standard. The preset quality keyword library will open tags corresponding to all lint Errors, key warnings, and keywords for coding styles that are not allowed to appear. Dynamic access review loads a relatively sufficient set of regression test vectors to ensure that the HDL code will not cause unnecessary defects in the original key functions. The specific vectors of the regression test vector set can be set by the user according to actual needs, and no further explanation is given here. The physical implementation review can be initially evaluated according to the real physical implementation strategy of the HDL code, and the PPA indicators corresponding to the real physical implementation strategy can be opened in the preset indicator library. In other words, the HDL code in the design freeze stage needs to be more constrained by the PPA indicators. Customized review can further perform more file integrity, storage location, call relationship, whether it is a frozen or locked file, and whether it is not allowed to be submitted. File normative review.
[0084] like Figure 3 As shown, the submission monitoring and pre-check startup module can be a TCL script program. The submission monitoring and pre-check startup module can set the opening and closing of the master control switch based on the master control switch parameters, and monitor the user's code submission actions in real time, and obtain the code to be submitted based on the user's submission instructions, store the code to be submitted in a temporary storage area in the specified code mapping and storage management module according to the code hierarchy mapping table, and maintain the queue of code to be submitted.
[0085] The code mapping and storage management module can be a program file written in TCL language, which maintains the tree-like file hierarchy table and storage directory of the HDL code, wherein the tree-like file hierarchy table is mapped and arranged according to the hierarchical calling relationship of the HDL design. When the submission monitoring and pre-check startup module indicates the need to store the HDL code to be submitted, the code mapping and storage management module can establish a corresponding directory according to the tree-like relationship and store the HDL code to be submitted.
[0086] For example, if the master control switch of the submission monitoring and pre-check startup module is set to off, the submission monitoring and pre-check startup module can directly submit the HDL code submitted by the user to the version library when it detects the input of the HDL code upload command such as "GIT commit" or "GIT push". If the master control switch of the submission monitoring and pre-check startup module is set to on, the submission monitoring and pre-check startup module will "intercept" the code submission command input by the HDL developer, store the code to be submitted in the designated temporary storage area, obtain the corresponding target pre-check configuration table in the flexible configuration management module according to the current stage information of the code to be submitted, determine the code pre-check task according to the code pre-check strategy of the target pre-check configuration table, and use the "bsub xx" command to submit the code pre-check task for review.
[0087] The log generation module can be a TCL script program or a program file written in TCL language. The submission monitoring and pre-check startup module can send a command to the log generation module when it detects the input of HDL code upload commands such as "GIT commit" or "GIT push", so that the log generation module can record the developer's submission command history, review process and review results according to time, and use the .log log text file for archiving to generate a pre-check log.
[0088] It is understandable that the code storage management method can be applied to a server, or to a system including a terminal and a server, and is implemented through interaction between the terminal and the server. When the code storage management method is applied to the server time, the log generation module records according to the server time.
[0089] The push module can be a TCL script program or a program file written in TCL language. The submission monitoring and pre-check startup module can send a command to the push module when detecting the input of HDL code upload commands such as "GIT commit" or "GIT push", so that the push module can use the post-print to push the prompt information that has entered the submission queue to the user. For example, the post-print can be used to push the prompt information that has entered the submission queue to the command terminal. After the pre-check is completed and a conclusion is drawn, the admission judgment module can send a command to the push module so that the push module calls the mail sending program to send the pre-check log to the developer via email, so that the user can understand and grasp the submission results.
[0090] The static code review module can be a script program written in Makefile. The submission monitoring and pre-check startup module can call and start the static code review module based on the pre-check configuration table. The static code review module can call third-party tools such as VCS and Spyglass based on the first target interface to perform static code review tasks. The preset quality keyword library can be a text file with a .tcl suffix.
[0091] The dynamic admission review module can be a script program written in Makefile, which can maintain a dynamic simulation test platform based on UVM. The submission monitoring and pre-check startup module can call and start the dynamic admission review module based on the pre-check configuration table. The dynamic admission review module can call the third-party simulation tool VCS based on the second target interface to perform the dynamic admission review task. The test vectors in the preset dynamic admission test vector set can be test files written in the system verilog language.
[0092] The physical implementation review module can be a script program written in Makefile. The submission monitoring and pre-check startup module can call and start the physical implementation review module based on the pre-check configuration table. The physical implementation review module can call a third-party synthesis tool based on the third target interface to perform the physical implementation review task. Exemplarily, it can be a quick pre-synthesis evaluation of the HDL code to be submitted to obtain a pre-synthesis report. From the pre-synthesis report, we can know the estimated values of its maximum frequency, power consumption, area, and gated clock ratio, etc.; in the PPA indicator library of this specific embodiment, the maximum frequency and maximum power consumption of the HDL module can be set 10% lower than the demand, and the maximum number of instances can be set to 110% of the demand.
[0093] The custom inspection module may be a script program written in TCL language, and the submission monitoring and pre-check startup module may call and start the custom inspection module based on the pre-check configuration table to perform custom review.
[0094] The admission determination module can be a program script written in TCL language. It can obtain corresponding prompt information from the static code inspection result based on the target keyword in the preset quality keyword library to obtain the static code review result; search for passed (PASS) or failed (FAILED) keywords in the dynamic admission review result; compare the physical implementation evaluation result with the target indicator in the preset indicator library to obtain the physical implementation review result and the custom review result, and comprehensively determine whether the target review result complies with the code admission determination policy. If the target review result does not comply with the code admission determination policy, a notification of rejection of code entry and the pre-check log are returned to the user. If the target review result complies with the code admission determination policy, code entry is executed, and a notification of the execution of code entry for the code to be submitted and the pre-check log are returned to the user.
[0095] It should be noted that the execution subject of the code storage management method provided in the embodiment of the present application can be a code storage management device, or a control module in the code storage management device for executing the code storage management method. In the embodiment of the present application, the execution of the code storage management method by the code storage management device is taken as an example to illustrate the code storage management device provided in the embodiment of the present application.
[0096] It should be noted that in the embodiments of the present application, the code storage management methods shown in the above-mentioned method drawings are all illustrative descriptions of one of the drawings in the embodiments of the present application. In specific implementation, the code storage management methods shown in the above-mentioned method drawings can also be implemented in combination with any other drawings that can be combined as shown in the above-mentioned embodiments, which will not be repeated here.
[0097] The code storage management device provided by the present application is described below. The code storage management device described below and the code storage management method described above can be referenced to each other.
[0098] Figure 4 It is a schematic diagram of the structure of the code storage management device provided by this application, such as Figure 4 As shown, the device includes a target pre-check configuration table acquisition module 210, a code pre-check task determination module 220, a target review result acquisition module 230 and a code storage execution module 240.
[0099] The target pre-check configuration table acquisition module 210 is used to obtain the code to be submitted based on the user's submission instruction, and obtain the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted. The preset configuration table library includes multiple pre-check configuration tables, and the pre-check configuration table corresponds to the stage information of the code to be submitted, and the target pre-check configuration table includes a code pre-check strategy and a code access determination strategy.
[0100] The code pre-check task determination module 220 is used to determine the code pre-check task according to the code pre-check strategy.
[0101] The target review result acquisition module 230 is used to perform a target review on the code to be submitted based on the code pre-check task and obtain a target review result.
[0102] The code storage execution module 240 is used to execute code storage if the target review result meets the code access determination policy.
[0103] Based on any of the above embodiments, the code pre-inspection task includes a static code review task; the target review result acquisition module 230 is specifically used to: obtain the code to be submitted in the temporary storage area; call the first target interface based on the static code review task, perform a static code check on the code to be submitted, and obtain a static code check result; based on the target keyword in the preset quality keyword library, obtain corresponding prompt information from the static code check result to obtain a static code review result.
[0104] Based on any of the above embodiments, the code pre-inspection task also includes a dynamic access review task; the target review result acquisition module 230 is specifically used to: obtain the code to be submitted in the temporary storage area; call the second target interface based on the dynamic access test task, load the target test vector in the preset dynamic access test vector set, simulate the code to be submitted, and obtain the dynamic access review result.
[0105] Based on any of the above embodiments, the code pre-inspection task also includes a physical implementation review task; the target review result acquisition module 230 is specifically used to: obtain the code to be submitted in the temporary storage area; call the third target interface based on the physical implementation review task, perform a physical implementation evaluation on the code to be submitted, and obtain a physical implementation evaluation result; compare the physical implementation evaluation result with the target indicator in the preset indicator library to obtain the physical implementation review result.
[0106] Based on any of the above embodiments, the code pre-inspection task also includes a custom review task; the target review result acquisition module 230 is specifically used to: obtain the code to be submitted in the temporary storage area; perform a file compliance review on the code to be submitted based on the custom review task to obtain a custom review result.
[0107] Based on any of the above embodiments, the code warehousing execution module is specifically used to: execute code warehousing if the static code review result, the dynamic access review result, the physical implementation review result and the custom review result comply with the code access determination policy.
[0108] Based on any of the above embodiments, the code repository management device also includes a log generation module, which is used to obtain the code to be submitted and the target pre-inspection configuration table based on the user's submission instruction, and before storing the code to be submitted in a temporary storage area, enable log recording to record the user's submission instruction history, as well as the pre-inspection process of the code to be submitted corresponding to the submission instruction and the target review result, and generate a pre-inspection log.
[0109] Based on any of the above embodiments, the code warehousing management device also includes a notification push module, which is used to obtain the code to be submitted and the target pre-inspection configuration table based on the user's submission instruction, and after storing the code to be submitted in a temporary storage area, return a notification to the user that the code to be submitted has entered the pre-inspection; based on the code pre-inspection task, the code to be submitted is subjected to a target review, and after obtaining the target review result, if the target review result does not comply with the code access determination policy, return a notification of rejection of code entry and the pre-inspection log to the user; if the target review result complies with the code access determination policy, after executing the code entry, return a notification that the code to be submitted has been executed for code entry and the pre-inspection log to the user.
[0110] Based on any of the above embodiments, a pre-inspection configuration table generation module is used to obtain the code to be submitted and the target pre-inspection configuration table based on the user's submission instruction, and before storing the code to be submitted in a temporary storage area, enable the target configuration management template to generate a pre-inspection configuration table corresponding to the pre-inspection task amount based on the stage information of the code to be submitted.
[0111] Figure 5 An example of a physical structure diagram of an electronic device is shown in FIG. Figure 5 As shown, the electronic device may include: a processor 310, a communication interface 320, a memory 330 and a communication bus 340, wherein the processor 310, the communication interface 320 and the memory 330 communicate with each other through the communication bus 340. The processor 310 may call the logic instructions in the memory 330 to execute the code storage management method, which includes: obtaining the code to be submitted based on the user's submission instruction, and obtaining the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, wherein the preset configuration table library includes multiple pre-check configuration tables, the pre-check configuration table corresponds to the stage information of the code to be submitted, and the target pre-check configuration table includes a code pre-check strategy and a code admission determination strategy; determining the code pre-check task according to the code pre-check strategy; performing a target review on the code to be submitted based on the code pre-check task to obtain the target review result; if the target review result meets the code admission determination strategy, executing code storage.
[0112] In addition, the logic instructions in the above-mentioned memory 330 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.
[0113] On the other hand, the present application also provides a computer program product, which includes a computer program, which can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the code warehousing management method provided by the above methods, the method including: obtaining the code to be submitted based on the user's submission instruction, and obtaining the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, the preset configuration table library includes multiple pre-check configuration tables, the pre-check configuration table corresponds to the stage information of the code to be submitted, and the target pre-check configuration table includes a code pre-check strategy and a code access determination strategy; determining the code pre-check task according to the code pre-check strategy; performing a target review on the code to be submitted based on the code pre-check task to obtain the target review result; if the target review result meets the code access determination strategy, executing code warehousing.
[0114] On the other hand, the present application also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to execute the code warehousing management method provided by the above-mentioned methods, the method comprising: obtaining the code to be submitted based on the user's submission instruction, and obtaining the corresponding target pre-check configuration table in a preset configuration table library according to the current stage information of the code to be submitted, the preset configuration table library including multiple pre-check configuration tables, the pre-check configuration table corresponding to the stage information of the code to be submitted, and the target pre-check configuration table including a code pre-check strategy and a code access determination strategy; determining a code pre-check task according to the code pre-check strategy; performing a target review on the code to be submitted based on the code pre-check task to obtain a target review result; if the target review result meets the code access determination strategy, executing code warehousing.
[0115] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.
[0116] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.
[0117] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims
1. A code storage management method, It is characterized in that include: Obtain the code to be submitted based on the user's submission instruction, and obtain the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, wherein the preset configuration table library includes multiple pre-check configuration tables, the pre-check configuration table corresponds to the stage information of the code to be submitted, and the target pre-check configuration table includes a code pre-check strategy and a code admission determination strategy; Determine the code pre-check task according to the code pre-check strategy; Performing a target review on the code to be submitted based on the code pre-check task, and obtaining a target review result; If the target review result meets the code access determination strategy, the code storage is executed.
2. The code storage management method according to claim 1, It is characterized in that The code pre-check task includes a static code review task; Performing a target test based on the code pre-check task and obtaining a target test result includes: Obtaining the code to be submitted in the temporary storage area; Calling the first target interface based on the static code review task, performing a static code check on the code to be submitted, and obtaining a static code check result; Based on the target keywords in the preset quality keyword library, corresponding prompt information is obtained from the static code inspection result to obtain the static code review result.
3. The code storage management method according to claim 2, It is characterized in that The code pre-check task also includes a dynamic access review task; Testing the target based on the code pre-check task and obtaining the target test result also includes: Obtaining the code to be submitted in the temporary storage area; Based on the dynamic access test task, the second target interface is called, the target test vector in the preset dynamic access test vector set is loaded, the code to be submitted is simulated, and the dynamic access review result is obtained.
4. The code storage management method according to claim 3, It is characterized in that The code pre-check task also includes a physical implementation review task; Testing the target based on the code pre-check task and obtaining the target test result also includes: Obtaining the code to be submitted in the temporary storage area; Based on the physical implementation review task, a third target interface is called to perform a physical implementation evaluation on the code to be submitted, and a physical implementation evaluation result is obtained; Compare the physical implementation evaluation results with the target indicators in the preset indicator library to obtain the physical implementation review results.
5. The code storage management method according to claim 4, It is characterized in that The code pre-check task also includes a custom review task; Testing the target based on the code pre-check task and obtaining the target test result also includes: Obtaining the code to be submitted in the temporary storage area; Based on the custom review task, the code to be submitted is reviewed for file compliance to obtain a custom review result.
6. The code storage management method according to any one of claim 5, It is characterized in that If the target review result meets the code access determination strategy, the code storage is executed, including: If the static code review result, the dynamic access review result, the physical implementation review result and the custom review result conform to the code access determination policy, code storage is executed.
7. The code storage management method according to claim 1, It is characterized in that The method further comprises: obtaining the code to be submitted and the target pre-check configuration table based on the user's submission instruction, and storing the code to be submitted in the temporary storage area before storing the code to be submitted in the temporary storage area: Enable logging to record the user's submission instruction history, as well as the pre-check process of the code to be submitted corresponding to the submission instruction and the target review result, and generate a pre-check log.
8. The code storage management method according to claim 7, It is characterized in that After acquiring the code to be submitted and the target pre-check configuration table based on the user's submission instruction and storing the code to be submitted in a temporary storage area, the method further includes: returning a notification to the user that the code to be submitted has entered the pre-check; After performing a target review on the code to be submitted based on the code pre-check task and obtaining a target review result, the method further includes: if the target review result does not meet the code admission determination policy, returning a notification of rejecting code entry and the pre-check log to the user; If the target review result meets the code access determination policy, after executing the code storage, the method further includes: returning a notification that the code to be submitted has been executed and the pre-check log to the user.
9. A code storage management device, It is characterized in that include: A target pre-check configuration table acquisition module is used to acquire the code to be submitted based on the user's submission instruction, and acquire the corresponding target pre-check configuration table in the preset configuration table library according to the current stage information of the code to be submitted, wherein the preset configuration table library includes multiple pre-check configuration tables, and the pre-check configuration table corresponds to the stage information of the code to be submitted, and the target pre-check configuration table includes a code pre-check strategy and a code admission determination strategy; A code pre-check task determination module, used to determine the code pre-check task according to the code pre-check strategy; A target review result acquisition module is used to perform a target review on the code to be submitted based on the code pre-check task and obtain a target review result; The code storage execution module is used to execute code storage if the target review result meets the code access determination policy.
10. An electronic device, It is characterized in that The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the code storage management method according to any one of claims 1 to 8 are implemented.