Continuous project integration method and continuous project integration system

Abstract

The application provides a continuous project integration method and a continuous project integration system, wherein the method includes the following steps that project information which includes a project ID and one or more pieces of project branch information is obtained; according to the project ID and the project branch information, one or more pieces of corresponding continuous integration task configuration information are generated; one or more continuous integration tasks corresponding to the continuous integration task configuration information are created. The application can enhance continuous integration performance and reduce integration cost.

Description

technical field [0001] The present application relates to the technical field of project integration, in particular to a method for project continuous integration and a system for project continuous integration. Background technique [0002] In a typical software project, the integration phase is usually at the end, so there are the most problems, and in the end it may lead to failure to deliver on time, and continuous integration (Continuous integration, referred to as CI) can be used to solve this problem. Continuous integration is a software development practice in which members of a team integrate their work frequently, usually at least once per day, which results in multiple integrations per day, with each integration being done through an automated build , with the goal of allowing the team to receive feedback and make improvements on an ongoing basis, without having to wait until later in the development cycle to find and fix bugs. [0003] Hudson is widely used in t...

AI Technical Summary

Problems solved by technology

[0008] 5. After Hudson builds regularly, it will analyze a result through configuration. It does not have a result monitoring function. If you need to obtain build quality data, you need to open one or more tasks to view and summarize;

[0009] 6. When the project ends and the task is deleted, the build result will be deleted along with the task, and it does not have the function of persistent saving

[0012] 2. Manually maintain the relationship between continuous integration tasks and projects. According to calculations, the number of tasks required by an Internet company is between 1,000 and 50,000, and the manual maintenance costs are huge;

[0013] 3. The continuous integration and construction quality data of manual summary projects requires a lot of labor costs for simple summary calculations, and the system cannot automatically monitor project quality;

[0014] 4. After the project is completed and the task is deleted, the historical construction quality data cannot be saved persistently, and the historical data cannot be traced;

[0015] 5. When Hudson creates tasks on a large scale (more than 10,000), there will be performance bottlenecks, which will cause Hudson to access slowly and cannot be expanded

[0016] In short, when the existing Hudson technical solutions are applied in projects, especially in large-scale projects, they face problems such as continuous integration task configuration difficulties, management and maintenance difficulties, project quality monitoring difficulties, and project quality data analysis difficulties. When continuous integration is performed by manual configuration management, it will bring a large cost overhead

Images