DevOps-based project management method, device and storage medium

Abstract

The embodiment of the present invention provides a DevOps-based project management method, device and storage medium. The method includes: creating a non-source code project according to a non-source code project creation request; deploying a newly created binary product corresponding to the non-source code project to a test product library of a product center, and the test product library triggers a pipeline; the pipeline manages the non-source code project based on the newly created binary product. Through the present invention, the problem that the DevOps platform in the related art cannot support the serial connection and management of non-source code projects is solved, and the DevOps system realizes the serial connection and management of non-source code projects.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communications, and in particular, to a DevOps-based project management method, device, and storage medium. Background Art

[0002] DevOps (a combination of Development and Operations) is a collective name for a set of processes, methods, and systems that are used to promote communication, collaboration, and integration between development (application / software engineering), technical operations, and quality assurance (QA) departments.

[0003] Currently, most of the DevOps platforms in the industry start with code bases, build source code projects, and connect the DevOps platform system. There is no mature and complete connection and management solution for product management, testing, deployment, release, rollback, etc. of non-source code projects in traditional industries.

[0004] In the practice of DevOps, traditional enterprises are often faced with many projects without source code in digital transformation. In these projects without source code, outsourcing vendors only provide product packages. Such projects without source code are completely dependent on external vendors. Traditional enterprises cannot control the security and stability of such project products. The project products are manually managed both online and offline, resulting in a chaotic management process system, a long online cycle, and cumbersome rollback steps. Summary of the invention

[0005] The embodiments of the present invention provide a DevOps-based project management method, device and storage medium to at least solve the problem in the related art that the DevOps platform cannot support the serial connection and management of non-source code projects.

[0006] According to one embodiment of the present invention, a DevOps-based project management method is provided, including: creating a sourceless code project according to a sourceless code project creation request; deploying a newly created binary artifact corresponding to the sourceless code project to a test artifact library of a product center, the test artifact library triggering a pipeline; the pipeline managing the sourceless code project based on the newly created binary artifact.

[0007] In at least one exemplary embodiment, the method further includes: when the test artifact library detects that the binary artifact corresponding to the sourceless code project is updated, the test artifact library triggers the pipeline; and the pipeline manages the sourceless code project based on the updated binary artifact.

[0008] In at least one exemplary embodiment, the pipeline includes a main pipeline and a sub-pipeline, and the test artifact library triggering the pipeline includes: the test artifact library triggering the main pipeline through a hook function.

[0009] In at least one exemplary embodiment, the pipeline includes a main pipeline and a sub-pipeline, and the pipeline manages the sourceless code projects based on the newly created binary artifact or the updated binary artifact, including: reading the newly created binary artifact or the updated binary artifact in the test artifact library through a plug-in installed in the main pipeline for reading files in the test artifact library; and managing the sourceless code projects based on the read newly created binary artifact or the updated binary artifact according to the configuration process of the main pipeline.

[0010] In at least one exemplary embodiment, according to the configuration process of the mainstream pipeline, the management of the source code-free project based on the read new binary artifact or the updated binary artifact includes: scanning the read new binary artifact or the updated binary artifact; performing environmental deployment verification on the new binary artifact or the updated binary artifact, wherein the environmental deployment verification includes at least one of the following: development environment deployment verification, test environment deployment verification, pre-production environment deployment verification; testing the new binary artifact or the updated binary artifact.

[0011] In at least one exemplary embodiment, after testing the newly created binary artifact or the updated binary artifact, the method further includes: triggering the sub-pipeline when predetermined conditions are met, wherein the predetermined conditions include: the newly created binary artifact or the updated binary artifact is tested and passed; or, the newly created binary artifact or the updated binary artifact is tested and passed and the test result meets a predetermined quality threshold; and according to the configuration process of the sub-pipeline, promoting the newly created binary artifact or the updated binary artifact to the production artifact library of the artifact center.

[0012] In at least one exemplary embodiment, after the newly created binary artifact or the updated binary artifact is promoted to the production artifact library of the artifact center according to the configuration process of the sub-pipeline, the method further includes: the publishing center verifies the binary artifact corresponding to the sourceless code project and the sourceless code project in the production artifact library; if the verification passes, the sourceless code project is published; if the verification fails, the binary artifact is rolled back in the production artifact library and / or the test artifact library.

[0013] In at least one exemplary embodiment, creating a passive code project according to a passive code project creation request includes: creating the passive code project in an organization management center according to the passive code project creation request, and accepting configuration of project information of the passive code project.

[0014] In at least one exemplary embodiment, the project information of the source-free project includes at least one of the following: project members, roles of the project members, and configuration procedures of the pipeline.

[0015] According to another embodiment of the present invention, a DevOps-based project management device is provided, including: an organization management center, used to create a non-source code project according to a non-source code project creation request; a product center, including a test product library, wherein the test product library is used to store newly created binary products corresponding to the non-source code project and trigger a pipeline; the pipeline is used to manage the non-source code project based on the newly created binary products.

[0016] In at least one exemplary embodiment, the test artifact library is further used to trigger the pipeline when it is detected that the binary artifact corresponding to the sourceless code project is updated; the pipeline is also used to manage the sourceless code project based on the updated binary artifact.

[0017] According to yet another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any one of the above method embodiments when run.

[0018] According to yet another embodiment of the present invention, there is provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0019] Through the present invention, a source-free code project is created according to a source-free code project creation request; the newly created binary product corresponding to the source-free code project is deployed to the test product library of the product center, and the test product library triggers the pipeline; the pipeline manages the source-free code project based on the newly created binary product. This solution takes the product center as the core, connects the various DevOps modules in series, and allows source-free code products to enjoy the full-process management, automation capabilities, change management and other capabilities brought by the DevOps system. Therefore, it can solve the problem in the related technology that the DevOps platform cannot support the series connection and management of source-free code projects, and realize the series connection and management of source-free code projects by the DevOps system. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 This is a schematic diagram of the system architecture of the Yunxiao platform;

[0021] Figure 2 This is a schematic diagram of the system architecture of the Tuskfish platform;

[0022] Figure 3 It is a hardware structure block diagram of a computer of a DevOps-based project management method according to an embodiment of the present invention;

[0023] Figure 4 is a flowchart of a DevOps-based project management method according to an embodiment of the present invention;

[0024] Figure 5 is a structural block diagram of a DevOps-based project management device according to an embodiment of the present invention;

[0025] Figure 6 is a detailed structural block diagram of a DevOps-based project management device according to an embodiment of the present invention;

[0026] Figure 7 It is a functional architecture diagram of a source code-free project management system based on DevOps according to an embodiment of the present invention;

[0027] Figure 8 It is a flow chart of DevOps-based source-free project management according to an embodiment of the present invention;

[0028] Fig. 9 It is a schematic diagram of an artifact center in which a project configuration manager uploads and deploys binary artifacts to a test environment according to an embodiment of the present invention. DETAILED DESCRIPTION

[0029] At present, most of the DevOps platforms in the industry start with code bases, build source code projects, and connect the DevOps platform system. For example, Figure 1 This is a schematic diagram of the system architecture of the Yunxiao platform. Figure 1 As shown in the figure, the Yunxiao platform takes demand as the value unit, creates new feature branches in the code base, streamlines the end-to-end delivery process, and organizes cross-functional collaboration with flow efficiency as the core. Figure 2 This is a schematic diagram of the system architecture of the Tuskfish platform. Figure 2 As shown in the figure, the Tuskfish platform is divided into 4 parts. The Tuskfish platform is also managed from the code base branch to pull through the end-to-end delivery process. It can be seen that most of the current mainstream DevOps products take demand as the value unit, through the creation of new code base feature branches, pull through the end-to-end delivery process, connect DevOps core modules such as agile dashboards, code centers, assembly line centers, and product libraries, and organize cross-functional collaboration with flow efficiency as the core.

[0030] For non-source code projects in traditional industries, the main pain points of mainstream DevOps products in the industry are as follows:

[0031] The project and the code base are highly coupled, usually in a one-to-one relationship. There are no source code-free projects on traditional DevOps platforms.

[0032] The pipeline center is triggered by the code base. For source code-free projects, there are only binary artifacts. Without the code base, the pipeline cannot be triggered. Only the artifacts cannot be deployed and verified in the development and test environment through the pipeline.

[0033] In the traditional financial industry, there is a lack of product management and circulation standards.

[0034] It can be seen that the current DevOps platform generally takes requirements & code repositories as the starting point, establishes the correlation between projects and code repositories, connects various DevOps modules in series, and pulls through the end-to-end delivery process, while there is no mature and complete connection and management solution for product management, testing, deployment, release, rollback, etc. of non-source code projects in traditional industries. The embodiments and exemplary embodiments of the present invention are oriented to non-source code projects, with the product center as the core, connecting various DevOps modules in series, so that non-source code products can enjoy the full process management, automation capabilities, change management and other capabilities brought by the DevOps system.

[0035] In addition, the current DevOps pipelines in the industry are generally triggered by code repositories. The pipelines are automatically triggered based on the version updates of the code repositories. In the DevOps-based source-free project management system of the embodiments and exemplary embodiments of the present invention, the pipeline trigger source may come from the product center. Based on the product version changes, the hook function is called to trigger the pipeline.

[0036] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and in combination with the embodiments.

[0037] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0038] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a computer as an example, Figure 3 1 is a hardware structure diagram of a computer of a DevOps-based project management method according to an embodiment of the present invention. Figure 3 As shown, the computer may include one or more ( Figure 3Only one is shown in the figure) a processor 302 (the processor 302 may include but is not limited to a central processing unit CPU, a microprocessor MCU or a programmable logic device FPGA and the like) and a memory 304 for storing data, wherein the computer may also include a transmission device 306 and an input / output device 308 for communication functions. It can be understood by those skilled in the art that Figure 3 The structure shown is only for illustration and does not limit the structure of the above-mentioned computer. Figure 3 More or fewer components as shown, or with Figure 3 Different configurations shown.

[0039] The memory 304 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the DevOps-based project management method in the embodiment of the present invention. The processor 302 executes various functional applications and data processing by running the computer program stored in the memory 304, that is, the above-mentioned DevOps-based project management method is realized. The memory 304 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 304 may further include a memory remotely arranged relative to the processor 302, and these remote memories can be connected to the computer via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0040] The transmission device 306 is used to receive or send data via a network. Specific examples of the above network may include a wireless network or a wired network provided by a communication provider.

[0041] In this embodiment, a DevOps-based project management method running on the above-mentioned computer is provided. Figure 4 is a flowchart of a DevOps-based project management method according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps:

[0042] Step S402: creating a non-source code project according to the non-source code project creation request.

[0043] In at least one exemplary embodiment, creating a passive code project according to a passive code project creation request may include: creating the passive code project in an organization management center according to the passive code project creation request, and accepting configuration of project information of the passive code project.

[0044] In at least one exemplary embodiment, the project information of the source-free project may include at least one of the following: project members, roles of the project members, and configuration flow of the pipeline.

[0045] Step S404: deploy the newly created binary artifact corresponding to the non-source code project to the test artifact library of the artifact center, and the test artifact library triggers the pipeline.

[0046] In at least one exemplary embodiment, the pipeline may include a main pipeline and a sub-pipeline, and the test artifact library triggering the pipeline may include: the test artifact library triggering the main pipeline through a hook function.

[0047] Step S406: the pipeline manages the non-source code project based on the newly created binary artifact.

[0048] In at least one exemplary embodiment, the method may further include: when the test artifact library detects that the binary artifact corresponding to the non-source code project is updated, the test artifact library triggers the pipeline; the pipeline manages the non-source code project based on the updated binary artifact. According to this solution, the pipeline is not only triggered when a new binary artifact is added to the test artifact library, but also when the binary artifact stored in the test artifact library is updated (for example, there is a version change, which may include version evolution and version rollback), thereby achieving smooth and continuous management of the non-source code project.

[0049] In at least one exemplary embodiment, the pipeline may include a main pipeline and a sub-pipeline, and the pipeline managing the sourceless code project based on the newly created binary artifact or the updated binary artifact may include: reading the newly created binary artifact or the updated binary artifact in the test artifact library through a plug-in installed in the main pipeline for reading files in the test artifact library; and managing the sourceless code project based on the read newly created binary artifact or the updated binary artifact according to the configuration process of the main pipeline.

[0050] In at least one exemplary embodiment, according to the configuration process of the mainstream pipeline, managing the sourceless code project based on the read new binary artifact or the updated binary artifact may include: scanning the read new binary artifact or the updated binary artifact; performing environmental deployment verification on the new binary artifact or the updated binary artifact, wherein the environmental deployment verification may include at least one of the following: development environment deployment verification, test environment deployment verification, pre-production environment deployment verification; testing the new binary artifact or the updated binary artifact.

[0051] In at least one exemplary embodiment, after testing the newly created binary artifact or the updated binary artifact, the method may further include: triggering the sub-pipeline when predetermined conditions are met, wherein the predetermined conditions may include: the newly created binary artifact or the updated binary artifact passes the test; or, the newly created binary artifact or the updated binary artifact passes the test and the test result meets a predetermined quality threshold; and according to the configuration process of the sub-pipeline, promoting the newly created binary artifact or the updated binary artifact to the production artifact library of the artifact center.

[0052] In at least one exemplary embodiment, after the newly created binary artifact or the updated binary artifact is promoted to the production artifact library of the artifact center according to the configuration process of the sub-pipeline, the method may also include: the publishing center verifies the binary artifact corresponding to the sourceless code project and the sourceless code project in the production artifact library; if the verification passes, the sourceless code project is published; if the verification fails, the binary artifact is rolled back in the production artifact library and / or the test artifact library.

[0053] Through the above steps, a source-free code project is created according to the source-free code project creation request; the newly created binary artifact corresponding to the source-free code project is deployed to the test artifact library of the product center, and the test artifact library triggers the pipeline; the pipeline manages the source-free code project based on the newly created binary artifact. This solution takes the product center as the core, connects the various DevOps modules in series, and allows source-free code products to enjoy the full-process management, automation capabilities, change management and other capabilities brought by the DevOps system. Therefore, it can solve the problem in the related technology that the DevOps platform cannot support the series connection and management of source-free code projects, and realize the series connection and management of source-free code projects by the DevOps system.

[0054] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0055] In this embodiment, a DevOps-based project management device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0056] Figure 5 is a structural block diagram of a DevOps-based project management device according to an embodiment of the present invention, such as Figure 5 As shown, the device comprises:

[0057] The organization management center 52 is used to create a non-source code project according to a non-source code project creation request;

[0058] The product center 54 may include a test product library 541, wherein the test product library 541 is used to store the newly created binary products corresponding to the non-source code project and trigger the pipeline 56;

[0059] The pipeline 56 is used to manage the non-source code project based on the newly created binary product.

[0060] In at least one exemplary embodiment, the test artifact library 541 is also used to trigger the pipeline 56 when it is detected that the binary artifact corresponding to the sourceless code project is updated; the pipeline 56 is also used to manage the sourceless code project based on the updated binary artifact.

[0061] In at least one exemplary embodiment, the pipeline 56 includes a main pipeline 561 and a sub-pipeline 562 , and the test artifact library 541 triggers the pipeline 56 including: the test artifact library 541 triggers the main pipeline 561 through a hook function.

[0062] In at least one exemplary embodiment, the pipeline 56 includes a mainstream pipeline 561 and a sub-pipeline 562, and the pipeline 56 is used to read the newly created binary artifact or the updated binary artifact in the test artifact library 541 through a plug-in installed in the mainstream pipeline 561 for reading files in the test artifact library 541; according to the configuration process of the mainstream pipeline 561, the source code-free project is managed based on the read newly created binary artifact or the updated binary artifact.

[0063] In at least one exemplary embodiment, the pipeline 56 is used to manage the source-free project based on the read new binary artifact or the updated binary artifact according to the configuration process of the main pipeline 561 in the following manner: scanning the read new binary artifact or the updated binary artifact; performing environmental deployment verification on the new binary artifact or the updated binary artifact, wherein the environmental deployment verification includes at least one of the following: development environment deployment verification, test environment deployment verification, and pre-production environment deployment verification; testing the new binary artifact or the updated binary artifact.

[0064] In at least one exemplary embodiment, the pipeline 56 is also used to trigger the sub-pipeline 562 when predetermined conditions are met, wherein the predetermined conditions include: the newly created binary artifact or the updated binary artifact is tested and passed; or, the newly created binary artifact or the updated binary artifact is tested and passed and the test result meets a predetermined quality threshold; according to the configuration process of the sub-pipeline 562, the newly created binary artifact or the updated binary artifact is promoted to the production artifact library 542 of the artifact center 54.

[0065] Figure 6 Detailed structural diagram of a DevOps-based project management device according to an embodiment of the present invention. Figure 6 As shown, in at least one exemplary embodiment, the device also includes: a publishing center 62, which is used to verify the binary artifacts corresponding to the sourceless code projects and the sourceless code projects in the production artifact library 542 after the pipeline 56 promotes the newly created binary artifact or the updated binary artifact to the production artifact library 542 of the artifact center 54 according to the configuration process of the sub-pipeline 562; if the verification is passed, the sourceless code projects are published; if the verification fails, the binary artifacts are rolled back in the production artifact library 542 and / or the test artifact library 541.

[0066] In at least one exemplary embodiment, the organization management center 52 is used to create the passive code project in the organization management center 52 according to the passive code project creation request, and accept the configuration of the project information of the passive code project. In at least one exemplary embodiment, the project information of the passive code project includes at least one of the following: project members, roles of the project members, and configuration flow of the pipeline 56.

[0067] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0068] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0069] In this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0070] S1, creating a non-source code project according to a non-source code project creation request;

[0071] S2, deploying the newly created binary artifact corresponding to the non-source code project to the test artifact library of the artifact center, and the test artifact library triggers the pipeline;

[0072] S3, the pipeline manages the non-source code project based on the newly created binary product.

[0073] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0074] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0075] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0076] In an exemplary embodiment, the processor may be configured to perform the following steps via a computer program:

[0077] S1, creating a non-source code project according to a non-source code project creation request;

[0078] S2, deploying the newly created binary artifact corresponding to the non-source code project to the test artifact library of the artifact center, and the test artifact library triggers the pipeline;

[0079] S3, the pipeline manages the non-source code project based on the newly created binary product.

[0080] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0081] The following describes in detail the DevOps-based source code-free project management method and system functional architecture design and implementation according to an embodiment of the present invention through exemplary embodiments.

[0082] Figure 7 : is a functional architecture diagram of a DevOps-based source-free project management system according to an embodiment of the present invention, such as Figure 7 As shown in the figure, the DevOps-based non-source code project management and delivery system for traditional industries is based on a microservice architecture and has good business expansion capabilities. It includes a measurement center, a demand center, a pipeline center, a code center, a product center, a release center, and an organization management center. Each part adopts an independent microservice design. The required part can be selected as needed to supplement the existing workflow. The whole provides a complete DevOps service, and for non-source code projects, it provides an overall solution and related module design of a DevOps platform based on a product center series connection.

[0083] Metrics Center: Quantify metrics of all aspects of devops from all angles, provide metrics scoring, and link dashboard visualization management, and provide multi-dimensional observations from different perspectives of the organization, project, and project members.

[0084] Demand Center: Provides efficient team collaboration services for teams, including project management, demand management, configurable agile dashboards, story maps, defect management, demand, code, and artifact association, change set viewing, test management, production management and other functions. It provides drag-and-drop planning and flexible work item tracking, and uses powerful analysis tools and dashboards to obtain and monitor the operation and progress of projects, providing complete project management tools for agile teams and traditional teams.

[0085] Code Center: Provides a code hosting platform based on git and gitlab for team code, including code cloning, viewing, comparison, code branch merging, and code review functions.

[0086] Pipeline Center: Visually display the delivery pipeline to improve delivery quality and efficiency. The pipeline data source can be either a gitlab code repository or a binary product (designed for source code-free projects). The pipeline supports compilation, construction, deployment, unit testing, code scanning, etc. It adopts a plug-in design method and can be connected to various third-party plug-ins. Compilation and construction support virtual machine compilation and container compilation, and support multiple compilation methods such as maven, ant, gradle, etc. Deployment supports virtual machine deployment and container deployment. The unit test plug-in will run the unit test cases in the build task, and you can view unit test reports, unit test coverage, code scanning problem count and other indicators on the platform.

[0087] It should be noted that the functional plug-ins such as compilation, construction, deployment, unit testing, and code scanning are all capabilities of the devops platform itself. In this context, the embodiment of the present invention manages non-source code products based on the product library connecting the entire devops platform in series (for example, the product library nexus integrates Jenkins, triggers the Jenkins pipeline through the hook function, and performs product scanning->testing->deployment), thereby realizing the full-scale connection and management of non-source code projects.

[0088] In an embodiment of the present invention, the following technical means can be used to integrate the product library and the pipeline. The product library uses nexus, and the pipeline is implemented based on jenkins. The overall integration technical means are as follows: jenkins installs plug-ins such as Maven ArtifactChoiceListProvider (Nexus). Whenever a user uploads a new version of a product, the hook function of the product library will trigger the jenkins pipeline. Jenkins will download the product from the product library, and then publish and deploy it through salt and ansible. It should be noted that this example is only for the convenience of further understanding of the solution, but it should not be understood as being implemented only in accordance with this implementation method.

[0089] Organization Management Center: Provides initial configuration of enterprise projects, including project creation, project code library creation or association, team management, process management, authority management, approval configuration and other functions. This center is designed for source-free projects and cancels the strong association between the code library and the project.

[0090] Product Center: Provides a variety of product (jar, war, node, etc.) management solutions, connects the pipeline development test pre-production environment in series, adopts the development test and production sub-library management mode, and provides product promotion function. When the product test passes and meets certain quality access control, the pipeline can promote the test environment products from the test environment product library to the production environment product library for the release center to carry out the corresponding production approval work.

[0091] Release Center: Customized design for traditional industries, it provides diversified release strategies such as canary release and blue-green release for production environments, greatly meeting the strong stability requirements of production environments in traditional industries.

[0092] Figure 8 is a flow chart of DevOps-based non-source code project management according to an embodiment of the present invention, such as Figure 8 As shown in the figure, the DevOps-based source code-free project management process is as follows:

[0093] (1) Create a new "Non-source Code Project" in the Organization Management Center, add project members, and assign roles such as project configuration administrator and project member.

[0094] (2) The project configuration administrator uploads the binary product to the product center of the test environment through the manual interface or command line, triggering the pipeline for deployment and testing in the development and test pre-production environment. Fig. 9 It is a schematic diagram of an artifact center in which a project configuration manager uploads and deploys binary artifacts to a test environment according to an embodiment of the present invention.

[0095] (3) The project configuration administrator configures the pipeline. The general process of the mainstream pipeline is as follows: select the trigger source as the artifact of the project corresponding to the artifact library -> artifact scanning -> multi-environment deployment -> automated testing.

[0096] (4) When the product passes the test and meets a certain quality threshold, the sub-assembly line is triggered. The general process of the sub-assembly line is product promotion, and the product is promoted to the production product library for use by the release center.

[0097] Note: The pipeline described in (3) and (4) can be used multiple times after being configured once. The hook function is automatically called to trigger the main pipeline according to the product version update mechanism.

[0098] (5) The release center approves the product versions and release orders of non-source code projects as needed, and releases them for production as needed. If there are any problems with the production verification, the corresponding version can be rolled back.

[0099] In summary, the pipeline of the embodiment of the present invention supports the product center as a trigger source, and calls the hook function to trigger the pipeline according to the product version change. This solution can be superimposed on the implementation method of the pipeline triggering the source code warehouse in the traditional DevOps system, thereby truly realizing the multi-trigger source of the pipeline, and automatically triggering the pipeline according to the version update of the code warehouse. In addition, based on the DevOps platform, the DevOps modules are connected in series with the product library as the center to manage the passive code products, and the DevOps modules are connected in series with the product center as the core, so that the passive code products can enjoy the full process management, automation capabilities, change management and other capabilities brought by the DevOps system.

[0100] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0101] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A DevOps-based project management method, characterized in that: include: Create a non-source code project according to the non-source code project creation request; Deploy the newly created binary artifact corresponding to the non-source code project to the test artifact library of the artifact center, and the test artifact library triggers the pipeline; Alternatively, when the test artifact library detects that the binary artifact corresponding to the non-source code project is updated, the test artifact library triggers the pipeline; The pipeline includes a main pipeline and a sub-pipeline, and the test product library triggers the pipeline including: the test product library triggers the main pipeline through a hook function; Reading the newly created binary artifact or the updated binary artifact in the test artifact library through a plug-in for reading files in the test artifact library installed in the main pipeline; Scan and read the newly created binary artifact or the updated binary artifact according to the configuration process of the mainstream pipeline; Performing environment deployment verification on the newly created binary product or the updated binary product, wherein the environment deployment verification includes at least one of the following: development environment deployment verification, test environment deployment verification, and pre-production environment deployment verification; Testing the newly created binary artifact or the updated binary artifact; triggering the sub-pipeline when a predetermined condition is met, wherein the predetermined condition includes: the newly created binary artifact or the updated binary artifact passes the test; or the newly created binary artifact or the updated binary artifact passes the test and the test result meets a predetermined quality threshold; According to the configuration process of the sub-pipeline, the newly created binary artifact or the updated binary artifact is promoted to the production artifact library of the artifact center.

2. The method according to claim 1, characterized in that After the newly created binary product or the updated binary product is promoted to the production product library of the product center according to the configuration process of the sub-pipeline, the method further includes: The publishing center verifies the non-source code project and the binary product corresponding to the non-source code project in the production product library; If the verification is passed, the non-source code project is released; If the verification fails, a version rollback is performed on the binary artifact in the production artifact library and / or the test artifact library.

3. The method according to claim 1, characterized in that Creating a non-source code project based on a non-source code project creation request includes: According to the request for creating the non-source code project, the non-source code project is created in the organization management center, and configuration of project information of the non-source code project is accepted.

4. The method according to claim 3, characterized in that The project information of the non-source code project includes at least one of the following: project members, roles of the project members, and configuration flow of the pipeline.

5. A DevOps-based project management device, characterized in that: For executing the method as claimed in any one of claims 1 to 4, comprising: The organization management center is used to create non-source code projects based on non-source code project creation requests; A product center, including a test product library, wherein the test product library is used to store newly created binary products corresponding to the non-source code project and trigger the pipeline; or, when it is detected that the binary product corresponding to the non-source code project is updated, trigger the pipeline; The pipeline is used to manage the source-free project based on the newly created binary product; or, is used to manage the source-free project based on the updated binary product.

6. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 4 when executed.

Images