Code development and test process management method based on git

Abstract

The invention relates to the field of computer software design, and particularly to a code development and testing process management method based on git. According to the method, a life cycle of software code is divided into three stages of development, testing and production, each stage has a separate git code library to be separately managed, continuous integration of the code is also separately and discriminately managed, relative independence of the code of each stage is guaranteed, and problems of code conflict and code stage confusion are solved.

Description

technical field

[0001] The invention relates to the field of computer software design, in particular to a git-based code development and test process management method. This method divides the life cycle of software code into three stages: development, testing, and production. Each stage has a separate git code base for separate management, and the continuous integration of code is also managed separately to ensure that the code of each stage Relatively independent, solve the problem of code conflict and code phase confusion. Background technique

[0002] In the software development process, software code writing is the specific process of realizing each system module, and the realization content includes the requirements of the target system's functions, performance, interfaces, and interfaces. Testing is also a very important step in project development. By testing each function point implemented by the code, the usability of the function is confirmed.

[0003] Developme...

Examples

Embodiment Construction

[0042] The specific implementation steps of the git-based code development and testing process management method of the present invention are described below through an embodiment:

[0043] (1) Staged code and continuous integration management

[0044] Based on the branch management of git, the master branch is established as the production stage for management, the test branch is established as the test stage for management, and each developer establishes various development branches according to their own development tasks as the development stage for management. Where master and test are managed branches, only testers and system administrators have administrative rights.

[0045] The code in each stage needs to go through an independent continuous integration process before being merged into the branch of the next stage.

[0046] 1. In the development phase, developers need to manually call the gradle build command for continuous integration, and the maven warehouse in the...

technical field

[0001] The invention relates to the field of computer software design, in particular to a git-based code development and test process management method. This method divides the life cycle of software code into three stages: development, testing, and production. Each stage has a separate git code base for separate management, and the continuous integration of code is also managed separately to ensure that the code of each stage Relatively independent, solve the problem of code conflict and code phase confusion. Background technique

[0002] In the software development process, software code writing is the specific process of realizing each system module, and the realization content includes the requirements of the target system's functions, performance, interfaces, and interfaces. Testing is also a very important step in project development. By testing each function point implemented by the code, the usability of the function is confirmed.

[0003] Developme...

Examples

Embodiment Construction

[0042] The specific implementation steps of the git-based code development and testing process management method of the present invention are described below through an embodiment:

[0043] (1) Staged code and continuous integration management

[0044] Based on the branch management of git, the master branch is established as the production stage for management, the test branch is established as the test stage for management, and each developer establishes various development branches according to their own development tasks as the development stage for management. Where master and test are managed branches, only testers and system administrators have administrative rights.

[0045] The code in each stage needs to go through an independent continuous integration process before being merged into the branch of the next stage.

[0046] 1. In the development phase, developers need to manually call the gradle build command for continuous integration, and the maven warehouse in the...

Images