CN117193794A - Management method, equipment and medium for software research and development project - Google Patents

Abstract

The invention discloses a management method, equipment and medium for software research and development projects, which belongs to the technical field of software research and development project management and is used to solve the technical problem that existing task item updating methods are prone to untimely and inaccurate updates. The method includes: in response to the development code corresponding to the task item being submitted to the code warehouse, triggering the pipeline to perform continuous integration of the development code; checking the task item status corresponding to the task item; when the task item status is not processing, Update the task item status and task item update content; after the continuous integration of the development code is completed, trigger the pipeline to perform continuous deployment of the development code; check the task item status corresponding to the task item; in the task item When the status is not completed, update the task item status and task item update content. This application achieves timely and accurate updates of task items through the above solution.

Description

A management method, equipment and medium for software research and development projects

Technical field

This application relates to the technical field of software R&D project management, and in particular to a management method, equipment and medium for software R&D projects.

Background technique

In software R&D projects, the project manager formulates task items based on the collected requirements. Developers need to develop according to the contents of the task items. After the development is completed, it is managed through the development and operation platform, such as source code management, product management, and continuous integration. , automated testing, continuous deployment, etc.

While developing the operation and maintenance platform for development work, developers also need to enter the software R&D project management function module to update task items. This requires separate operations on different functional modules, which increases the workload of developers and increases the workload of developers. Manually updating task items can easily lead to inconsistencies between the actual development progress and the task progress in the software R&D project management function module, causing the problem of untimely and inaccurate task item updates, thus affecting project progress tracking and adjustment.

Contents of the invention

Embodiments of the present application provide a management method, equipment and media for software research and development projects, which are used to solve the following technical problems: existing task item updating methods are prone to untimely and inaccurate updates.

The embodiments of this application adopt the following technical solutions:

In the first aspect, embodiments of the present application provide a management method for software research and development projects. The method includes: in response to submitting the development code corresponding to the task item to the code warehouse, triggering the pipeline to perform continuous integration of the development code; checking all The task item status corresponding to the task item; when the task item status is not processing, update the task item status and task item update content; after the continuous integration of the development code is completed, trigger the pipeline to perform the development Continuous deployment of code; check the task item status corresponding to the task item; when the task item status is not completed, update the task item status and task item update content.

In one or more embodiments of the present application, before the development code corresponding to the task item is submitted to the code warehouse, the method further includes: configuring a minimum work item in the software research and development project management function module, and the minimum work item is Configured as a task item, the task item is used to disassemble the development requirements; configure the task item status corresponding to the task item, and the task item status at least includes: pending, processing, and completed.

In one or more embodiments of the present application, for the continuous integration, the triggering mode of the pipeline is automatic triggering; for the continuous deployment, the triggering mode of the pipeline is automatic triggering or manual triggering.

In one or more embodiments of this application, the continuous integration stage includes: code compilation, which compiles the development code; automated testing, which uses automated testing tools to perform unit testing on the development code; static Code analysis, using static code analysis tools to statically analyze the development code; product upload, uploading the compiled code files to the product warehouse; image making, making docker images and uploading them to the image warehouse; image deployment, in use Deploy the docker image in the test K8S environment.

In one or more embodiments of the present application, the order of the stages of code compilation, image creation, and image deployment cannot be changed.

In one or more embodiments of this application, the continuous deployment stage includes: code compilation, which compiles the development code; automated testing, which uses automated testing tools to perform unit testing on the development code; static Code analysis, using static code analysis tools to statically analyze the development code; product upload, uploading the compiled code files to the product warehouse; image making, making docker images and uploading them to the image warehouse; image deployment, in use Deploying the docker image in the production K8S environment; automated monitoring, using automated monitoring tools to monitor the deployed development code to detect problems in the code; automated rollback, using automated delivery tools to monitor the development The code is rolled back.

In one or more embodiments of the present application, the order of the stages of code compilation, image creation, and image deployment cannot be changed.

In one or more embodiments of the present application, when the task item status is not being processed, the task item update content at least includes: updater, update time, comments, remaining estimated time, and record; Wherein, the comments are added through the submission information when the development code is submitted to the code warehouse, the remaining estimated time is determined by the time difference between the planned completion time of the continuous integration and the integration elapsed time, and the record is through The content that needs to be modified is added to the task item; when the status of the task item is not completed, the updated content of the task item also includes the actual time used, and the actual time used is the time it takes to start creating and continue deploying the task item. The time difference is determined.

In a second aspect, embodiments of the present application also provide a management device for software research and development projects. The device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores There are instructions that can be executed by the at least one processor, so that the at least one processor can execute the above-mentioned management method of a software research and development project.

In a third aspect, embodiments of the present application also provide a non-volatile computer storage medium on which computer-executable instructions are stored, and the computer-executable instructions are configured to perform the management of a software research and development project as described above. method.

The embodiments of this application provide a management method, equipment and medium for software research and development projects, which have the following beneficial effects:

1). It can automatically update the established task items, which can effectively avoid the problem of untimely and inaccurate manual update of task items and ensure the timely and accurate update of task progress.

2) By linking the continuous integration and continuous deployment function modules with the software R&D project management function module/system, task items are automatically updated during continuous integration and continuous deployment operations, reducing the need for project developers to switch software on the development and operation platform. The R&D project management function module reduces the workload caused by manually updating task items, thereby reducing the workload of developers and reducing development costs.

Description of the drawings

In order to explain the embodiments of the present application or the technical solutions in the prior art more clearly, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are only These are some embodiments recorded in this application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting creative efforts. In the attached picture:

Figure 1 is a flow chart of a management method for a software research and development project provided by an embodiment of the present application;

Figure 2 is a flow chart of the linkage between continuous integration and software research and development project management systems in an application scenario provided by the embodiment of the present application;

Figure 3 is a flow chart of the linkage between continuous deployment and the software research and development project management system in an application scenario provided by the embodiment of the present application;

Figure 4 is a schematic structural diagram of a management device for software research and development projects provided by an embodiment of the present application.

Detailed ways

In order to enable those in the technical field to better understand the technical solutions in the present application, the technical solutions 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 The embodiments are only some of the embodiments of this application, not all of them. Based on the embodiments of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of protection of this application.

The embodiments of this application provide a management method, equipment and media for software research and development projects, and perform software development work based on a development and operation and maintenance platform. Compared with traditional software development work, it has features such as automation, visualization, and collaboration. On the development and operation and maintenance platform, Continuous integration and continuous deployment can be achieved to ensure the quality and stability of software. The software R&D project management function module can track project progress, improve project progress transparency, quickly respond to project changes, and adjust project plans in a timely manner. Therefore, the embodiments of this application link the continuous integration and continuous deployment functional modules of the development and operation platform with the software R&D project management functional modules, thereby reducing the workload of developers and avoiding the problem of untimely and inaccurate task item updates.

The methods in the embodiments of the present application will be described in detail below through the accompanying drawings.

Figure 1 is a flow chart of a management method for software research and development projects provided by an embodiment of the present application. As shown in Figure 1, the project management method in the embodiment of the present application at least includes the following execution steps:

Step 101: In response to the development code corresponding to the task item being submitted to the code warehouse, the pipeline is triggered to perform continuous integration of the development code.

The software R&D project management method provided by the embodiment of this application is mainly to realize the linkage between continuous integration, continuous deployment and task items. Therefore, in an example of this application, the task items must be configured first. Specifically, the R&D managers R&D content can be divided according to project requirements, and the minimum work item can be configured. The minimum work item here is represented by a task item. At the same time, after configuring the task item, the task item status of the task item also needs to be configured. The task item status Configured as Pending, Processing, and Completed.

After completing the configuration work, the developers of the software development project can carry out development work according to the aforementioned tasks. After the development is completed, the development code will be uploaded to the code warehouse. After uploading, the pipeline will automatically trigger continuous integration testing of the development code.

In one or more possible implementations of the embodiments of this application, the aforementioned continuous integration includes the following stages: code compilation, which compiles the development code; automated testing, which uses automated testing tools to perform unit testing on the development code; Static code analysis, using static code analysis tools to perform static analysis on the development code; product upload, uploading the compiled code files to the product warehouse; making mirrors, making docker images and uploading them to the mirror warehouse; mirror deployment, in Deploy the docker image in the K8S environment for testing. It should be noted that the aforementioned stages can be deleted or added according to actual project requirements, but the order of the three stages of code compilation, image production, and image deployment cannot be changed.

Step 102: Check the status of the task item corresponding to the task item.

After triggering continuous integration, it is necessary to detect the status of the task item corresponding to the task item. Specifically, check whether the status of the task item is processing.

Step 103: When the task item status is not processing, update the task item status and task item update content.

If the status of the aforementioned task item is not being processed, the status of the task item needs to be updated to being processed, and the update content of the task item also needs to be updated. In an example of this application, the update content of the aforementioned task item at least includes: Updater , update time, comments, remaining estimated time and records; among them, comments are added through the submission information when the development code is submitted to the code warehouse, and the remaining estimated time is determined by the time difference between the planned completion time of continuous integration and the integration elapsed time , records are added through the content that needs to be modified in the task item.

Further, if the status of the aforementioned task item is in processing, then only the update content of the aforementioned task item needs to be updated, and there is no need to update the status of the task item.

Step 104: After the continuous integration of the development code is completed, trigger the pipeline to perform continuous deployment of the development code.

Continuous integration and continuous deployment are essential testing processes in software development projects. Therefore, after the continuous integration testing is completed, the pipeline is automatically triggered or manually triggered for continuous deployment of the development code.

In one or more possible implementations of the embodiments of this application, the aforementioned continuous deployment includes the following stages: code compilation, which compiles the development code; automated testing, which uses automated testing tools to perform unit testing on the development code; Static code analysis, using static code analysis tools to perform static analysis on the development code; product upload, uploading the compiled code files to the product warehouse; making mirrors, making docker images and uploading them to the mirror warehouse; mirror deployment, in Deploying the docker image in the K8S environment for production; automated monitoring, using automated monitoring tools to monitor the deployed development code to detect problems in the code; automated rollback, using automated delivery tools to monitor the Development code is rolled back.

Similarly, the aforementioned continuous deployment stages can be deleted or added according to the actual needs of the software development project, but the order of the three stages of code compilation, image production, and image deployment cannot be changed, and these three stages cannot be deleted. .

Step 105: Check the status of the task item corresponding to the task item.

After triggering the pipeline for continuous deployment, you need to check whether the status of the task item corresponding to the task item is completed.

Step 106: When the task item status is not completed, update the task item status and task item update content.

When it is checked that the status of the aforementioned task item is not completed, the status of the task item needs to be updated to completed, and the update content of the task item also needs to be updated. In an example of this application, the update content of the task item here is consistent with the above. Task items in the integration phase are updated with the same content and also include an actual elapsed time determined by the time difference between when the task item was created and when the continuous deployment was completed.

In order to explain the project management method in the embodiment of the present application in more detail, the embodiment of the present application also provides the following supplementary description.

1), Software R&D project management configuration

Configure the minimum work item of the software development project as a task item, and configure the task item status and status flow.

2), continuous integration implementation instructions

The continuous integration process focuses on the integration, construction and testing of code. Its purpose is to detect and solve problems as early as possible, ensure code quality, and make it easier to integrate the code into the main branch. The focus of continuous integration is on the automated construction, automated testing and automated quality inspection of code, with the purpose of ensuring the quality and reliability of the code. For example, in the continuous integration process, developers will frequently submit code to the code repository, and automated build and testing tools will automatically build and test the code, and provide timely feedback on test results and code quality to developers.

In an example of this application, the continuous integration process is implemented based on the pipeline. The triggering method of the pipeline is automatic triggering. When code is submitted in the code warehouse, the pipeline will be automatically triggered to complete the continuous integration process. The continuous integration stages are shown in the following table. .

In an example of this application, the various stages of continuous integration shown in the above table can be deleted and sorted according to the needs of actual development work. The order of the three stages of code compilation, mirror production, and mirror deployment cannot be changed. , and these three stages cannot be deleted. The overall sequence is: code compilation → image production → image deployment.

3), continuous deployment implementation instructions

The continuous deployment process focuses on the deployment, delivery and operation and maintenance of code. Its purpose is to quickly and reliably deploy code to the production environment to ensure the reliability and consistency of delivery. The focus of continuous deployment is automated deployment, automated monitoring, and automated rollback to ensure that code can be deployed to the production environment quickly and reliably. For example, in the continuous deployment process, automated deployment tools will automatically deploy the built code to test, pre-release and production environments, automated monitoring tools will monitor the deployed code, and automated rollback tools will automatically roll back when problems occur Deployed code.

In an example of this application, continuous deployment is based on the process of continuous integration, and the pipeline deployment process can be triggered manually or automatically. The complete stages of continuous deployment are shown in the following table.

In an example of this application, the various stages of continuous deployment shown in the above table can be deleted and sorted according to the needs of actual development work. The order of the three stages of code compilation, image production, and image deployment cannot be changed. , and these three stages cannot be deleted. The overall sequence is: code compilation → image production → image deployment.

4) Description of continuous integration and task item linkage

Figure 2 is a flow chart of the linkage between continuous integration and the software R&D project management system in an application scenario provided by the embodiment of the present application. The linkage of the software R&D project management system here is also the linkage with the task items. It can be seen from Figure 2 The detailed process of continuous integration and task item linkage is as follows:

①Create task items. After the project manager collects the requirements, he disassembles the requirements in the software development project management function module and creates task items;

② Development tasks, developers carry out actual development locally based on the created task items based on the development and operation platform;

③Submit the code, use Git to submit the code, and submit the code to the code warehouse;

④ Integration testing, every code submission will trigger the automatic execution of the pipeline. After the execution of the pipeline is completed, the code will be deployed to the integration test environment for testing;

⑤ Check the status of the task item, and submit the code to trigger the pipeline for code integration, indicating that the actual development of the task item has begun. You need to check whether the status of the current task item is "Processing";

⑥ Modify the status of the task item. When performing continuous code integration, if the status of the task item is not in the "Processing" state, you need to update the task item status to "In Processing". If the task item status is already in the "Processing" state, then The status of the task item does not need to be updated, only other contents of the task item can be updated.

Specifically, when updating the status of a task item to "Processing", the content of the task item that needs to be updated is as shown in the following table:

At the same time, when the status of the task item is already in the "Processing" state, the updated content of the task item is as shown in the following table:

5) Instructions on linkage between continuous deployment and task items

Figure 3 is a flow chart of the linkage between continuous deployment and the software R&D project management system in an application scenario provided by the embodiment of the present application. The linkage of the software R&D project management system here is also the linkage with the task items. It can be seen from Figure 3 The detailed process of linkage between continuous deployment and task items is as follows:

① Integration testing. After the continuous integration testing of the development content of the task item is completed, it indicates that the continuous deployment of the production environment can be carried out;

②Deployment, the continuous deployment process is based on the continuous integration process, and the deployment process is carried out on the basis of continuous integration. After the development code based on the content of the task item is deployed to the production environment, it indicates that the task item has been completed.

③ Check the status of the task item. When deploying code, you need to check whether the status of the current task item is "Completed";

④ Modify the status of the task item. After the code is deployed, if the status of the task item is not in the "Completed" status, you need to update the status of the task item to "Completed". If the status of the task item is already in the "Completed" status, the task The item status does not need to be updated, only other content of the task item can be updated.

Specifically, when updating the status of a task item to "Completed", the content of the task item that needs to be updated is as shown in the following table:

At the same time, when the task item status is already in the "Completed" state, the task item update content is as shown in the following table:

At this point, the linkage between the continuous integration and continuous deployment functional modules of the development and operation platform and the software R&D project management functional module has been completed, thus ensuring timely and accurate updates of the status of task items.

Based on the same inventive concept, embodiments of the present application also provide a management device for software research and development projects, the structure of which is shown in Figure 4.

Figure 4 is a schematic structural diagram of a management device for software research and development projects provided by an embodiment of the present application. As shown in Figure 4, the management device 400 of the software research and development project in the embodiment of the present application specifically includes: at least one processor 401; and a memory 403 communicatively connected (connected through a bus 402) to the at least one processor 401; wherein, The memory 403 stores instructions that can be executed by at least one processor 401, so that the at least one processor 401 can execute a software research and development project management method as described in the above embodiment.

In one or more possible implementations of the embodiments of this application, the aforementioned processor is used to execute, in response to the development code corresponding to the task item being submitted to the code warehouse, trigger the pipeline to perform continuous integration of the development code; check the task The task item status corresponding to the item; when the task item status is not processing, update the task item status and task item update content; after the continuous integration of the development code is completed, trigger the pipeline to perform the development code Continuous deployment; check the task item status corresponding to the task item; when the task item status is not completed, update the task item status and task item update content.

In addition, embodiments of the present application also provide a non-volatile computer storage medium on which computer-executable instructions are stored, and the computer-executable instructions are configured to execute a software research and development project as described above. management methods.

In one or more possible implementations of the embodiments of this application, the aforementioned computer-executable instructions are configured to trigger the pipeline to perform continuous integration of the development code in response to the submission of the development code corresponding to the task item to the code warehouse; check The task item status corresponding to the task item; when the task item status is not processing, update the task item status and task item update content; after the continuous integration of the development code is completed, trigger the pipeline to perform the Continuous deployment of development code; check the task item status corresponding to the task item; when the task item status is not completed, update the task item status and task item update content.

Those skilled in the art should understand that embodiments of the present description may be provided as methods, systems, or computer program products. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The specification is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

It should also be noted that the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements not only includes those elements, but also includes Other elements are not expressly listed or are inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or device that includes the stated element.

This specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present description may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through communications networks. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the descriptions are relatively simple. For relevant details, please refer to the partial description of the method embodiments.

The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desired results. Additionally, the processes depicted in the figures do not necessarily require the specific order shown, or sequential order, to achieve desirable results. Multitasking and parallel processing are also possible or may be advantageous in certain implementations.

The above description is only one or more embodiments of this specification, and is not intended to limit this specification. Various modifications and variations may occur to one or more embodiments of this specification to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims (10)

1. A management method for software research and development projects, characterized in that the method includes: In response to the development code corresponding to the task item being submitted to the code warehouse, the pipeline is triggered to perform continuous integration of the development code; Check the status of the task item corresponding to the task item; When the task item status is not processing, update the task item status and task item update content; After the continuous integration of the development code is completed, trigger the pipeline to perform continuous deployment of the development code; Check the status of the task item corresponding to the task item; When the task item status is not completed, the task item status and task item update content are updated. 2. A management method for software research and development projects according to claim 1, characterized in that, before the development code corresponding to the task item is submitted to the code warehouse, the method further includes: The minimum work item is configured in the software research and development project management function module, and the minimum work item is configured as a task item, and the task item is used to disassemble the development requirements; Configure a task item status corresponding to the task item, and the task item status at least includes: pending, processing, and completed. 3. A management method for software research and development projects according to claim 1, characterized in that: For the continuous integration, the triggering mode of the pipeline is automatic triggering; For the continuous deployment, the triggering mode of the pipeline is automatic triggering or manual triggering. 4. A management method for software research and development projects according to claim 1, characterized in that the stage of continuous integration includes: Code compilation, compiling the development code; Automated testing, using automated testing tools to perform unit testing on the development code; Static code analysis, using static code analysis tools to statically analyze the development code; Product upload, upload the compiled code files to the product warehouse; Make an image, make a docker image and upload it to the image warehouse; Image deployment: deploy the docker image in the K8S environment for testing. 5. A management method for software research and development projects according to claim 4, characterized in that the order of the stages of code compilation, image production and image deployment cannot be changed. 6. A management method for software research and development projects according to claim 1, characterized in that the stage of continuous deployment includes: Code compilation, compiling the development code; Automated testing, using automated testing tools to perform unit testing on the development code; Static code analysis, using static code analysis tools to statically analyze the development code; Product upload, upload the compiled code files to the product warehouse; Make an image, make a docker image and upload it to the image warehouse; Image deployment: deploy the docker image in the K8S environment used for production; Automated monitoring, using automated monitoring tools to monitor the deployed development code to detect problems in the code; Automated rollback, using automated delivery tools to roll back the development code. 7. A management method for software research and development projects according to claim 6, characterized in that the order of the stages of code compilation, image production and image deployment cannot be changed. 8. The management method of a software research and development project according to claim 1, characterized in that when the status of the task item is not being processed, the update content of the task item at least includes: update person, update time, Comments, remaining estimated time and records; wherein, the comments are added through the submission information when the development code is submitted to the code warehouse, and the remaining estimated time is calculated through the planned completion time of the continuous integration and the integration elapsed time. The time difference between is determined, and the record is added based on the content that needs to be modified in the task item; When the task item status is not completed, the task item update content also includes the actual time taken, and the actual time taken is determined by the time difference between the start of creation of the task item and the completion of continuous deployment. 9. A management device for software research and development projects, characterized in that the device includes: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, so that the at least one processor can execute a management method for a software research and development project according to any one of claims 1-8. 10. A non-volatile computer storage medium with computer-executable instructions stored thereon, characterized in that the computer-executable instructions are configured to execute a software according to any one of claims 1-8 R&D project management methods.