Software product release process management system and method

Abstract

The invention aims to provide a software product release process management system and method. The system comprises a Web user side, an FIP resource manager, a CI code server and a Mock code verification server. The Web user side provides visual tracking and management of software resources, including information tracking and query of resource sources, versions and construction tasks, supports installation package generation and deployment, automatic release (strategy configuration, task scheduling and result verification) and release rollback mechanisms at the same time, and ensures the safety and controllability of the release process; the FIP resource manager stores and manages software resources which are continuously integrated and manually uploaded as a data source basis of the Web user side; the CI code server provides functions of version control, branch management, merging conflict resolution, automatic construction, dependency management and construction task scheduling of codes; the Mock code verification server supports test types of unit test, integration test and system test. The method is applied to the technical field of software management.

Description

Technical Field

[0001] The present invention is applied to the technical field of software management, and particularly relates to a software product release process management system and method. Background Art

[0002] Git refers to an open source distributed version control system. FTP (File Transfer Protocol) refers to the file transfer protocol, which is a protocol used to control the bidirectional transfer of files on the Internet. Jenkins refers to an open source, Java-based automation server that is mainly used to implement continuous integration (CI) and continuous delivery (CD). CI / CD is the abbreviation of continuous integration (Continuous Integration) and continuous delivery (Continuous Delivery) / continuous deployment (Continuous Deployment). Docker: Docker refers to an open source containerization platform that allows developers and operators to build, test, and deploy applications in different environments.

[0003] In the field of software development, as the scale and complexity of software projects continue to expand, how to efficiently manage the software development process, ensure software quality, and quickly respond to market demand have become important challenges facing software development teams. To this end, the industry has developed a series of tools and methods to optimize the software development and release process.

[0004] 1. Version control: Git is the most popular distributed version control system and is widely used in software development. It allows developers to modify and control code locally, while also supporting remote collaboration and code merging, greatly improving development efficiency and team collaboration capabilities.

[0005] 2. Continuous Integration and Continuous Deployment (CI / CD): Jenkins is a well-known CI / CD tool in the industry. It supports automated building, testing, and deployment, helping development teams to quickly provide feedback on the effects of code changes, reduce integration risks, and accelerate software delivery.

[0006] 3. Automated testing: Automated testing is an important means to ensure software quality. By writing test scripts and simulating user behavior, the software is comprehensively tested to discover and fix potential problems.

[0007] 4. Product tracking and management: A large number of build products are generated during the software development process. How to effectively track and manage these products and ensure that they are associated with the code base, version, build task and field release version is a problem to be solved.

[0008] In view of the above technical background, many companies have begun to try to integrate these tools into a unified platform to achieve automation and visualization of the software development process. However, these integration solutions often have the following problems: 1. Lack of tight integration and collaboration between tools leads to process fragmentation and data and information need to be manually transferred between different tools.

[0009] 2. Insufficient coverage of automated testing and lack of comprehensive testing strategies and methods.

[0010] 13. The product tracking and management functions are not perfect, making it difficult to ensure the accuracy and consistency of the products.

[0011] 14. The lack of unified release standards and processes leads to a chaotic release process that is difficult to reproduce.

[0012] Most of the existing technical implementation solutions are some existing software development and release management platforms, which attempt to integrate version control, continuous integration, automated testing, and product tracking functions into a unified platform. However, these platforms often have the following limitations: (1) Limited automated testing capabilities: Although these platforms support automated testing, they often lack comprehensive testing strategies and methods and cannot cover all testing scenarios and requirements.

[0013] (2) Imperfect product tracking and management functions: These platforms often have deficiencies in product tracking and management, making it difficult to ensure the correctness and consistency of products. For example, it may not be possible to effectively track information such as the source, version, and build task of the product.

[0014] (3) Lack of unified release standards and processes: These platforms usually lack unified release standards and processes, resulting in a chaotic release process that is difficult to reproduce. For example, different projects or teams may adopt different release methods and processes, resulting in inconsistent and unpredictable release results.

[0015] In summary, the prior art has the following disadvantages: 1. Insufficient tool integration: In the current software development and release process, multiple independent tools (such as version control, file transfer, continuous integration, etc.) are often used, but these tools lack tight integration, resulting in process fragmentation. Data and information need to be manually transferred between different tools, increasing the risk of errors and operational complexity.

[0016] 2. Inefficient verification and error correction: The existing software development process may have duplication of work or omissions in the verification and error correction stages, and lacks a unified, automated testing and verification mechanism, resulting in unstable software quality and extended release cycles.

[0017] 3. Difficulty in product tracking and management: The software build products (such as binary files, configuration files, etc.) lack effective tracking and management mechanisms during the development, testing and release process, making it difficult to ensure the correctness and consistency of the products, increasing the risk of release and upgrade failures.

[0018] 4. Insufficient standardization of the release process: There is a lack of a unified and standardized software release process. Different projects or teams may adopt different release methods, resulting in inconsistencies in the release process and problems that are difficult to reproduce.

[0019] Therefore, it is necessary to provide a software product release process management system and method to achieve software verification, error correction, product tracking and management, as well as standardized management of the release process. Summary of the invention

[0020] The technical problem to be solved by the present invention is to overcome the deficiencies of the prior art and provide a software product release process management system and method to achieve software verification, error correction, product tracking and management, and standardized management of the release process.

[0021] The technical solution adopted by the present invention is: the present invention comprises a Web client, a FIP resource manager, a CI code server, and a Mock code verification server; Users access the system through the Web client to conduct operational management of software development, testing, and release. The Web client provides visual tracking and management of software resources, including information tracking and query of resource sources, versions, and build tasks. It also supports generation of installation packages and deployment, automated release (policy configuration, task scheduling, result verification), and release rollback mechanism to ensure the security and controllability of the release process. The FIP resource manager stores and manages continuously integrated and manually uploaded software resources as the data source basis of the Web client; The CI code server provides code version control, branch management, merge conflict resolution, and automated build, dependency management, and build task scheduling functions; The Mock code verification server supports the test types of unit testing, integration testing, and system testing, provides test case management and test report generation functions, and has a Mock code verification function for simulating and verifying code behavior.

[0022] As can be seen from the above scheme, the purpose of this application is to propose a software product release process management system based on the company's current software management tools and development process management optimization, aiming to achieve the following goals: 1. Tool integration and automation: By integrating third-party software such as Git, FTP, Jenkins, and self-developed automatic software testing and release tracking managers, a unified and automated software development and release platform is formed to reduce manual operations and improve process efficiency and accuracy; 2. Efficient verification and error correction: Introduce automated software testing and verification mechanisms to ensure that the software is fully tested before release, reduce defects and errors after release, and improve software quality and user satisfaction; 3. Visual product tracking and management: Provides visual product tracking and management functions to ensure that software construction products are effectively tracked and managed during the development, testing and release process, and to ensure the correctness and consistency of products; 4. Standardized release process: Establish a unified and standardized software release process to ensure that different projects or teams follow the same release specifications and improve the predictability and controllability of the release process.

[0023] To summarize, this application integrates and optimizes the software development and release processes, improves software quality, release efficiency and user satisfaction, and reduces release risks and costs, to provide an efficient, intelligent, flexible and secure software product release process management system. The system is based on the company's current software management tools and development process management optimization, integrates third-party software such as Git, FTP, Jenkins, and independently develops components such as automatic software testing and release tracking managers to achieve software verification, error correction, product tracking and management, as well as standardized management of the release process.

[0024] A preferred solution is that the method includes implementation management, and the implementation management includes the following steps: Step A1: Start local branch coding and static code review. If passed, perform unit testing. Otherwise, return to local branch coding. Step A2: When the unit test passes, merge the local branch into the develop branch and perform static code review. If the unit test fails, perform error troubleshooting and return to the unit test. Step A3: When the static code review passes, compile the develop branch, otherwise return to the local branch coding. If the compilation succeeds, perform local automatic testing; if the compilation fails, perform error troubleshooting; Step A4: If the automatic test succeeds, merge the develop branch into the release branch and perform a static code review. If the automatic test fails, perform error troubleshooting. Step A5: When the static code review passes, compile the release branch, otherwise compile the front end of the develop branch; Step A6: After the release branch is compiled, perform an overall automatic test. If the compilation fails, perform error troubleshooting. Step A7: When the overall automatic test passes, merge the release branch into the master branch and compile the master branch. If the automatic test fails, perform error troubleshooting. Step A8: After the compilation is successful, manual testing and review are performed. If the compilation fails, error troubleshooting is performed. Step A9: If the manual test fails, perform error troubleshooting; if the manual test passes the review, wait for deployment to the production server and end the test.

[0025] A preferred solution is that the method further includes project research and development, which includes four stages: development, project construction, platform release and operation, and on-site maintenance. The development includes the following steps: Step B1: Demand Analysis, Step B2: Resource development, Step B3: Functional test, Step B4: JenKins builds. JenKins refers to the industry-renowned CI / CD tool that supports automated building, testing, and deployment, helping development teams quickly feedback on the effects of code changes, reducing integration risks, and accelerating software delivery. Step B5: Resources uploaded by the Web authentication user; Step B1 in the development phase includes the following sub-steps: Step B1-1: Collect user needs. Step B1-2: Demand Analysis, Step B1-3: Output requirement document; Step B2 in the development phase includes the following sub-steps: Step B2-1, resource development, Step B2-2: Self-test by R&D personnel. Step B2-3: Find the bug and fix it; Step B3 in the development phase includes the following sub-steps: Step B3-1, write test cases, Step B3-2, manual testing, Step B3-3, regression testing, Step B3-4: Write a functional test report, Step B3-5: If the defect rate meets the standard, determine the use case that can be automated. Step B3-6: Write the test script and upload it to GIT. GIT refers to an open source distributed version control system. Step B4 in the development phase includes the following sub-steps: Step B4-1, Jenkins build, Step B4-2, perform automatic testing, Step B4-3: If the test is successful, the resource is uploaded to the Web server resource pool, where the Web server refers to the Web client; Step B5 in the development phase includes the following sub-steps: Step B5-1, fill in the launcher config parameters (optional). Launcher config refers to the launcher configuration. Step B5-2: Authenticate the resources uploaded by the user to the resource pool.

[0026] A preferred solution is that the project construction includes the following steps: Step C1, IDE editing UI, Step C2, Web server; Step C1 includes the following subdivision steps in the construction phase: Step C1-1, import the downloaded solution and project configuration files, Step C1-2, edit UI, Step C1-3, Generate UI Config, Step C1-4: Upload UI Config and package it offline into a deployable file. Step C1-5: If the resources in UI Config are consistent with ResourceList (the resources in UI configuration are consistent with those in the resource list), the newly added resources are added to the resource pool by calling the webserver API; Step C2 includes the following subdivision steps in the construction phase: Step C2-1, create a new plan or import the configuration file of an existing plan, Step C2-2: If it is a new solution, you need to add an environment. If you import the configuration file of an existing solution, you need to check whether the solution exists. If it does, check whether the original solution is consistent with the imported solution. If they are consistent, the original solution will be displayed. If they are inconsistent or the checked solution does not exist, you need to check whether the resources exist in the resource pool. Step C2-3: Form a plan, Step C2-4, download the solution and import it into IDE. IDE refers to IntelliJ IDEA, a widely used integrated development environment (IDE) developed by JetBrains, designed to improve developer productivity and code quality. Step C2-5, download the solution to generate ResourceList (resource list), various resources, launcher config (launcher configuration) and package, Step C2-6: Form the final deployment file.

[0027] A preferred solution is that the platform release operation includes the following steps: Step D1, execute the installation program, Step D2, start ProcessManger (process management); Step D3: Load modules in order according to the launcher config. Step D4: Load UI plug-ins according to the UI Config sequence.

[0028] A preferred solution is that the on-site maintenance includes the following steps: If the requirements are not met and there is no network, make local modifications and manually modify the Project file; if there is a network and there is no need to update resources but the resource parameter values ​​need to be updated, upgrade the corresponding plan to form a new version of the plan; if resources need to be updated, re-develop the resources.

[0029] A preferred solution is that the method further includes resource management, and the resource management includes the following steps: Step E1: Standardized process development, Step E2: Data management, Step E3: Solution / resource / environment / deployment template management, Step E4: Add / Update / View / Delete / Download / Authorize / Trigger Build. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 is a system architecture diagram of the present invention; Figure 2 is a flow chart of platform deployment for said implementation management; Figure 3 is a standardized flow chart for the first part of the research and development of the project; Figure 4 It is a standardized flow chart for the second part of the research and development of the said project; Figure 5 It is a standardized flow chart for the third part of the research and development of the project; Figure 6 It is a standardized flow chart for the fourth part of the project development; Figure 7 is a flow chart of the resource management. DETAILED DESCRIPTION

[0031] like Figure 1 As shown, in this embodiment, the present invention includes a Web client, a FIP resource manager, a CI code server, and a Mock code verification server; Users access the system through the Web client to conduct operational management of software development, testing, and release. The Web client provides visual tracking and management of software resources, including information tracking and query of resource sources, versions, and build tasks. It also supports generation of installation packages and deployment, automated release (policy configuration, task scheduling, result verification), and release rollback mechanism to ensure the security and controllability of the release process. The FIP resource manager stores and manages continuously integrated and manually uploaded software resources as the data source basis of the Web client; The CI code server provides code version control, branch management, merge conflict resolution, and automated build, dependency management, and build task scheduling functions; The Mock code verification server supports the test types of unit testing, integration testing, and system testing, provides test case management and test report generation functions, and has a Mock code verification function for simulating and verifying code behavior.

[0032] The nature of the Web client: software resource management operating system; function: providing visual tracking and management of software resources, including tracking and querying of information such as resource sources, versions, and build tasks; additional functions: supporting generation of installation packages and deployment, automated publishing (including policy configuration, task scheduling, and result verification), and a release rollback mechanism to ensure the security and controllability of the release process.

[0033] The nature of the FIP resource manager: a system for storing and managing software resources; function: storing and managing CI (continuous integration) and manually uploaded software resources, serving as the data source basis for the Web user end.

[0034] The nature of the CI code server: code management and build system based on Git and Jenkins; Function: Provides code version control, branch management, merge conflict resolution, as well as automated build, dependency management, and build task scheduling.

[0035] The nature of the Mock code verification server (test management): an independently developed automatic software testing tool; functions: supports multiple test types such as unit testing, integration testing, system testing, provides test case management, test report generation and other functions, and may also include Mock code verification functions (used to simulate and verify code behavior).

[0036] The above components together constitute a complete software development and deployment process, covering multiple stages of the software life cycle from code management, building, testing to release and rollback. The collaboration and integration between them ensure the efficiency, quality and security of software development.

[0037] like Figure 2 As shown, in this embodiment, the method includes implementation management, and the implementation management includes the following steps: Step A1: Start local branch coding and static code review. If passed, perform unit testing. Otherwise, return to local branch coding. Step A2: When the unit test passes, merge the local branch into the develop branch and perform static code review. If the unit test fails, perform error troubleshooting and return to the unit test. Step A3: When the static code review passes, compile the develop branch, otherwise return to the local branch coding. If the compilation succeeds, perform local automatic testing; if the compilation fails, perform error troubleshooting; Step A4: If the automatic test succeeds, merge the develop branch into the release branch and perform a static code review. If the automatic test fails, perform error troubleshooting. Step A5: When the static code review passes, compile the release branch, otherwise compile the front end of the develop branch; Step A6: After the release branch is compiled, perform an overall automatic test. If the compilation fails, perform error troubleshooting. Step A7: When the overall automatic test passes, merge the release branch into the master branch and compile the master branch. If the automatic test fails, perform error troubleshooting. Step A8: After the compilation is successful, manual testing and review are performed. If the compilation fails, error troubleshooting is performed. Step A9: If the manual test fails, perform error troubleshooting; if the manual test passes the review, wait for deployment to the production server and end the test.

[0038] Among them, the implementation management includes platform automated deployment, which uses automated tools to achieve rapid and accurate deployment of the software platform and reduce errors caused by manual operations; and provides an access interface for Web users to facilitate users to perform software management operations through the Web interface.

[0039] like Figures 3 to 6 As shown, in this embodiment, the method also includes project development, which includes four stages: development, project construction, platform release and operation, and on-site maintenance. The development includes the following steps: Step B1: Demand Analysis, Step B2: Resource development, Step B3: Functional test, Step B4, JenKins build, Step B5: Resources uploaded by the Web authentication user; Step B1 in the development phase includes the following sub-steps: Step B1-1: Collect user needs. Step B1-2: Demand Analysis, Step B1-3: Output requirement document; Step B2 in the development phase includes the following sub-steps: Step B2-1, resource development, Step B2-2: Self-test by R&D personnel. Step B2-3: Find the bug and fix it; Step B3 in the development phase includes the following sub-steps: Step B3-1, write test cases, Step B3-2, manual testing, Step B3-3, regression testing, Step B3-4: Write a functional test report, Step B3-5: If the defect rate meets the standard, determine the use case that can be automated. Step B3-6: Write test script and upload to GIT; Step B4 in the development phase includes the following sub-steps: Step B4-1, Jenkins build, Step B4-2, perform automatic testing, Step B4-3: If the test is successful, upload the resource to the Web server resource pool; Step B5 in the development phase includes the following sub-steps: Step B5-1, fill in the launcher config parameters (optional), Step B5-2: Authenticate the resources uploaded by the user to the resource pool.

[0040] like Figures 3 to 6 As shown, in this embodiment, the project construction includes the following steps: Step C1, IDE editing UI, Step C2, Web server; Step C1 includes the following subdivision steps in the construction phase: Step C1-1, import the downloaded solution and project configuration files, Step C1-2, edit UI, Step C1-3, Generate UI Config, Step C1-4: Upload UI Config and package it offline into a deployable file. Step C1-5: If the resources in the UI Config are consistent with the ResourceList, the newly added resources are added to the resource pool by calling the API of the web server; Step C2 includes the following subdivision steps in the construction phase: Step C2-1, create a new plan or import the configuration file of an existing plan, Step C2-2: If it is a new solution, you need to add an environment. If you import the configuration file of an existing solution, you need to check whether the solution exists. If it does, check whether the original solution is consistent with the imported solution. If they are consistent, the original solution will be displayed. If they are inconsistent or the checked solution does not exist, you need to check whether the resources exist in the resource pool. Step C2-3: Form a plan, Step C2-4, download the solution and import it into IDE. Step C2-5, download the solution to generate ResourceList, various resources, launcher config and package them. Step C2-6: Form the final deployment file.

[0041] The development is a standardized process, which ensures the consistency and controllability of software quality by formulating and following a standardized software development process. The standardized process includes demand management, development management, test management, and release management.

[0042] 1. Demand Management: lRequirement collection and organization: Use requirement analysis tools to collect and organize user requirements and form requirement documents.

[0043] lRequirement review: Organize relevant personnel to review the requirement documents to ensure the rationality and feasibility of the requirements.

[0044] 2. Development Management: l Development task allocation: Assign development tasks to corresponding developers based on the requirements document.

[0045] lCode development and submission: Developers develop code according to the agreed coding standards and submit the code to the code repository (such as Git).

[0046] 3. Test management: lTest case writing: Testers write test cases based on the requirement documents.

[0047] lAutomated testing: Use automated testing tools to test the software to ensure software quality.

[0048] 4. Release Management: lPreparation before release: Before release, perform necessary configuration and preparation, such as environment configuration and dependency installation.

[0049] l Release operation: Use release management tools (such as Jenkins) to release software and ensure the accuracy and stability of the release.

[0050] The flowchart of the standardization process is shown in the figure: like Figures 3 to 6 As shown, in this embodiment, the platform publishing operation includes the following steps: Step D1, execute the installation program, Step D2, start ProcessManager; Step D3: Load modules in order according to the launcher config. Step D4: Load UI plug-ins in order according to UI Config.

[0051] like Figure 1 to Figure 2 As shown, in this embodiment, the on-site maintenance includes the following steps: If the requirements are not met and there is no network, make local modifications and manually modify the Project file; if there is a network and there is no need to update resources but the resource parameter values ​​need to be updated, upgrade the corresponding plan to form a new version of the plan; if resources need to be updated, re-develop the resources.

[0052] like Figure 7 As shown, in this embodiment, the method further includes resource management, and the resource management includes the following steps: Step E1: Standardized process development, Step E2: Data management, Step E3: Solution / resource / environment / deployment template management, Step E4: Add / Update / View / Delete / Download / Authorize / Trigger Build.

[0053] The resource management is the management of solutions / resources / environments / deployment templates. Through the data management module, solutions, resources, environments, and deployment templates are uniformly managed and maintained, providing operations such as adding, updating, viewing, deleting, downloading, and authenticating. The resource management includes resource statistics and resource downloading and sharing.

[0054] Resource statistics: Statistics and analysis of software resources (such as code, configuration, documents, etc.) to understand the distribution and utilization of resources.

[0055] Resource downloading and sharing: Provide resource downloading interface and sharing mechanism to facilitate users to obtain and use the required resources.

[0056] In this embodiment, the system also has the following technical effects: 1. Overall architecture of the technical solution: The overall architecture is innovative, which realizes the integrated management and automated process of the entire life cycle of software development, testing, and release. This architecture is highly scalable and flexible and can adapt to software development teams of different sizes and needs.

[0057] 2. Core algorithm of automatic software testing tool: The self-developed automatic software testing tool is an important part of the present invention. Its core algorithm can intelligently analyze test cases, execute test tasks, and generate detailed test reports. This algorithm has a high degree of accuracy and reliability, and is the key to ensuring software quality.

[0058] 3. Visual tracking and product management implementation method: The present invention provides a visual tracking function for building products, and its implementation method includes steps such as data storage, information retrieval and display. This method can clearly display the relevant information of the built product and provide comprehensive tracking and management support for managers.

[0059] 4. Specific implementation of release strategy and rollback mechanism: The release strategy and rollback mechanism of the present invention are innovative. They can customize the release process according to actual needs and quickly restore to the previous state when problems occur during release. This mechanism ensures the security and controllability of the release process and is one of the important protection points of the present invention.

[0060] 5. This system is the "Ant Home" software product release process management system, which shows many significant advantages. First of all, this system realizes the comprehensive integration and optimization of the software release process. Traditional management methods often rely on scattered tools and manual operations, which are not only inefficient but also prone to errors. The "Ant Home" system is based on third-party software such as Git, FTP, Jenkins, and combined with self-developed automatic software testing and release tracking managers to form a complete and unified management platform. This enables each link in the software release process to be effectively monitored and managed, greatly improving efficiency and accuracy.

[0061] Secondly, the system also has significant advantages in data management and display. Through an intuitive and easy-to-use interface, users can easily view and manage various data such as solutions, resources, environments, deployment templates, etc. At the same time, the system also provides rich statistics and query functions to help users better understand the various states and trends in the software release process. This visual management method not only improves the user's operating experience, but also provides strong support for software quality control and continuous improvement.

[0062] Although the embodiments of the present invention are described with practical solutions, they do not constitute limitations on the meaning of the present invention. For those skilled in the art, it is obvious to modify the implementation scheme and combine it with other solutions based on this description.

Claims

1. A software product release process management system, characterized by: It includes Web client, FIP resource manager, CI code server, and Mock code verification server; Users access the system through the Web client to conduct operational management of software development, testing, and release. The Web client provides visual tracking and management of software resources, including information tracking and query of resource sources, versions, and build tasks. It also supports generation of installation packages and deployment, automated release (policy configuration, task scheduling, result verification), and release rollback mechanism to ensure the security and controllability of the release process. The FIP resource manager stores and manages continuously integrated and manually uploaded software resources as the data source basis of the Web client; The CI code server provides code version control, branch management, merge conflict resolution, and automated build, dependency management, and build task scheduling functions; The Mock code verification server supports the test types of unit testing, integration testing, and system testing, provides test case management and test report generation functions, and has a Mock code verification function for simulating and verifying code behavior.

2. A method for managing the software product release process management system as claimed in claim 1, characterized in that: The method includes implementing management, and the implementing management includes the following steps: Step A1: Start local branch coding and static code review. If passed, perform unit testing. Otherwise, return to local branch coding. Step A2: When the unit test passes, merge the local branch into the develop branch and perform static code review. If the unit test fails, perform error troubleshooting and return to the unit test. Step A3: When the static code review passes, compile the develop branch, otherwise return to the local branch coding. If the compilation succeeds, perform local automatic testing; if the compilation fails, perform error troubleshooting; Step A4: If the automatic test succeeds, merge the develop branch into the release branch and perform a static code review. If the automatic test fails, perform error troubleshooting. Step A5: When the static code review passes, compile the release branch, otherwise compile the front end of the develop branch; Step A6: After the release branch is compiled, perform an overall automatic test. If the compilation fails, perform error troubleshooting. Step A7: When the overall automatic test passes, merge the release branch into the master branch and compile the master branch. If the automatic test fails, perform error troubleshooting. Step A8: After the compilation is successful, manual testing and review are performed. If the compilation fails, error troubleshooting is performed. Step A9: If the manual test fails, perform error troubleshooting; if the manual test passes the review, wait for deployment to the production server and end the test.

3. A method according to claim 2, characterized in that: The method also includes project development, which includes four stages: development, project construction, platform release and operation, and on-site maintenance. The development includes the following steps: Step B1: Demand Analysis, Step B2: Resource development, Step B3: Functional test, Step B4, JenKins build, Step B5: Resources uploaded by the Web authentication user; Step B1 in the development phase includes the following sub-steps: Step B1-1: Collect user needs. Step B1-2: Demand Analysis, Step B1-3: Output requirement document; Step B2 in the development phase includes the following sub-steps: Step B2-1, resource development, Step B2-2: Self-test by R&D personnel. Step B2-3: Find the bug and fix it; Step B3 in the development phase includes the following sub-steps: Step B3-1, write test cases, Step B3-2, manual testing, Step B3-3, regression testing, Step B3-4: Write a functional test report, Step B3-5: If the defect rate meets the standard, determine the use case that can be automated. Step B3-6: Write test script and upload to GIT; Step B4 in the development phase includes the following sub-steps: Step B4-1, Jenkins build, Step B4-2, perform automatic testing, Step B4-3: If the test is successful, upload the resource to the Web server resource pool; Step B5 in the development phase includes the following sub-steps: Step B5-1, fill in the launcher config parameters (optional), Step B5-2: Authenticate the resources uploaded by the user to the resource pool.

4. A method according to claim 2, characterized in that: The project construction includes the following steps: Step C1, IDE editing UI, Step C2, Web server; Step C1 includes the following subdivision steps in the construction phase: Step C1-1, import the downloaded solution and project configuration files, Step C1-2, edit UI, Step C1-3, Generate UI Config, Step C1-4: Upload UI Config and package it offline into a deployable file. Step C1-5: If the resources in UI Config are consistent with ResourceList, the newly added resources are added to the resource pool by calling the webserver API; Step C2 includes the following subdivision steps in the construction phase: Step C2-1, create a new plan or import the configuration file of an existing plan, Step C2-2: If it is a new solution, you need to add an environment. If you import the configuration file of an existing solution, you need to check whether the solution exists. If it does, check whether the original solution is consistent with the imported solution. If they are consistent, the original solution will be displayed. If they are inconsistent or the checked solution does not exist, you need to check whether the resources exist in the resource pool. Step C2-3: Form a plan, Step C2-4, download the solution and import it into IDE. Step C2-5, download the solution to generate ResourceList, various resources, launcher config and package them. Step C2-6: Form the final deployment file.

5. A method according to claim 3, characterized in that: The platform release operation includes the following steps: Step D1, execute the installation program, Step D2, start ProcessManager; Step D3: Load modules in order according to the launcher config. Step D4: Load UI plug-ins in order according to UI Config.

6. A method according to claim 3, characterized in that: The on-site maintenance includes the following steps: If the requirements are not met and there is no network, make local modifications and manually modify the Project file; if there is a network and there is no need to update resources but the resource parameter values ​​need to be updated, upgrade the corresponding plan to form a new version of the plan; if resources need to be updated, re-develop the resources.

7. A method according to claim 2, characterized in that: The method also includes resource management, which includes the following steps: Step E1: Standardized process development, Step E2: Data management, Step E3: Solution / resource / environment / deployment template management, Step E4: Add / Update / View / Delete / Download / Authorize / Trigger Build.

Images