A Code issuing Tool

Abstract

The invention discloses a code issuing tool, comprising a code issuing module, a test module, a pre-issuing module and an audit module. Each module is respectively linked with a corresponding displayinterface and a corresponding script. Each module is used for executing a corresponding operation after receiving an instruction generated after a corresponding button is triggered. Each module can only publish the code after the completion of its own processing to the next module for processing, and each module performs code processing in the order of code release module-test module-pre-release module-audit module, and only the last-level audit module can publish the code that has passed the audit. In the invention, the worker only needs to trigger the corresponding button on the display interface, the code issuing tool can execute the corresponding issuing process, the service is simple, and each module can only issue the code completed by itself to the module at the next level, and thecode issuing process can not be issued by leaping level, so that the perfection and reliability of the code issuing process are improved.

Description

technical field [0001] The invention relates to the technical field of code release, in particular to a code release tool. Background technique [0002] The current code release process is: programmers manually upload code to the server - modify the test environment configuration for testing - pre-release the code in the simulation environment - review - release and other processes. However, each part of the current publishing process needs to be manually input by a staff member with a specific command statement before the corresponding operation can be performed. For example, when performing a test, a staff member is required to input a specified test statement, which may include content such as a directory of a test script or a test item. [0003] In such a publishing method, the staff need to learn and recite the instruction sentences of each process, and the business is complicated. Once the staff forgets the instructions, the release process may not be completed or th...

AI Technical Summary

Problems solved by technology

[0003] In such a release method, the staff need to learn and recite the instruction sentences of each process, and the business is complicated

Once the staff forgets the instructions, the release process may not be completed or the completion is not up to standard, and some problems may not be discovered. If these problems cause the customer's product to work abnormally, it will take a lot of company resources to troubleshoot. If the problem is serious, it will bring losses to the company, and the reliability is low

For example, in the process of code testing, there are many test items, that is, multiple tests are performed on the code, so it is easy for the staff to miss test items, resulting in incomplete testing

Moreover, if the release process is not perfect, the staff may need to rework again, which increases the time operation cost and reduces the efficiency of code release

[0004] Moreover, the current release method and process are not standardized enough, and the entire process is only based on the conscious execution of the staff, which leads to the fact that the developers who execute each part may exceed their authority to perform other parts of the work. For example, the staff who perform the pre-release may , do not send the pre-released code to the next level for review, but directly release it to the main site, which may cause problems in the final released code, which will bring losses to the company and low reliability

Images