Increment establishing method and device

Abstract

The invention provides an increment establishing method and device. The increment establishing method comprises the steps that the types of establishment tasks and corresponding execution sequences of the tasks are defined; alteration sets of the establishment tasks are obtained; the alteration sets of the establishment tasks are sorted according to the execution sequences to generate an establishment task list; according to the establishment task list, a compiling environment is created, compiling is performed in sequence, and compiled output files are compressed into increment packs. By adopting the technical scheme, rapid and accurate increment pack establishment is achieved, repeatedly produced problems between development and testing and factors possibly influencing product quality are decreased, and the product research and development efficiency and patch pack issuing frequentness are improved.

Description

technical field [0001] The present invention relates to the technical field of software development, in particular to an incremental construction method and an incremental construction device. Background technique [0002] With the expansion of software scale and the improvement of software complexity, it becomes more and more important to obtain and verify the latest development and modification as soon as possible in the development process. The traditional method of fully building, packaging, installing (deploying), and providing for test verification has the following disadvantages: [0003] 1. Usually hundreds of people or a larger R&D team can submit hundreds of times a day. If each version is fully built, packaged, and installed (deployed), it will take hundreds of hours or even more; [0004] 2. In the way of full packaging according to the plan and at fixed time intervals, the wrong submission in the installation package cannot be stripped; [0005] 3. By manually...

AI Technical Summary

Problems solved by technology

[0004] 2. In the way of full packaging according to the plan and at fixed time intervals, the wrong submission in the installation package cannot be stripped;

[0005] 3. By manually developing local builds and publishing incremental replacement files for test verification, it is impossible to guarantee that the compilation and build environment when developing local build replacement files is consistent with the build environment of the build server, and it is impossible to guarantee that the code will be finalized when developing local build replacement files. will be submitted to the code repository;

[0006] 4. After developing and submitting the code, through the construction server, update the latest code of the relevant project (project) and build it, and release the incremental replacement file to the test, which will bring in other new development submissions, which may bring in new problems;

[0007] 5. After developing and submitting the code, through the construction server, update the specified version of the relevant project (project) to build in parallel, and release the incremental replacement file for testing, which may result in less or more projects being selected, resulting in modified code and replacement files Inconsistent;

[0008] 6. In both cases 4 and 5, it is impossible to accurately identify the changes of dependent components, resulting in component incompatibility, or the situation that the components that the project depends on are not updated

Images