Research and development delivery method and device, computer program product and development platform

Abstract

The invention provides a research and development delivery method and device, a computer program product and a development platform, and the method comprises the steps that a demand module obtains a business demand, the business demand is divided into at least one task, and the task is a procedural work for completing the business demand; the demand module establishes a workflow state flow diagram for the task; the demand module configures a trigger strategy for the workflow state of the workflow state flow diagram, so that a corresponding assembly line task is triggered when the workflow state is turned to; under the condition that the continuous delivery module completes the assembly line task corresponding to the workflow state, the demand module triggers the workflow state of the workflow state flow diagram to flow to the corresponding next workflow state until the workflow state flows to the last workflow state to complete the task; under the condition that the continuous delivery module completes all the tasks, the demand module obtains the media released by the tasks to complete delivery, and the problem that automatic delivery is difficult to achieve in research and development in the prior art is solved.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to a research and development delivery method, device, computer-readable storage medium, computer program product and development platform. Background Art

[0002] At present, each stage of the DevOps development process is usually supported by a variety of different tool chains. Users use corresponding tools to perform related functions and measure data statistics at different development stages. This approach has the following shortcomings:

[0003] (1) At different R&D stages, operations and statistical data need to be performed in corresponding tools respectively. Users can only automate local R&D processes. There is a lack of correlation between tools, which leads to high manual costs in the overall R&D process. The degree of automation in the overall R&D process needs to be improved.

[0004] (2) Users can only view local data in each DevOps tool. The measurement data statistics are relatively scattered, and information is difficult to communicate. There is a lack of global measurement data statistics and visualization for the entire R&D process.

[0005] It can be seen that the traditional DevOps tool chain usage model can only realize the automated operation and statistical display of measurement data in local R&D processes. There is a lack of connection between different tools, and it is impossible to realize the automated execution of the entire R&D process and the overall measurement data statistics and visualization display. Summary of the invention

[0006] The main purpose of this application is to provide a method, device, computer-readable storage medium, computer program product and development platform for delivering R&D, so as to at least solve the problem that it is difficult to achieve automated delivery of R&D in the prior art.

[0007] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a research and development delivery method is provided, including: a demand module obtains business requirements, splits the business requirements into at least one task, and the task is a procedural work to complete the business requirements; the demand module establishes a workflow state flow diagram for the task, and the workflow state flow diagram is a flowchart of the flow between workflow states, and the workflow states include start, development, test and completion; the demand module configures a trigger strategy for the workflow state of the workflow state flow diagram, so that when it flows to the workflow state, the pipeline task corresponding to the trigger strategy is triggered, and the pipeline task needs to complete multiple subtasks in sequence to complete the task; when the continuous delivery module completes the pipeline task corresponding to the workflow state, the demand module triggers the workflow state of the workflow state flow diagram to flow to the corresponding next workflow state until it flows to the last workflow state to complete the task; when the continuous delivery module completes all the tasks, the demand module obtains the media released by each task to complete the delivery.

[0008] Optionally, after the requirement module splits the business requirement into at least one task, the method further includes: generating test data according to the business requirement, the test data including a test plan, test cases and defects; establishing an association between the test data and the task so that a group of the test data corresponds to one task.

[0009] Optionally, after the requirement module configures a trigger strategy for the workflow state of the workflow state flow diagram so that the pipeline task corresponding to the trigger strategy is triggered when the workflow state is transferred to the workflow state, the method further includes: when the workflow state of the workflow state flow diagram flows to the test, sending the test data associated with the task to the pipeline task triggered by the trigger strategy corresponding to the test to complete the test.

[0010] Optionally, a trigger strategy is configured for the workflow state of the workflow state flow diagram of the requirement module, so that the pipeline task corresponding to the trigger strategy is triggered when the flow reaches the workflow state, including: when the current workflow state of the workflow state flow diagram triggers the corresponding pipeline task, the task information of the task is sent to the corresponding pipeline task, and the task information includes task ID, responsible person and media version information.

[0011] Optionally, when the continuous delivery module completes the pipeline task corresponding to the workflow state, the requirement module triggers the workflow state of the workflow state flow diagram to flow to the corresponding next workflow state, and the method further includes: passing the process data of the pipeline task to the requirement module, the requirement module is used to query the progress of the task, and the process data includes code, test report and medium; in response to the query request, the requirement module displays the task, the code, the test report, the medium, the test data and the deployment environment associated with the business requirement.

[0012] Optionally, when the continuous delivery module completes the pipeline task corresponding to the workflow state, after the requirement module triggers the workflow state flow of the workflow state flow diagram to transfer to the corresponding next workflow state, the method further includes: in response to a query request, the continuous delivery module displays the metadata of the medium delivered by the task.

[0013] According to another aspect of the present application, a developed delivery device is provided, comprising: an acquisition unit, used for a demand module to acquire business requirements, split the business requirements into at least one task, and the task is a procedural work to complete the business requirements; a first establishment unit, used for the demand module to establish a workflow state flow diagram for the task, the workflow state flow diagram is a flowchart of the flow between workflow states, and the workflow states include start, development, test and completion; a configuration unit, used for the demand module to configure a trigger policy for the workflow state of the workflow state flow diagram, so that when the flow is transferred to the workflow state, the pipeline task corresponding to the trigger policy is triggered, and the pipeline task needs to complete multiple subtasks in sequence to complete the task; a flow unit, used for, when the continuous delivery module completes the pipeline task corresponding to the workflow state, the demand module triggers the workflow state of the workflow state flow diagram to flow to the corresponding next workflow state, until the task is completed by transferring to the last workflow state; a delivery unit, used for, when the continuous delivery module completes all the tasks, the demand module obtains the medium released by each task to complete the delivery.

[0014] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute any one of the methods described.

[0015] According to another aspect of the present application, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, any one of the methods described above is implemented.

[0016] According to another aspect of the present application, a development platform is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include means for executing any one of the methods described.

[0017] Applying the technical solution of the present application, in the above-developed delivery method, first, the demand module obtains the business demand, splits the above-mentioned business demand into at least one task, and the above-mentioned task is the procedural work to complete the above-mentioned business demand; the above-mentioned demand module establishes a workflow state flow diagram for the above-mentioned task, and the above-mentioned workflow state flow diagram is a flowchart of the flow between workflow states, and the above-mentioned workflow states include start, development, test and completion; the above-mentioned demand module configures a trigger strategy for the above-mentioned workflow state of the above-mentioned workflow state flow diagram, so that when it flows to the above-mentioned workflow state, the pipeline task corresponding to the above-mentioned trigger strategy is triggered, and the above-mentioned pipeline task needs to complete multiple subtasks in sequence to complete the above-mentioned task; when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned demand module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram. Flow to the corresponding next workflow state until it flows to the last workflow state to complete the above task; when the above continuous delivery module completes all the above tasks, the above demand module obtains the media released by each of the above tasks to complete the delivery. The method can establish a workflow state flow diagram according to the type of each task by splitting the business requirements into at least one task to complete the business requirements. For example, the workflow states of the test task include start, test and completion. Some workflow states need to be configured with a trigger strategy to trigger the corresponding pipeline task. For example, the test state triggers the subtasks of multiple test items to form a pipeline task. The continuous delivery module can be used to complete the pipeline task and deliver the task. After all tasks are completed, the corresponding media can be delivered to achieve automated delivery, which solves the problem that it is difficult to achieve automated delivery in research and development in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A hardware structure block diagram of a mobile terminal for executing a research and development delivery method provided in an embodiment of the present application is shown;

[0019] Figure 2 A schematic diagram of a process flow of a research and development delivery method provided according to an embodiment of the present application is shown;

[0020] Figure 3 A schematic flow chart of another delivery method developed according to an embodiment of the present application is shown;

[0021] Figure 4A structural block diagram of a delivery device developed according to an embodiment of the present application is shown.

[0022] The above drawings include the following reference numerals:

[0023] 102, processor; 104, memory; 106, transmission device; 108, input and output devices. DETAILED DESCRIPTION

[0024] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0025] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] For the convenience of description, some nouns or terms involved in the embodiments of the present application are explained below:

[0028] Post-event: an event that is executed after the current operation is completed. For example, a pipeline post-event refers to an event that is automatically executed after the pipeline task is completed.

[0029] Task ID: The ID that uniquely identifies a task in the requirements module.

[0030] As introduced in the background technology, it is difficult to achieve automated delivery of R&D in the prior art. To solve this technical problem, the embodiments of the present application provide a method, device, computer-readable storage medium, computer program product and development platform for delivering R&D.

[0031] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0032] 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 mobile terminal as an example, Figure 1 FIG. 1 is a hardware structure block diagram of a mobile terminal of a delivery method developed in an embodiment of the present invention. Figure 1 As shown, the mobile terminal may include one or more ( Figure 1 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the mobile terminal may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is for illustration only and does not limit the structure of the mobile terminal. Figure 1 More or less media as shown, or with Figure 1 Different configurations are shown.

[0033] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the delivery method developed in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, the above method is implemented. The memory 104 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 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories can be connected to the mobile terminal 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. The transmission device 106 is used to receive or send data via a network. The above-mentioned specific network example may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0034] In this embodiment, a delivery method for research and development running on a mobile terminal, a computer terminal or a similar computing device is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0035] Figure 2 is a flow chart of a delivery method according to an embodiment of the present application. Figure 2 As shown, the method comprises the following steps:

[0036] Step S201, the demand module obtains business requirements and divides the business requirements into at least one task, where the task is a procedural work to complete the business requirements;

[0037] Step S202, the demand module creates a workflow state flow diagram for the task, where the workflow state flow diagram is a flow chart of flows between workflow states, where the workflow states include start, development, test, and completion;

[0038] Step S203, the demand module configures a trigger strategy for the workflow state of the workflow state flow diagram, so that when the workflow state is transferred to the workflow state, the pipeline task corresponding to the trigger strategy is triggered, and the pipeline task needs to complete multiple subtasks in sequence to complete the task;

[0039] Step S204, when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned demand module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram to flow to the corresponding next above-mentioned workflow state, until it flows to the last above-mentioned workflow state to complete the above-mentioned task;

[0040] Step S205: When the continuous delivery module completes all the tasks, the demand module obtains the media published by each task to complete the delivery.

[0041] In the above-mentioned R&D delivery method, first, the demand module obtains the business demand and splits the above-mentioned business demand into at least one task, and the above-mentioned task is the procedural work to complete the above-mentioned business demand; the above-mentioned demand module establishes a workflow state flow diagram for the above-mentioned task, and the above-mentioned workflow state flow diagram is a flowchart of the flow between workflow states, and the above-mentioned workflow states include start, development, test and completion; the above-mentioned demand module configures a trigger strategy for the above-mentioned workflow state of the above-mentioned workflow state flow diagram, so that when it flows to the above-mentioned workflow state, the pipeline task corresponding to the above-mentioned trigger strategy is triggered, and the above-mentioned pipeline task needs to complete multiple subtasks in sequence to complete the above-mentioned task; when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned demand module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram to flow to the corresponding The method divides the business requirements into at least one task that completes the business requirements, and then establishes a workflow state flow diagram according to the type of each task. For example, the workflow states of the test task include start, test and completion. Some workflow states need to be configured with a trigger strategy to trigger the corresponding pipeline task. For example, the test state triggers the subtasks of multiple test items to form a pipeline task, and the continuous delivery module can be used to complete the pipeline task and deliver the task. After all the tasks are completed, the corresponding media can be delivered to achieve automated delivery, which solves the problem that it is difficult to achieve automated delivery in research and development in the prior art.

[0042] In order to implement automatic testing, in an optional implementation manner, after the requirement module splits the business requirement into at least one task, the method further includes:

[0043] Step S301, generating test data according to the above business requirements, the above test data including test plans, test cases and defects;

[0044] Step S302: establishing an association relationship between the test data and the task, so that one group of the test data corresponds to one task.

[0045] In the above implementation, the requirement module includes a test tool, in which a test plan is formulated according to business requirements and test cases and defects are added, and are associated with corresponding tasks of the requirement module to facilitate calling of test data for automatic testing.

[0046] In order to realize automatic testing, in an optional implementation manner, after the requirement module configures a trigger strategy for the workflow state of the workflow state flow diagram so that the pipeline task corresponding to the trigger strategy is triggered when the workflow state is transferred to the workflow state, the method further includes:

[0047] Step S401, when the workflow state of the workflow state flow diagram is transferred to the test, the test data associated with the task is sent to the pipeline task triggered by the trigger policy corresponding to the test to complete the test.

[0048] In the above implementation, when the workflow state is transferred to the test, the test pipeline task is triggered and the test data is called to perform automated testing.

[0049] In order to realize the workflow state transfer, in an optional implementation, a trigger strategy is configured for the workflow state of the workflow state transfer diagram of the requirement module, so that when the workflow state is transferred to the workflow state, the pipeline task corresponding to the trigger strategy is triggered, including:

[0050] Step S501, when the current workflow state of the workflow state flow diagram triggers the corresponding pipeline task, the task information of the task is sent to the corresponding pipeline task, and the task information includes task ID, responsible person and media version information.

[0051] In the above implementation, the corresponding pipeline automatic triggering method of the continuous delivery module is bound to the corresponding workflow state. After automatic triggering, the demand data is automatically associated and written into the corresponding pipeline task result. The pipeline post-event is configured according to the usage scenario. That is, after the pipeline is executed, the relevant tasks of the demand module are triggered to automatically flow to the specified state, and the data in the continuous delivery module is written back to the demand module.

[0052] In order to facilitate the progress checking, in an optional implementation, when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned requirement module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram to flow to the corresponding next above-mentioned workflow state, and the above-mentioned method further includes:

[0053] Step S601, transferring the process data of the above-mentioned pipeline task to the demand module, the above-mentioned demand module is used to query the progress of the above-mentioned task, the above-mentioned process data includes code, test report and medium;

[0054] Step S602: In response to the query request, the requirement module displays the task, the code, the test report, the medium, the test data and the deployment environment associated with the business requirement.

[0055] In the above implementation, the progress of task completion is determined according to the workflow state flow diagram, and the subtasks of the task can also be checked to see whether they have been completed. The process data in the continuous delivery module is written back to the requirement module, and the above tasks, the above codes, the above test reports, the above media, the above test data, the deployment environment and other information associated with the above business requirements can be displayed.

[0056] In order to facilitate traceability, in an optional implementation, when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned requirement module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram to flow to the corresponding next above-mentioned workflow state, and the above-mentioned method further includes:

[0057] Step S701: In response to a query request, the continuous delivery module displays metadata of the medium delivered by the task.

[0058] In the above implementation, two-way data tracking is achieved from the requirement management tool and the media management tool, that is, it is possible to view in the requirement module which tasks, codes, test reports, media, test and deployment environment information and other information are associated with the current requirement, and it is also possible to view on the media side which requirements, tasks, codes, test reports, test and deployment environment information and other information are associated with a certain medium, so that the entire traceability process can be seen.

[0059] In order to enable those skilled in the art to more clearly understand the technical solution of the present application, the implementation process of the delivery method developed by the present application will be described in detail below in conjunction with specific embodiments.

[0060] This embodiment relates to a specific R&D delivery method, such as Figure 3 As shown, the following steps are included:

[0061] For the structure and process description of the above system and method, Figure 3 As shown, the task module uses the Jira tool, the code module uses the GitLab tool, and the construction module uses the Jenkins tool as an example.

[0062] First, split the requirements according to business needs, split the requirements into different tasks and subtasks for management and distribution, and distribute the corresponding types of tasks to relevant personnel. Each task type has a corresponding workflow state flow. For example, in the Jira task management tool, requirements can be split into epics, stories, tasks, requirement subtasks, development subtasks, test subtasks, defects and other types, and distributed to corresponding requirements, development, testing and other personnel. Epics, stories, tasks and subtasks are split at multiple levels, and iteration plans are made for subtasks. The subtask types are determined to generate a workflow state flow diagram, such as Figure 3As shown, you can also formulate management strategies such as test plans and test cases according to business needs and associate them with corresponding tasks. In addition, you can bind the corresponding pipeline name to the corresponding task status for triggering.

[0063] The second step is to configure the continuous delivery module, manage the code and branches in GitLab, bind the corresponding requirement ID when submitting the local branch code, and add the Jira task ID in the commit message to bind the relationship between the task and the code. Configure atomic tasks such as code, build, component release, deployment, and testing in the Jenkins pipeline, and configure the pipeline post-event according to the usage scenario, that is, after the pipeline is executed, a task with a specified ID in Jira is triggered to automatically flow to the specified state.

[0064] After the configuration of the requirements module and the continuous delivery module is completed, when the user changes the task status in Jira according to the task progress, if the pipeline trigger event is configured, the pipeline task of the corresponding name will be automatically triggered, and the task ID, responsible person, iteration or version information in the Jira task and other data will be transferred to the continuous delivery module for storage. During the execution of the pipeline, the system collects information such as code repository, branch name, version number, build status, test status, media name and storage address, and transfers the generated media to the media module for storage management. After the pipeline is executed, if the post-event is configured, such as configuring the corresponding task ID to flow to the "closed" state, the corresponding task ID will be automatically closed, and the pipeline process data will be transferred to Jira for storage.

[0065] Through the two-way trigger configuration and data feedback of the requirements module and the continuous delivery module, automated delivery and two-way data tracking can be achieved at the same time. In terms of data tracking, users can view the progress of current requirements from the requirements module, such as the corresponding task development progress, test quality, media storage, online release, etc. in Jira. At the same time, they can also view the metadata of the currently delivered media from the continuous delivery module, that is, the metadata information such as the requirements, code branches, quality and test reports of the current online media. The media can be components. In terms of automated delivery, the two-way trigger mechanism is used to improve the automation level between different tools.

[0066] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0067] The embodiments of the present application also provide a delivery device for research and development. It should be noted that the delivery device for research and development of the embodiments of the present application can be used to execute the delivery method for research and development provided by the embodiments of the present application. The device 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 for 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 conceived.

[0068] The following is an introduction to the delivery device developed and provided in the embodiments of the present application.

[0069] Figure 4 is a structural block diagram of a delivery device developed according to an embodiment of the present application. Figure 4 As shown, the device comprises:

[0070] An acquisition unit 10 is used for the demand module to acquire business requirements and split the business requirements into at least one task, where the task is a procedural work to complete the business requirements;

[0071] A first establishing unit 20 is used for the requirement module to establish a workflow state flow diagram for the task, wherein the workflow state flow diagram is a flow chart of the flow between workflow states, and the workflow states include start, development, test and completion;

[0072] A configuration unit 30 is used for the above-mentioned requirement module to configure a trigger strategy for the above-mentioned workflow state of the above-mentioned workflow state flow diagram, so that when the workflow state is transferred to the above-mentioned workflow state, the pipeline task corresponding to the above-mentioned trigger strategy is triggered, and the above-mentioned pipeline task needs to complete multiple subtasks in sequence to complete the above-mentioned task;

[0073] The flow unit 40 is used for triggering the workflow state of the workflow state flow diagram to flow to the corresponding next workflow state when the continuous delivery module completes the pipeline task corresponding to the workflow state, until the task is completed after the workflow state is transferred to the last workflow state;

[0074] The delivery unit 50 is used for the demand module to obtain the media published by each of the tasks to complete the delivery when the continuous delivery module completes all of the tasks.

[0075] In the delivery device developed above, by splitting business requirements into at least one task to complete the business requirements, a workflow state flow diagram can be established according to the type of each task. For example, the workflow states of the test task include start, test and completion. Some workflow states need to be configured with a trigger strategy to trigger the corresponding pipeline task. For example, the test state triggers the sub-tasks of multiple test items to form a pipeline task. The pipeline task can be completed and the task delivered through the continuous delivery module. After all tasks are completed, the corresponding media can be delivered to achieve automated delivery, which solves the problem that it is difficult to achieve automated delivery in research and development in the prior art.

[0076] In order to realize automatic testing, in an optional implementation manner, the above-mentioned device further includes:

[0077] A generating unit, configured to generate test data according to the business requirement after the requirement module divides the business requirement into at least one task, wherein the test data includes a test plan, test cases and defects;

[0078] The second establishing unit is used to establish an association relationship between the test data and the task, so that a group of the test data corresponds to one task.

[0079] In the above implementation, the requirement module includes a test tool, in which a test plan is formulated according to business requirements and test cases and defects are added, and are associated with corresponding tasks of the requirement module to facilitate calling of test data for automatic testing.

[0080] In order to realize automatic testing, in an optional implementation manner, the above-mentioned device further includes:

[0081] A first sending unit is used to configure a trigger strategy for the workflow state of the workflow state flow diagram in the requirement module, so that after the pipeline task corresponding to the trigger strategy is triggered when the workflow state is transferred to the workflow state, when the workflow state of the workflow state flow diagram flows to the test, the test data associated with the task is sent to the pipeline task triggered by the trigger strategy corresponding to the test to complete the test.

[0082] In the above implementation, when the workflow state is transferred to the test, the pipeline task of the test is triggered and the test data is called to perform the automated test.

[0083] In order to realize the workflow state transfer, in an optional implementation manner, the configuration unit includes:

[0084] The second sending unit is used to send the task information of the task to the corresponding pipeline task when the current workflow state of the workflow state flow diagram triggers the corresponding pipeline task, and the task information includes task ID, responsible person and media version information.

[0085] In the above implementation, the corresponding pipeline automatic triggering method of the continuous delivery module is bound to the corresponding workflow state. After automatic triggering, the demand data is automatically associated and written into the corresponding pipeline task result. The pipeline post-event is configured according to the usage scenario. That is, after the pipeline is executed, the relevant tasks of the demand module are triggered to automatically flow to the specified state, and the data in the continuous delivery module is written back to the demand module.

[0086] In order to facilitate checking the progress, in an optional implementation manner, the above device further includes:

[0087] A third sending unit is used for transmitting the process data of the above-mentioned pipeline task to the requirement module after the above-mentioned workflow state of the above-mentioned workflow state flow diagram is transferred to the corresponding next workflow state when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, and the above-mentioned requirement module is used to query the progress of the above-mentioned task, and the above-mentioned process data includes code, test report and medium;

[0088] The first query unit is used to respond to the query request, and the requirement module displays the task, the code, the test report, the medium, the test data and the deployment environment associated with the business requirement.

[0089] In the above implementation, the progress of task completion is determined according to the workflow state flow diagram, and the subtasks of the task can also be checked to see whether they have been completed. The process data in the continuous delivery module is written back to the requirement module, and the above tasks, the above codes, the above test reports, the above media, the above test data, the deployment environment and other information associated with the above business requirements can be displayed.

[0090] In order to facilitate traceability, in an optional implementation, when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned requirement module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram to flow to the corresponding next above-mentioned workflow state, and the above-mentioned method further includes:

[0091] The second query unit is used to respond to the query request, and the continuous delivery module displays the metadata of the medium delivered by the task.

[0092] In the above implementation, two-way data tracking is achieved from the requirement management tool and the media management tool, that is, it is possible to view in the requirement module which tasks, codes, test reports, media, test and deployment environment information and other information are associated with the current requirement, and it is also possible to view on the media side which requirements, tasks, codes, test reports, test and deployment environment information and other information are associated with a certain medium, so that the entire traceability process can be seen.

[0093] The above-mentioned delivery device includes a processor and a memory. The above-mentioned units are stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize the corresponding functions. The above-mentioned modules are all located in the same processor; or, the above-mentioned modules are located in different processors in any combination.

[0094] The processor includes a kernel, which calls the corresponding program unit from the memory. One or more kernels can be set, and the problem of R&D being difficult to achieve automated delivery in the existing technology can be solved by adjusting kernel parameters.

[0095] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0096] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the delivery method developed above.

[0097] Specifically, the delivery methods of R&D include:

[0098] Step S201, the demand module obtains business requirements and divides the business requirements into at least one task, where the task is a procedural work to complete the business requirements;

[0099] Step S202, the demand module creates a workflow state flow diagram for the task, where the workflow state flow diagram is a flow chart of flows between workflow states, where the workflow states include start, development, test, and completion;

[0100] Step S203, the demand module configures a trigger strategy for the workflow state of the workflow state flow diagram, so that when the workflow state is transferred to the workflow state, the pipeline task corresponding to the trigger strategy is triggered, and the pipeline task needs to complete multiple subtasks in sequence to complete the task;

[0101] Step S204, when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned demand module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram to flow to the corresponding next above-mentioned workflow state, until it flows to the last above-mentioned workflow state to complete the above-mentioned task;

[0102] Step S205: When the continuous delivery module completes all the tasks, the demand module obtains the media published by each task to complete the delivery.

[0103] An embodiment of the present invention provides a processor, and the processor is used to run a program, wherein the above-developed delivery method is executed when the above-mentioned program is run.

[0104] Specifically, the delivery methods of R&D include:

[0105] Step S201, the demand module obtains business requirements and divides the business requirements into at least one task, where the task is a procedural work to complete the business requirements;

[0106] Step S202, the demand module creates a workflow state flow diagram for the task, where the workflow state flow diagram is a flow chart of flows between workflow states, where the workflow states include start, development, test, and completion;

[0107] Step S203, the demand module configures a trigger strategy for the workflow state of the workflow state flow diagram, so that when the workflow state is transferred to the workflow state, the pipeline task corresponding to the trigger strategy is triggered, and the pipeline task needs to complete multiple subtasks in sequence to complete the task;

[0108] Step S204, when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned demand module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram to flow to the corresponding next above-mentioned workflow state, until it flows to the last above-mentioned workflow state to complete the above-mentioned task;

[0109] Step S205: When the continuous delivery module completes all the tasks, the demand module obtains the media published by each task to complete the delivery.

[0110] An embodiment of the present invention provides a development platform, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, at least the following steps are implemented:

[0111] Step S201, the demand module obtains business requirements and divides the business requirements into at least one task, where the task is a procedural work to complete the business requirements;

[0112] Step S202, the demand module creates a workflow state flow diagram for the task, where the workflow state flow diagram is a flow chart of flows between workflow states, where the workflow states include start, development, test, and completion;

[0113] Step S203, the demand module configures a trigger strategy for the workflow state of the workflow state flow diagram, so that when the workflow state is transferred to the workflow state, the pipeline task corresponding to the trigger strategy is triggered, and the pipeline task needs to complete multiple subtasks in sequence to complete the task;

[0114] Step S204, when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned demand module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram to flow to the corresponding next above-mentioned workflow state, until it flows to the last above-mentioned workflow state to complete the above-mentioned task;

[0115] Step S205: When the continuous delivery module completes all the tasks, the demand module obtains the media published by each task to complete the delivery.

[0116] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program for initializing at least the following method steps:

[0117] Step S201, the demand module obtains business requirements and divides the business requirements into at least one task, where the task is a procedural work to complete the business requirements;

[0118] Step S202, the demand module creates a workflow state flow diagram for the task, where the workflow state flow diagram is a flow chart of flows between workflow states, where the workflow states include start, development, test, and completion;

[0119] Step S203, the demand module configures a trigger strategy for the workflow state of the workflow state flow diagram, so that when the workflow state is transferred to the workflow state, the pipeline task corresponding to the trigger strategy is triggered, and the pipeline task needs to complete multiple subtasks in sequence to complete the task;

[0120] Step S204, when the continuous delivery module completes the above-mentioned pipeline task corresponding to the above-mentioned workflow state, the above-mentioned demand module triggers the above-mentioned workflow state of the above-mentioned workflow state flow diagram to flow to the corresponding next above-mentioned workflow state, until it flows to the last above-mentioned workflow state to complete the above-mentioned task;

[0121] Step S205: When the continuous delivery module completes all the tasks, the demand module obtains the media published by each task to complete the delivery.

[0122] 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.

[0123] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0124] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0125] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0126] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0127] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0128] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0129] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0130] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0131] From the above description, it can be seen that the above embodiments of the present application achieve the following technical effects:

[0132] 1) In the delivery method of the research and development of the present application, first, the demand module obtains the business demand and splits the above business demand into at least one task, and the above task is the procedural work to complete the above business demand; the above demand module establishes a workflow state flow diagram for the above task, and the above workflow state flow diagram is a flowchart of the flow between workflow states, and the above workflow states include start, development, test and completion; the above demand module configures a trigger strategy for the above workflow state of the above workflow state flow diagram, so that when it flows to the above workflow state, the pipeline task corresponding to the above trigger strategy is triggered, and the above pipeline task needs to complete multiple subtasks in sequence to complete the above task; when the continuous delivery module completes the above pipeline task corresponding to the above workflow state, the above demand module triggers the above workflow state of the above workflow state flow diagram to flow to The corresponding next workflow state is formed until it flows to the last workflow state to complete the task. When the continuous delivery module completes all the tasks, the demand module obtains the media released by each of the tasks to complete the delivery. The method can establish a workflow state flow diagram according to the type of each task by splitting the business requirements into at least one task to complete the business requirements. For example, the workflow states of the test task include start, test and completion. Some workflow states need to be configured with a trigger strategy to trigger the corresponding pipeline task. For example, the test state triggers the subtasks of multiple test items to form a pipeline task. The continuous delivery module can be used to complete the pipeline task and deliver the task. After all the tasks are completed, the corresponding media can be delivered to achieve automated delivery, which solves the problem that it is difficult to achieve automated delivery in research and development in the prior art.

[0133] 2) In the delivery device developed by the present application, by splitting the business requirements into at least one task to complete the business requirements, a workflow state flow diagram can be established according to the type of each task. For example, the workflow states of the test task include start, test and completion. Some workflow states need to be configured with a trigger strategy to trigger the corresponding pipeline task. For example, the test state triggers the sub-tasks of multiple test items to form a pipeline task. The pipeline task can be completed and the task delivered through the continuous delivery module. After all tasks are completed, the corresponding media can be delivered to achieve automated delivery, which solves the problem that it is difficult to achieve automated delivery in research and development in the prior art.

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

Claims

1. A delivery method for research and development, characterized in that: include: The demand module obtains business requirements and divides the business requirements into at least one task, where the task is a procedural work to complete the business requirements; The requirement module establishes a workflow state flow diagram for the task, wherein the workflow state flow diagram is a flow chart of the flow between workflow states, and the workflow states include start, development, test and completion; The demand module configures a trigger strategy for the workflow state of the workflow state flow diagram, so that when the workflow state is transferred to the workflow state, the pipeline task corresponding to the trigger strategy is triggered, and the pipeline task needs to complete multiple subtasks in sequence to complete the task; When the continuous delivery module completes the pipeline task corresponding to the workflow state, the demand module triggers the workflow state of the workflow state flow diagram to flow to the corresponding next workflow state until it flows to the last workflow state to complete the task; When the continuous delivery module completes all the tasks, the demand module obtains the media published by each task to complete the delivery.

2. The method according to claim 1, characterized in that: After the demand module divides the business demand into at least one task, the method further includes: Generate test data according to the business requirements, the test data including test plans, test cases and defects; An association relationship is established between the test data and the task, so that a group of the test data corresponds to one task.

3. The method according to claim 2, characterized in that After the requirement module configures a trigger strategy for the workflow state of the workflow state flow diagram so that the pipeline task corresponding to the trigger strategy is triggered when the workflow state is transferred to the workflow state, the method further includes: When the workflow state of the workflow state flow diagram is transferred to the test, the test data associated with the task is sent to the pipeline task triggered by the trigger policy corresponding to the test to complete the test.

4. The method according to claim 1, characterized in that: Configuring a trigger strategy for the workflow state of the workflow state flow diagram of the demand module so that a pipeline task corresponding to the trigger strategy is triggered when the workflow state is transferred to the workflow state, including: When the current workflow state of the workflow state flow diagram triggers the corresponding pipeline task, the task information of the task is sent to the corresponding pipeline task, and the task information includes task ID, responsible person and media version information.

5. The method according to claim 2, characterized in that: When the continuous delivery module completes the pipeline task corresponding to the workflow state, after the requirement module triggers the workflow state of the workflow state flow diagram to flow to the corresponding next workflow state, the method further includes: The process data of the pipeline task is transferred to the demand module, and the demand module is used to query the progress of the task, wherein the process data includes code, test report and medium; In response to the query request, the requirement module displays the task, the code, the test report, the medium, the test data and the deployment environment associated with the business requirement.

6. The method according to claim 1, characterized in that When the continuous delivery module completes the pipeline task corresponding to the workflow state, after the requirement module triggers the workflow state of the workflow state flow diagram to flow to the corresponding next workflow state, the method further includes: In response to a query request, the continuous delivery module displays metadata of the medium delivered by the task.

7. A delivery device developed, characterized in that: include: An acquisition unit, used for the demand module to acquire business requirements and split the business requirements into at least one task, where the task is a procedural work to complete the business requirements; A first establishing unit is used for the requirement module to establish a workflow state flow diagram for the task, wherein the workflow state flow diagram is a flow chart of the flow between workflow states, and the workflow states include start, development, test and completion; A configuration unit, configured for the requirement module to configure a trigger strategy for the workflow state of the workflow state flow diagram, so that when the workflow state is transferred to the workflow state, a pipeline task corresponding to the trigger strategy is triggered, and the pipeline task needs to complete multiple subtasks in sequence to complete the task; A transfer unit, configured to trigger the workflow state of the workflow state transfer diagram to transfer to the corresponding next workflow state by the demand module when the continuous delivery module completes the pipeline task corresponding to the workflow state, until the task is completed by transferring to the last workflow state; The delivery unit is used for, when the continuous delivery module completes all the tasks, the demand module obtains the media published by each task to complete the delivery.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 6.

9. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

10. A development platform, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include methods for executing any one of claims 1 to 6.

Images