Multi-version parallel development method and system based on gitlab
A development system and multi-version technology, applied in the direction of non-redundancy-based fault handling, response error generation, office automation, etc., can solve problems such as the influence of subjective factors, achieve the effect of resolving conflicts and improving development efficiency
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0064]BACKGROUND OF THE INVENTION A method of supporting multi-editions simultaneously develops iterations, making different teams can also develop different functional modules of unified projects, unable to conflict, compile, deploy, and provide a stable test environment for test team testing, parallel development The pattern will greatly improve the development efficiency.
[0065]version number:
[0066]Naming Specification V [Home Edition Number]. [Submap]. [Fix] version number.
[0067][FIX] version number is only used for the version number after the project online, the version number during the CI / CD is only referred to as the top three version numbers, the above version number is not detailed, the first three Vx.x.x
[0068]Branch management specification
[0069]In this manner, the code contains four branches:
[0070]Master branch
[0071]STAGE / VX.X.X;
[0072]Release / vx.x.x;
[0073]Feature / vx.x.x / xxxx;
[0074]Hotfix / vx.x.x / xxxx.
[0075]The relationship between the four codes is likefigur...
Embodiment 2
[0111]Please refer toFigure 4 ,Figure 4 It is a structural diagram of a GitLab-based multi-version parallel development system. Such asimage 3 The present invention is a multi-version parallel development system based on GitLab, including:
[0112]New module, the new module gets a new version of the code, integrate the new version code to the master branch:
[0113]Getting modules, the getting module opens the new version of code, creates a Stage branch from the master branch and a Release branch;
[0114]Pre-trial module, the pre-trial module After the new version is completed, pre-trial is made by the Release branch to obtain pre-trial results;
[0115]Deployment module, the deployment module determines the pre-trial results, if the pre-trial result is correct, deploy the new version code through the Release branch to obtain the deployment result;
[0116]Production module, the production module is produced by the Release branch according to the deployment result, obtaining a Release branch code...
Embodiment 3
[0125]CombineFigure 5As shown, this embodiment discloses a specific embodiment of a computer device. The computer device can include a processor 81 and a memory 82 stored with a computer program instruction.
[0126]Specifically, the processor 81 may include a central processor (CPU), or a particular integrated circuit (Application Specific Integrated Circuit, an ASIC), or can be configured to implement one or more integrated circuits of the present application embodiment.
[0127]The memory 82 can include a large capacity memory for data or instructions. For example, not limitation, memory 82 can include hard disk drives, simply referred to as HDDs, floppy drives, solid state drives, SSDs, flash, CD, magnetic disc, tape or universal serial bus (Universal Serialbus, referred to as a USB) Driver or two or more combinations of these. In appropriate, memory 82 can include a medium that is removably or not removable (or fixed). In a suitable case, the memory 82 can be inside or outside the da...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More