Process management method, system and equipment based on DevOps

Abstract

The invention relates to the field of software information, and discloses a DevOps-based process management method, system and equipment. The method comprises the following steps: disassembling a research and development process of a software project to obtain each step in the research and development process, and packaging each step into an independently deployed task node; a to-be-processed software project is obtained, a research and development process and a stage process corresponding to the software project are determined according to the identification information, and the software project carries unique identification information; based on the research and development process and the stage process, screening the task nodes corresponding to the stage process, and constructing the screened task nodes into an assembly line; the assembly line is executed, and the research and development process is completed. According to the method, the software delivery quality is automatically monitored, the workload of research and development testers in the aspect of quality analysis is reduced, a flexible process establishment mechanism is introduced, different research and development processes are flexibly established according to management specifications of different projects, and the fine degree and flexibility of research and development process management are improved.

Description

Technical Field

[0001] The present application relates to the field of software information, and in particular to a DevOps-based process management method, system and device. Background Art

[0002] In the modern software industry, DevOps systems are often used to build, test, and release software faster, more frequently, and more reliably through automated CI / CD pipelines. Traditional DevOps systems are unable to control CI / CD pipelines, resulting in developers or operations personnel not following process specifications, for example, releasing untested changes to the official environment, or delivering software with security vulnerabilities, causing huge system risks.

[0003] However, existing enterprises or organizations usually formulate a series of system launch systems to artificially constrain this problem. For example, they require that the system must pass a round of "online review" before it can be launched, and often require "functional test reports", "UI walkthrough reports", "security test reports", etc. before it can be launched. Using the above methods not only has high management costs, but can only reduce the probability of problems as much as possible, but cannot fundamentally solve the problem. In addition, it can usually only control the final link of system launch, and it is difficult to achieve fine control over the entire software development process.

[0004] Therefore, there is an urgent need for a management solution that can refine and dynamic the software development process and improve delivery quality. Summary of the invention

[0005] In view of the shortcomings of the prior art mentioned above, the present application discloses a process management method, system and device based on DevOps, which are used to solve the problem of being unable to determine the delivery quality of software in a refined and dynamic manner during the software development process.

[0006] The first aspect of the present application discloses a process management method based on DevOps, comprising: disassembling the R&D process of the software project, obtaining each step in the R&D process, and encapsulating each step into an independently deployed task node; obtaining a software project to be processed, determining the R&D process and phase process corresponding to the software project according to the identification information, wherein the software project carries unique identification information, and the phase process includes at least two of the development phase, the testing phase, the deployment phase, the production phase, the acceptance phase, and the online phase; based on the R&D process and the phase process, screening the task nodes corresponding to the phase process, and constructing the screened task nodes into a pipeline;

[0007] Execute the pipeline to complete the R&D process.

[0008] In certain embodiments of the first aspect of the present application, the task nodes corresponding to each of the multiple stage processes are screened based on the R&D process and combined to construct a complete pipeline of the current software project, including: according to the business logic corresponding to the R&D process of the current software project, at least one pipeline is constructed for each of the stage processes in the development stage, the testing stage, the acceptance stage and the online stage, and multiple pipelines are combined to form a complete pipeline.

[0009] In certain embodiments of the first aspect of the present application, each step is encapsulated as an independently deployed task node, including: dividing the task node into an inherent node for building an image or deploying a service and a gate control node for verifying code quality; the inherent node and the gate control node both include execution parameters, execution results, whether blocked, task number, previous node and next node; determining the CI / CD pipelines corresponding to the development stage, the test stage, the deployment stage, the production stage, the acceptance stage and the online stage according to the R&D process; monitoring the configuration requirements in each of the CI / CD pipelines, and if it is detected that the configuration requirements include building an image or deploying a service, configuring the inherent node in the CI / CD pipeline; if it is detected that the configuration requirements include software component analysis or code security scanning, configuring the gate control node in the CI / CD pipeline; verifying the current task node in the CI / CD pipeline through the gate control node; if the current verification passes, executing the next task node in the process; if the current verification fails, terminating the execution and feeding back a diagnostic report of the verification failure.

[0010] In certain embodiments of the first aspect of the present application, each step is encapsulated as an independently deployed task node, and also includes: when configuring the task nodes in each of the CI / CD pipelines, the execution order of each of the task nodes in the CI / CD pipeline is determined according to the series connection of the previous node and the next node of each task node; in response to the execution order, the corresponding task node is started according to the task number; the task node is controlled to run according to the configured execution parameters, and the execution result of the current task node is determined; if the execution result meets the preset conditions, the next node is started to be executed; if the execution result does not meet the preset conditions, the current task node is terminated.

[0011] In certain embodiments of the first aspect of the present application, if it is monitored that the configuration requirements include software component analysis or code security scanning, it also includes: using the Spring Boot framework to independently encapsulate at least one quality scanning tool to generate at least one microservice, the quality scanning tool including code quality analysis, code security vulnerability analysis and automated testing; providing a first API interface for performing a scan and a second API interface for obtaining a scan report; configuring the access control node to call at least one of the at least one microservice by accessing the first API interface or the second API interface.

[0012] In certain embodiments of the first aspect of the present application, the R&D process of the software project is disassembled, and before each step in the R&D process is obtained, it also includes: deploying the first permission and the second permission respectively according to the different roles of the project manager and the developer; calling the first permission to create a corresponding R&D process based on the received software project as a delivery project or a non-delivery project; calling the second permission to configure the software name corresponding to the software project through the R&D process; after determining the software name, selecting the pre-configured R&D process to determine the pipeline template corresponding to each stage process, configuring each pipeline template, and supplementing the node information of each stage process by adding the task node. After the configuration is completed, it is executed according to the established R&D process.

[0013] In certain embodiments of the first aspect of the present application, verifying the current task node in the CI / CD pipeline also includes: obtaining a download task corresponding to the current software project, the download task is generated based on the test performance of the current task node in the CI / CD pipeline, and the test performance includes software analysis or security scanning; downloading the target application package required for the test performance of the software project from the server in response to the download task; receiving the target application package, and when the target application package is installed, verifying the software project to obtain a verification record.

[0014] In certain embodiments of the first aspect of the present application, the verification of the software project to obtain a verification record includes: in response to a verification start operation, displaying a verification auxiliary pop-up window, the verification auxiliary pop-up window including a task selection control; in response to a verification task selection request triggered based on the task selection control, sending the verification task selection request to a server so that the server obtains a pending verification task; receiving the pending verification task sent by the server, and in response to a trigger operation based on any verification task among the pending verification tasks, executing any verification task, and obtaining the verification record based on the verification result corresponding to any verification task.

[0015] The second aspect of the present application discloses a DevOps-based process management system, including: a node definition module, used to disassemble the R&D process of the software project, obtain each step in the R&D process, and encapsulate each step into an independently deployed task node; a process determination module, used to obtain the software project to be processed, and determine the corresponding R&D process and stage process of the software project according to the identification information, the software project carries unique identification information, and the stage process includes at least two of the development stage, testing stage, deployment stage, production stage, acceptance stage and online stage; a pipeline construction module, based on the R&D process and the stage process, screens the task nodes corresponding to the stage process, and constructs the screened task nodes into a pipeline; a process management module, used to execute the pipeline to complete the R&D process.

[0016] The third aspect of the present application discloses an electronic device, comprising: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the above method.

[0017] Beneficial effects of the present application: The present application disassembles the R&D process of the software project, obtains each step in the R&D process, and encapsulates each step into an independently deployed task node, which is conducive to the process of R&D; the corresponding R&D process of the software project is determined according to the identification information. On the one hand, the R&D process management is introduced into the CI / CD process of the DevOps system, which restricts developers from arbitrarily releasing software without following the specifications, thereby improving software reliability; based on the R&D process, the task nodes corresponding to each of the multiple stage processes are screened and combined to build a complete pipeline for the software project; on the other hand, a flexible process construction mechanism is introduced, and different R&D processes can be flexibly constructed according to the management specifications of different projects, thereby improving the refinement and flexibility of R&D process management; through the refined management and automated control of the R&D process of the software project, it is ensured that the software project can meet the established quality standards at each stage, which is conducive to timely discovery and problem solving, and avoiding the expansion of problems in subsequent stages. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is an application environment diagram for implementing a DevOps-based process management method in an embodiment of the present application;

[0019] Figure 2 It is a flow chart of a process management method based on DevOps in an embodiment of the present application;

[0020] Figure 3 It is a logical flow chart of a process management method based on DevOps in an embodiment of the present application;

[0021] Figure 4 It is a DevOps system architecture diagram in a DevOps-based process management method in an embodiment of the present application;

[0022] Figure 5 It is a flowchart of the testing phase in a DevOps-based process management method in an embodiment of the present application;

[0023] Figure 6 This is a diagram of an application creation configuration interface in a DevOps-based process management method in an embodiment of the present application;

[0024] Figure 7 This is a diagram of a node configuration interface in a DevOps-based process management method in an embodiment of the present application;

[0025] Figure 8 This is a configuration interface diagram of the R&D stage in a DevOps-based process management method in an embodiment of the present application;

[0026] Fig. 9 This is a diagram of a gate control node configuration interface in a DevOps-based process management method in an embodiment of the present application;

[0027] Fig.10 This is a diagram of a configuration interface for a pipeline access control node in a DevOps-based process management method in an embodiment of the present application;

[0028] Fig.11 It is a schematic diagram of the structure of a DevOps-based process management system in an embodiment of the present application;

[0029] Fig.12 It is a structural schematic diagram of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0030] The following describes the implementation methods of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and sub-samples in the embodiments can be combined with each other without conflict.

[0031] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application, and thus the drawings only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed at will, and the component layout may also be more complicated.

[0032] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0033] The terms "first", "second", etc. in the specification and claims of the embodiments of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged where appropriate, so as to describe the embodiments of the embodiments of the present disclosure described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0034] Unless otherwise stated, the term "plurality" means two or more.

[0035] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B indicates: A or B.

[0036] The term "and / or" is a description of the association relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.

[0037] Terminology explanation:

[0038] DevOps is a combination of Development and Operations. It represents a group of processes, methods and systems. By automating the processes of "software delivery" and "architecture change", it makes building, testing and releasing software faster, more frequent and more reliable.

[0039] CI / CD is the abbreviation of Continuous Integration, Continuous Delivery / Deployment, which is a key component of DevOps practice. Through automated tools and processes, CI / CD enables software to be frequently integrated, tested, and ultimately delivered to users during the development process, thereby improving software quality and delivery efficiency.

[0040] Pipeline: In software development, it refers to the CI / CD pipeline.

[0041] Spring Boo is a framework for simplifying the initial construction and development process of Spring applications. The framework uses a specific way to configure, so that developers no longer need to define boilerplate configurations.

[0042] Combination Figure 1 As shown, it is an implementation environment diagram of a DevOps-based process management method provided in an embodiment of the present disclosure, including a user end and a server end, wherein the user end and the server end are connected to a network and communicate with each other. In this application, the user end is the front end and the server end is the back end.

[0043] It should be understood that the DevOps-based process management method is applied to the terminal. In some embodiments, the terminal can be at least one of a computer device, a desktop device, a smart phone, and a tablet device; the server can be configured as an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, and big data and artificial intelligence platforms; the software can be an application based on the DevOps process management method, etc., but is not limited to the above forms.

[0044] Combination Figure 2 As shown, the embodiment of the present disclosure provides a flow chart of a process management method based on DevOps, including:

[0045] Step S201, disassembling the R&D process of the software project, obtaining each step in the R&D process, and encapsulating each step into an independently deployed task node;

[0046] The overall development process of a software project is broken down into smaller steps (minimum execution process), and each step is encapsulated as an independently deployed task node. For example, a software development project includes multiple task nodes such as requirements analysis, design, coding, and testing. For example, in project management tools (such as Jira, Trello, etc.), each task node is created as a task or card for easy tracking and management.

[0047] Step S202, obtaining a software project to be processed, and determining the R&D process and phase process corresponding to the software project according to the identification information, wherein the software project carries unique identification information, and the phase process includes at least two of the development phase, the testing phase, the deployment phase, the production phase, the acceptance phase, and the online phase;

[0048] Among them, a software project to be processed is obtained, and its type and corresponding R&D process are determined according to its unique identification information (such as project ID, name, etc.). For example, in a project management system, its R&D process is automatically loaded by inputting or scanning the unique identification information of the project.

[0049] Step S203, based on the R&D process and the stage process, the task nodes corresponding to the stage process are screened, and the screened task nodes are constructed into a pipeline;

[0050] Among them, based on the R&D process, corresponding task nodes are screened and combined from multiple stage processes (such as development, testing, deployment, etc.) to build a complete pipeline for the current software project.

[0051] For example, in a continuous integration / continuous deployment (CI / CD) system, the pipeline is automatically configured according to the project's R&D process to ensure that the project can be developed and deployed according to the predetermined steps.

[0052] Optionally, in some embodiments, the task nodes corresponding to the respective phases of the R&D process are selected and combined to construct a complete pipeline of the current software project, including:

[0053] According to the business logic corresponding to the R&D process of the current software project, at least one assembly line is constructed for each of the stage processes in the development stage, the testing stage, the acceptance stage and the online stage, and multiple assembly lines are combined to form a complete assembly line.

[0054] Specifically, since each software project has different requirements, that is, differences in its type, there are differences in the R&D process. By performing differentiated requirement configuration for different types of software projects, not only can the complete configured pipeline be differentiated, but it also improves the sophistication and flexibility of R&D process management.

[0055] Step S204, executing the pipeline to complete the R&D process.

[0056] Among them, different task nodes are executed for verification according to the progress of the software project in the specific implementation stage process. For example, in the development stage, the code is statically analyzed, and in the testing stage, functional testing and performance testing are performed. For example, in automated testing tools (such as Selenium, JMeter, etc.), the corresponding test tasks can be automatically executed according to the progress of the project and a test report can be generated.

[0057] In the project management system, an automated notification mechanism is configured to promptly notify relevant personnel when a task node fails verification, and provide a diagnostic report so that they can quickly locate and solve the problem.

[0058] In this embodiment, in the process of managing the development of software projects, by disassembling the development process, building pipelines, executing verification tasks and processing verification results, it is ensured that the project is developed and deployed according to the predetermined steps and quality requirements; in addition, with the support of automation tools and systems, the efficiency and accuracy of project management can be further improved.

[0059] Optionally, in some embodiments, each of the steps is encapsulated as an independently deployable task node, including:

[0060] The task nodes are divided into inherent nodes for building images or deploying services and access control nodes for verifying code quality; both the inherent nodes and the access control nodes include execution parameters, execution results, whether blocked, task number, previous node and next node;

[0061] Determine the CI / CD pipelines corresponding to the development stage, the testing stage, the deployment stage, the production stage, the acceptance stage and the launch stage respectively according to the R&D process;

[0062] Monitor the configuration requirements in each of the CI / CD pipelines,

[0063] If it is detected that the configuration requirement includes building an image or deploying a service, configuring the inherent node in the CI / CD pipeline;

[0064] If it is detected that the configuration requirement includes software component analysis or code security scanning, the access control node is configured in the CI / CD pipeline;

[0065] The current task node in the CI / CD pipeline is verified through the access control node; if the current verification passes, the next task node in the process is executed; if the current verification fails, the execution is terminated and a diagnostic report of the verification failure is fed back.

[0066] Specifically, the task nodes are first classified. Each type of task node has fixed attributes, namely, execution parameters, execution results, whether to block, task number, previous node and next node. For example, execution parameters are the parameters required by each node when executing the task; execution result is the result after the task is executed, which can be success, failure or other status; whether to block indicates whether to prevent the execution of subsequent nodes if the current node task fails; task number is a number used to uniquely identify each node; previous node refers to the predecessor node of the current node in the process; next node refers to the successor node of the current node in the process.

[0067] Configure the corresponding CI / CD pipeline for each stage, including setting trigger conditions, task execution order, environment configuration, etc. Use the monitoring function of the CI / CD system to track the configuration requirements in each pipeline in real time.

[0068] For example, when it is detected that the configuration requirements include building images or deploying services, an inherent node is configured in the corresponding CI / CD pipeline. The inherent node will perform specific build or deployment tasks, such as building Docker images, deploying Kubernetes services, etc. For example, when it is detected that the configuration requirements include software component analysis or code security scanning, a gatekeeper node is configured in the corresponding CI / CD pipeline. The gatekeeper node will perform pre-check tasks, such as scanning vulnerabilities in the code, checking the versions of dependent libraries, etc. If the gatekeeper node fails (such as a security issue), it will decide whether to continue executing subsequent nodes based on whether the attribute is blocked.

[0069] For example, if the pipeline configuration is completed, when the trigger conditions are met (such as code submission, version update, etc.), the pipeline will be automatically executed, and the monitoring function of the CI / CD system can be used to track the execution status of the pipeline in real time, including the execution results and time consumption of each node; if problems arise during the execution of the pipeline, relevant personnel will be notified in a timely manner for processing, and the configuration of the pipeline will be adjusted according to the processing results.

[0070] Through the above-mentioned method, it is ensured that the CI / CD pipeline can effectively perform tasks such as building, deploying, and checking in different R&D stages, thereby improving the development efficiency and security of software projects; according to the different progress of the software project in the stage process, different task nodes are executed to verify the current software project; if the current verification passes, the next task node in the process is executed; if the current verification fails, the execution is terminated, and a diagnostic report of the verification failure is fed back, so as to automatically monitor the quality of software delivery and reduce the workload of R&D testers in quality analysis.

[0071] In some embodiments, each of the steps is encapsulated as an independently deployed task node, further comprising:

[0072] When configuring the task nodes in each of the CI / CD pipelines, the execution order of each of the task nodes in the CI / CD pipeline is determined by connecting the previous node and the next node of each of the task nodes in series;

[0073] In response to the execution order, starting the corresponding task node according to the task number;

[0074] Controlling the task node to run according to the configured execution parameters, and determining the execution result of the current task node;

[0075] If the execution result meets the preset conditions, the next node will be executed; if the execution result does not meet the preset conditions, the task will be terminated at the current task node.

[0076] Specifically, by connecting the previous and next nodes of the task node in series, the automatic configuration of the task node in the CI / CD pipeline is realized, which greatly simplifies the process setting, enables developers to build and modify the pipeline more quickly, and improves work efficiency; determines the execution order of each task node in the pipeline to ensure the correct execution order of the task. Avoid build failure or wrong delivery caused by the wrong task execution order; starts the corresponding task node according to the task number, so that the pipeline can flexibly respond to different build requirements, which is conducive to on-demand build and delivery, improves resource utilization and build flexibility. Control the task node to run according to the configured execution parameters, so that each task can be customized according to the needs, can meet the construction requirements of different projects, and improve the flexibility and accuracy of the build. By judging whether the execution result of the current task node meets the preset conditions, it is decided whether to execute the next node, which can timely discover problems and terminate at the current task node, avoiding the accumulation and transmission of errors, and improving the reliability and stability of the build. When the execution result of a task node does not meet the preset conditions, it will be terminated at the current task node, which is conducive to timely positioning and handling of problems; developers can quickly locate the erroneous link and make corresponding repairs, thereby shortening the build cycle and improving delivery efficiency.

[0077] Through the above methods, the construction efficiency and delivery quality of the CI / CD pipeline are jointly improved in terms of automated configuration, sequential execution, flexible response, parameterized operation, result judgment and feedback, and error handling.

[0078] Optionally, in some embodiments, if it is detected that the configuration requirement includes software component analysis or code security scanning, the method further includes:

[0079] Using the Spring Boot framework to independently encapsulate at least one quality scanning tool to generate at least one microservice, the quality scanning tool including code quality analysis, code security vulnerability analysis and automated testing;

[0080] Providing a first API interface for performing a scan and a second API interface for obtaining a scan report;

[0081] The access control node is configured to call at least one of the at least one microservice by accessing the first API interface or the second API interface.

[0082] Specifically, using the Spring Boot framework, at least one quality scanning tool (such as a code quality analysis tool, a code security vulnerability analysis tool, and an automated testing tool) is independently encapsulated into a microservice. In this way, high cohesion and low coupling of the service are achieved, and the maintainability and scalability of the system are improved.

[0083] Each microservice can be deployed, run, and expanded independently, which facilitates resource allocation and performance optimization according to the needs of different quality scanning tools. At the same time, it provides a first API interface for executing scans, through which the quality scanning process is triggered, providing a convenient execution entry, which is convenient for integration into existing CI / CD pipelines or other automated processes.

[0084] A second API interface for obtaining scan reports is provided, so that users can obtain detailed scan results and reports after the scan is completed, which helps users to timely understand code quality, security vulnerabilities and test status, and then take corresponding improvement measures.

[0085] By accessing the above API interface and calling at least one of the microservices for quality scanning, the access control node plays an important role in the CI / CD pipeline. It decides whether to allow the code to continue to the next stage based on the scanning results, so that the access control node can flexibly interact with the microservices to achieve automated quality control; at the same time, it also improves the scalability and configurability of the access control node, making it easier to customize the settings according to different project requirements.

[0086] By encapsulating the quality scanning tool into a microservice and providing an API interface for calling, the quality scanning process is automated, which greatly improves the efficiency of code quality inspection and reduces the possibility of manual intervention and errors. At the same time, the introduction of the microservice architecture can more easily adapt to the needs of projects of different scales and complexities, and also improves the flexibility and response speed of the system.

[0087] By using code quality analysis tools, code security vulnerability analysis tools, and automated testing tools for quality scanning, we can effectively discover potential problems and risks in the code, which is conducive to early warning and taking corresponding measures to repair and improve, thereby improving the security and quality level of the code.

[0088] Optionally, before disassembling the R&D process of the software project to obtain each step in the R&D process, the following steps may be included:

[0089] Deploy the first and second permissions respectively according to the different roles of project managers and developers;

[0090] Invoke the first permission to create a corresponding R&D process according to the received software project as a delivery project or a non-delivery project;

[0091] Invoke the second permission and configure the software name corresponding to the software project through the research and development process;

[0092] After determining the software name, select the pre-configured R&D process to determine the pipeline template corresponding to each stage process, configure each pipeline template, and supplement the node information of each stage process by adding the task node. After the configuration is completed, execute according to the established R&D process.

[0093] In the above manner, according to the different roles of the project manager and the developer, the first permission and the second permission are respectively deployed in the system, ensuring that people of different roles can only access and execute functions related to their responsibilities, thereby improving the security of the system and the standardization of operations. When the project manager calls the first permission, the corresponding R&D process can be automatically created according to the received software project type (delivery type or non-delivery type). On the one hand, the project management process is simplified, so that the project manager can focus more on the overall planning and progress control of the project. By calling the second permission, the developer can conveniently configure the name of the software project in the R&D process, simplifying and improving the efficiency of software project management, so that the developer can enter the actual development stage of the project faster. After determining the software name, the developer is allowed to select the pre-configured R&D process and determine the pipeline template corresponding to each stage of the process. For example, according to the actual needs of the project, each pipeline template can be flexibly configured, and the node information of each stage of the process can be supplemented by adding task nodes, so that the R&D process is more in line with the actual needs of the project and the development efficiency and quality of the project are improved. After the configuration is completed, it can be automatically executed according to the established R&D process. This execution method reduces human intervention, reduces the possibility of errors, and improves the execution efficiency of the R&D process.

[0094] Optionally, verifying the current task node in the CI / CD pipeline further includes:

[0095] Obtaining a download task corresponding to the current software project, wherein the download task is generated based on the test performance of the current task node in the CI / CD pipeline, wherein the test performance includes software analysis or security scanning;

[0096] In response to the download task, downloading from the server a target application package required for the software project performance test;

[0097] The target application package is received, and when the target application package is installed, the software project is verified to obtain a verification record.

[0098] In the above manner, a series of operations are initiated by obtaining the download task corresponding to the current software project, which realizes the automation of the process and the precise driving of the task, reduces manual intervention, and improves work efficiency; in response to the download task, the target application package required for the software project test performance is downloaded from the server, and after receiving the target application package, its installation is checked. If the installation is complete, the software project is immediately verified and the verification results are recorded to ensure the integrity and consistency of the software project, and the verification records are provided for subsequent analysis and improvement; through the verification records, problems in the test performance of the software project can be discovered in time, such as potential security vulnerabilities, code errors, etc. In this way, not only can the problem be quickly located and corresponding solutions be taken, but HIA also improves the efficiency and quality of software development.

[0099] Optionally, the verifying the software project to obtain a verification record includes:

[0100] In response to the verification start operation, displaying a verification auxiliary floating window, wherein the verification auxiliary floating window includes a task selection control;

[0101] In response to a verification task selection request triggered by the task selection control, sending the verification task selection request to a server so that the server obtains a verification task to be processed;

[0102] Receive the pending verification tasks sent by the server, execute any verification task in response to a trigger operation based on any verification task among the pending verification tasks, and obtain the verification record based on a verification result corresponding to any verification task.

[0103] Specifically, when the user performs a verification start operation, a verification auxiliary floating window is immediately displayed. The floating window contains a task selection control, allowing the user to intuitively see and select the task that needs to be verified. This improves the friendliness and convenience of user interaction and enables users to manage verification tasks more easily.

[0104] After the user triggers the verification task selection request through the task selection control, the request is sent to the server. The verification obtains the pending verification tasks from the server and returns them to the system. This dynamic way of obtaining verification tasks can reflect the latest verification requirements in real time, improving the timeliness and accuracy of verification tasks.

[0105] After receiving the pending verification tasks, the user can choose to trigger any of the verification tasks for execution. This flexibility allows the user to arrange the execution order of the verification tasks according to their own needs or priorities, improving the controllability and efficiency of the verification process.

[0106] For any verification task triggered by the user, a verification record is generated based on the verification result corresponding to the task. Through this instant feedback mechanism, the execution status and results of the verification task can be understood in a timely manner, so that corresponding measures can be taken or subsequent operations can be performed.

[0107] By generating verification records, the execution process, results and related information of the verification task are fully recorded, which improves the transparency and traceability of the verification process. The historical records of the verification task can be viewed and audited at any time to ensure the accuracy and compliance of the verification process.

[0108] The verification process has been optimized by integrating verification auxiliary floating windows, dynamically obtaining verification tasks, and instantly feedback verification results. This makes the verification process more efficient, convenient, and controllable, reduces verification costs and time costs, and improves overall verification efficiency and quality.

[0109] See also Figure 3 , is a logical flow chart of a DevOps-based process management method in an embodiment of the present application, including:

[0110] Abstract each step in the development process of a software project and define the step as a task node in the development process. Multiple nodes can be connected in series to form a pipeline. In a complete software development process, there may be multiple stages. Figure 3 Including the development stage, testing stage, and formal stage, you can build a production line for each stage, and finally form a complete R&D process.

[0111] Among them, when developers create pipelines for software applications, they can only choose the orchestrated R&D process, task nodes, pipelines and R&D processes.

[0112] See also Figure 4 , is a DevOps system architecture diagram in a DevOps-based process management method in an embodiment of the present application, including:

[0113] Through encapsulation technology, various code quality and security scanning tools are encapsulated into independently deployable components. Such components are access control. Access control is also encapsulated as an independently deployable task node. When the pipeline executes to the access control node, the independent component is automatically called to perform software quality scanning. The pipeline will parse the scanning results and decide whether to continue or terminate the pipeline based on the scanning results.

[0114] For example, the DevOps platform has the functions of R&D process management, application management and integration management, and the integrated management is equipped with code security scanning, software component analysis and automated testing functions.

[0115] In some embodiments, if the project manager is in charge of building the R&D process, the R&D personnel will create software applications, select R&D processes, supplement node information, and execute pipeline distribution tasks.

[0116] 1) Packaging quality scanning tool

[0117] There are multiple quality scanning tools, such as code quality analysis, code security vulnerability analysis, automated testing, etc. They are encapsulated as an independent microservice using the Spring Boot framework, exposing two APIs: "Execute Scan" and "Get Scan Report".

[0118] 2) Define pipeline task nodes

[0119] There are two types of task nodes. One type is the inherent nodes in the CI / CD pipeline, such as building images and service deployment. These nodes rely on Jenkins and Kubernetes. The other type is the access control node. Behind this type of node is the quality scanning tool encapsulated in step 1. The node only needs to call the "Execute Scan" interface and the "Get Scan Report" interface. In order to flexibly configure whether the access control node blocks the process, it is necessary to define the "Whether to Block" attribute. Only when this attribute is true will the pipeline be blocked from continuing when the scan fails.

[0120] In order to connect the task nodes in series, the task nodes also need to define two attributes: the previous node and the next node. In summary, all the attributes of the task nodes are: execution parameters, execution results, whether to block, task number, previous node, and next node.

[0121] After the task node is defined, it is put into the pipeline template for use.

[0122] 3) Define the R&D pipeline

[0123] Multiple task nodes connected in series form a R&D assembly line.

[0124] Each node does not need to remember its position in the process, but only needs to save its previous node and next node, and the pipeline only needs to save the information of the first node. Through this data structure, any task nodes can be connected in series into a R&D pipeline.

[0125] 4) Define the R&D process

[0126] The R&D pipeline corresponds to a stage of the R&D process. A complete R&D process usually has multiple stages, such as "development stage", "testing stage", "acceptance stage" and "online stage".

[0127] In the development phase, the goal is to develop and deploy quickly, and unnecessary links need to be simplified. The configuration can be as follows:

[0128] During the testing phase, you need to check the code quality, so you need to add various access control nodes: Figure 5 , is a flowchart of the test phase in a DevOps-based process management method in an embodiment of the present application.

[0129] 5) Create an application

[0130] See Figure 6 , is a diagram of an application creation configuration interface in a DevOps-based process management method in an embodiment of the present application. When a developer creates a pipeline for an application, he selects a research and development process and no longer needs to manually build a pipeline. The pipeline is automatically created based on the selected research and development process as a pipeline template. The developer only needs to fill in the necessary node information, such as the code address, etc., and eventually the node information will be saved in the "scan parameters" of the node.

[0131] 6) Execution pipeline

[0132] When executing the pipeline, the access control node will be automatically triggered, that is, the "scan interface" in the node properties will be called with "scan parameters". After the execution is triggered, the scanning component will create a scanning task to start scanning, and return the task number to the node of the pipeline, which will be saved in the scanning task number of the node. After the scanning component task is completed, the DevOps system's general callback interface will be called with the task number. The callback interface will find the corresponding task node through the task number. The task node will then use the task number to obtain the scan report through the report interface, and decide whether to continue or terminate the pipeline execution based on the scan report.

[0133] 7) Scenario Examples

[0134] The project manager defines a "delivery project development process" that includes a development phase and a testing phase.

[0135] In the development phase, to facilitate rapid integration, only two nodes are built and deployed.

[0136] During the testing phase, the quality of the delivered software needs to be controlled, and a series of quality control nodes need to be added. Therefore, "software component analysis", "code security scanning" and "code scanning" are pulled as quality gates. Only after passing all gates can you go to the "application service deployment" node.

[0137] After creating an application, developers no longer need to manually build a CI / CD pipeline. Using the R&D process as a template, the pipeline is automatically built. Developers only need to configure the necessary information for each node. For details, see Figure 7 , a node configuration interface diagram in a DevOps-based process management method in an embodiment of the present application, through node name, node code, target image, shared storage name, mount path, working directory, dockfile file and build content.

[0138] Finally, the developers complete the development process of the entire software life cycle according to the development process established by the project manager. Figure 8 , a diagram of the configuration interface for the R&D stage in a DevOps-based process management method in an embodiment of the present application.

[0139] Access control function

[0140] AFunction Introduction

[0141] The access control function is the core of this R&D process management solution. Its purpose is to improve the quality of software delivery by automatically scanning code quality and blocking the pipeline of unqualified code, so as to prevent low-quality or security-risk code from being released to the production environment.

[0142] In a production line, one or more access control systems can be configured according to the needs of R&D management. The use of access control systems depends on the project management specialist. The reasonable use of access control systems at different stages of the R&D process can better improve the quality of software. For example, in the development stage, you can configure code quality access control (sonarqube) to scan for hidden bugs and bad smells in the code. If the access control scan fails, the image will not be allowed to be built, forcing developers to optimize the code they submit based on the analysis report. In the testing stage, you can configure automated testing access control. Only after the automated test passes can the test environment be deployed and tested. This can greatly improve the quality of the tested code and reduce the workload of testers.

[0143] Business logic diagram, see Figure 8 , a diagram of the configuration interface for the R&D stage in a DevOps-based process management method in an embodiment of the present application.

[0144] B Function Implementation

[0145] (1) Implementing access control nodes

[0146] Behind the access control are several open source or self-developed scanning tools, such as sonarqube, SAST, and self-developed automated testing tools. The implementation of the access control node is actually a packaged scanning tool. The following uses the open source security scanning tool SAST as an example to introduce how to implement a code security scanning access control node.

[0147] After the SAST scanning tool is deployed, the "Execute Scan" and "Get Scan Report" interfaces are exposed. A new access control node is added, and the "Execute Scan" and "Get Scan Report" interface URLs are configured. The access control node is responsible for calling these two interfaces to complete the "scan" and "report parsing" actions.

[0148] If the access control node parses the report and the result is "failed", the pipeline will be blocked from continuing execution.

[0149] See also Fig. 9 , which is a diagram of the access control node configuration interface in a DevOps-based process management method in an embodiment of the present application.

[0150] C Operation steps

[0151] (1) Add access control nodes

[0152] (2) Pipeline integrated access control node

[0153] After the access control node is implemented, you can find this node in the pipeline template and pull the node into the existing pipeline. This logic is similar to inserting an element in the middle of a linked list.

[0154] See Fig.10 , is a diagram of an access control node configuration interface for pipeline configuration in a DevOps-based process management method in an embodiment of the present application.

[0155] (3) Execute access control node

[0156] When executing the pipeline, the access control nodes will be executed in sequence with the pipeline, and the execution results will be displayed in the execution record. If the result is not passed, the pipeline will be blocked from continuing to execute.

[0157] Since the R&D process is configured by project management specialists and developers cannot modify the R&D process, the access control nodes in the process cannot be bypassed, thus avoiding the situation where non-compliant code is released to the production environment.

[0158] See also Fig.11 , is a schematic diagram of the structure of a DevOps-based process management system in an embodiment of the present application, including:

[0159] The node definition module 1101 is used to disassemble the development process of the software project, obtain each step in the development process, and encapsulate each step into an independently deployed task node;

[0160] The process determination module 1102 is used to obtain a software project to be processed, and determine the R&D process and phase process corresponding to the software project according to the identification information, wherein the software project carries unique identification information, and the phase process includes at least two of the development phase, the testing phase, the deployment phase, the production phase, the acceptance phase, and the online phase;

[0161] The pipeline construction module 1103 selects the task nodes corresponding to the stage process based on the R&D process and the stage process, and constructs the selected task nodes into a pipeline;

[0162] The process management module 1104 is used to execute the pipeline and complete the R&D process.

[0163] It should be noted that the DevOps-based process management system of this application corresponds one-to-one to the DevOps-based process management method. The corresponding technical details and technical solutions refer to the above-mentioned DevOps-based process management method, and will not be repeated here.

[0164] Through the above method, the present application disassembles the R&D process of the software project, obtains each step in the R&D process, and encapsulates each step into an independently deployed task node, which is conducive to the process of R&D process; the corresponding R&D process of the current software project is determined according to the identification information. On the one hand, the R&D process management is introduced into the CI / CD process of the DevOps system, which restricts developers from arbitrarily releasing software without following the specifications, thereby improving the reliability of the software; based on the R&D process, the task nodes corresponding to each of the multiple stage processes are selected and combined to construct a complete pipeline for the current software project; on the other hand, a flexible process construction mechanism is introduced, and different R&D processes can be flexibly constructed according to the management specifications of different projects, thereby improving the sophistication and flexibility of R&D process management; through the refined management and automated control of the R&D process of the software project, it is ensured that the software project can meet the established quality standards at each stage, which is conducive to timely discovery and problem solving, and avoiding the expansion of problems in subsequent stages.

[0165] In other embodiments, the present disclosure also provides an electronic device, including: a processor and a memory; the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the above method.

[0166] Fig.12The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Fig.12 The computer system 1200 of the electronic device shown is only an example and should not bring any limitation to the functions and application scope of the embodiments of the present application.

[0167] like Fig.12 As shown, the computer system 1200 includes a central processing unit (CPU) 1201, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1202 or the program loaded from the storage part 1208 to the random access memory (RAM) 1203, such as executing the method in the above embodiment. In the random access memory 1203, various programs and data required for system operation are also stored. The central processing unit 1201, the read-only memory 1202 and the random access memory 1203 are connected to each other through a bus 1204. An input / output (I / O) interface 1205 is also connected to the bus 1204.

[0168] The following components are connected to the input / output interface 1205: an input section 1206 including a keyboard, a mouse, etc.; an output section 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the input / output interface 1205 as needed. A removable medium 1211, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1210 as needed so that a computer program read therefrom is installed into the storage section 1208 as needed.

[0169] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication part 1209, and / or installed from a removable medium 1211. When the computer program is executed by the central processing unit 1201, various functions defined in the method of the present application are executed.

[0170] The above description and accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent possible changes only. Unless explicitly required, separate components and functions are optional, and the order of operation may vary. Parts and subsamples of some embodiments may be included in or replace parts and subsamples of other embodiments. Moreover, the words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" used in this application refers to any and all possible combinations listed in association with one or more. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of a stated sub-sample, whole, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other sub-samples, wholes, steps, operations, elements, components and / or groups of these. In the absence of further restrictions, the elements defined by the sentence "comprising a ..." do not exclude the presence of other identical elements in the process, method or device comprising the elements. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the various embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.

[0171] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software may depend on the specific application and design constraints of the technical solution. Technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present disclosure. Technicians can clearly understand that for the convenience and simplicity of description, the specific working process of the methods, devices and units described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0172] In the embodiments disclosed herein, the disclosed methods and products (including but not limited to devices, equipment, etc.) can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units can be only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some sub-samples can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. 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 units may be selected according to actual needs to implement this embodiment. In addition, each functional unit in the embodiment of the present disclosure may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit.

[0173] The flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the method, system and computer program product according to the embodiment of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and a part of the module, program segment or code contains one or more executable instructions for realizing the specified logical function. In some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. In the description corresponding to the flowchart and block diagram in the accompanying drawings, the operations or steps corresponding to different boxes can also occur in a different order from the order disclosed in the description, and sometimes there is no specific order between different operations or steps. For example, two consecutive operations or steps can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, which can depend on the functions involved. Each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware-based method for performing the specified functions or actions, or may be implemented by a combination of dedicated hardware and computer instructions.

Claims

1. A process management method based on DevOps, characterized in that: include: Decomposing the R&D process of the software project, obtaining each step in the R&D process, and encapsulating each step into an independently deployed task node; Acquire a software project to be processed, and determine the R&D process and phase process corresponding to the software project according to the identification information, wherein the software project carries unique identification information, and the phase process includes at least two of a development phase, a testing phase, a deployment phase, a production phase, an acceptance phase, and an online phase; Based on the R&D process and the stage process, the task nodes corresponding to the stage process are screened, and the screened task nodes are constructed into a pipeline; Execute the pipeline to complete the R&D process.

2. The method according to claim 1, characterized in that The task nodes corresponding to the stage process are screened based on the R&D process and the stage process, and the screened task nodes are constructed into a pipeline, including: Determine the project name or project ID corresponding to the software project according to the identification information; Using the project name or the project ID to configure the business logic of the software project, and determining the corresponding R&D process and phase process of the software project based on the business logic; Determine each stage process in the R&D process, select the matching task nodes for each stage process, build each task node to construct a pipeline for each stage process, and combine multiple pipelines to form a pipeline for the software project to be processed.

3. The method according to claim 1, characterized in that Encapsulate each of the above steps into an independently deployed task node, including: The task nodes are divided into inherent nodes for building images or deploying services and access control nodes for verifying code quality; both the inherent nodes and the access control nodes include execution parameters, execution results, whether blocked, task number, previous node and next node; Determine the CI / CD pipelines corresponding to the development stage, the testing stage, the deployment stage, the production stage, the acceptance stage and the launch stage respectively according to the R&D process; Monitor the configuration requirements in each of the CI / CD pipelines, If it is detected that the configuration requirement includes building an image or deploying a service, configuring the inherent node in the CI / CD pipeline; If it is detected that the configuration requirement includes software component analysis or code security scanning, the access control node is configured in the CI / CD pipeline; The current task node in the CI / CD pipeline is verified through the access control node; if the current verification passes, the next task node in the process is executed; if the current verification fails, the execution is terminated and a diagnostic report of the verification failure is fed back.

4. The method according to claim 3, characterized in that Each of the steps is encapsulated as an independently deployed task node, which also includes: When configuring the task nodes in each of the CI / CD pipelines, the execution order of each of the task nodes in the CI / CD pipeline is determined by connecting the previous node and the next node of each of the task nodes in series; In response to the execution order, starting the corresponding task node according to the task number; Controlling the task node to run according to the configured execution parameters, and determining the execution result of the current task node; If the execution result meets the preset conditions, the next node will be executed; if the execution result does not meet the preset conditions, the task will be terminated at the current task node.

5. The method according to claim 3, characterized in that: If the configuration requirement is detected before software component analysis or code security scanning, it also includes: Using the Spring Boot framework to independently encapsulate at least one quality scanning tool to generate at least one microservice, the quality scanning tool including code quality analysis, code security vulnerability analysis and automated testing; Providing a first API interface for performing a scan and a second API interface for obtaining a scan report; The access control node is configured to call at least one of the at least one microservice by accessing the first API interface or the second API interface.

6. The method according to claim 1, characterized in that The development process of the software project is disassembled to obtain each step in the development process, including: Deploy the first and second permissions respectively according to the different roles of project managers and developers; Invoke the first permission to create a corresponding R&D process according to the received software project as a delivery project or a non-delivery project; Invoke the second permission and configure the software name corresponding to the software project through the research and development process; After determining the software name, select the pre-configured R&D process to determine the pipeline template corresponding to each stage process, configure each pipeline template, and supplement the node information of each stage process by adding the task node. After the configuration is completed, execute according to the established R&D process.

7. The method according to claim 3, characterized in that Verifying the current task node in the CI / CD pipeline also includes: Obtaining a download task corresponding to the current software project, wherein the download task is generated based on the test performance of the current task node in the CI / CD pipeline, wherein the test performance includes software analysis or security scanning; In response to the download task, downloading from the server a target application package required for the software project performance test; The target application package is received, and when the target application package is installed, the software project is verified to obtain a verification record.

8. The method according to claim 7, characterized in that The verifying the software project to obtain a verification record includes: In response to the verification start operation, displaying a verification auxiliary floating window, wherein the verification auxiliary floating window includes a task selection control; In response to a verification task selection request triggered by the task selection control, sending the verification task selection request to a server so that the server obtains a verification task to be processed; Receive the pending verification tasks sent by the server, execute any verification task in response to a trigger operation based on any verification task among the pending verification tasks, and obtain the verification record based on a verification result corresponding to any verification task.

9. A process management system based on DevOps, characterized in that: include: A node definition module is used to disassemble the R&D process of the software project, obtain each step in the R&D process, and encapsulate each step into an independently deployed task node; a process determination module, used to obtain a software project to be processed, and determine the R&D process and phase process corresponding to the software project according to the identification information, wherein the software project carries unique identification information, and the phase process includes at least two of the development phase, the testing phase, the deployment phase, the production phase, the acceptance phase, and the online phase; A pipeline construction module, which selects the task nodes corresponding to the stage process based on the R&D process and the stage process, and constructs the selected task nodes into a pipeline; The process management module is used to execute the pipeline and complete the R&D process.

10. An electronic device, characterized in that: include: Processor and memory; The memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the method according to claims 1 to 8.

Images