Source code Submit SOP (git version)

Home > Sci-Tech

Source code Submit SOP (git version)

2022-01-15 12:04:34 9 ℃

First, principle

1. Before maintaining public base classes, toolbars, and secondary libraries, it is necessary to discuss with other team members before the consensus can be maintained.

2. Strictly comply with the source code check-in specification, help to discover code vulnerabilities, reduce code consolidation risks, reduce the error probability of the remote warehouse code, please be careful, cautious, don't skip the process step by time. The progress is meaningful under the premise of ensuring quality.

Second, six steps

1. Before starting the encoding, the code from the remote warehouse PULL recently successfully built (help to reduce the code consolidation conflict).

2, write function code and corresponding unit tests (if there is no special case tool class and the second-party library will write unit test, the service code can be judged by themselves).

3, local construction

1) Compile code, execute unit test, run code, to ensure that the unit test is passed, and the program is functioning properly;

2) Check if the code meets the coding specification (it is recommended to use a static code check tool automatically check);

3) Execute CommT pre-operation, progressively compare each change point, check if the code logic meets the coding intent, and the comment is missing;

4) Fill in the commit information, pay attention to the name of the branch name, this submit the associated task or BUG number; if there are multiple content, it should be explained. It is recommended to complete the independent task or repair bugs for commit, try to avoid a task multiple times multiple tasks multiple times.

Summary of information 1:

Develop_3.0: 1, [Task QZA-339] Tyson WS Clinet Access; 2, JServer-Parent Adds WS Client Dependent Package;

Summary of Sample 2:

Master: 1, [bug QZA-433] Football - important Tab increases local cache;

5) Confirm the commit;

4, second construction

1) From the remote warehouse PULL latest code to the local; if there is no code update, skip step 4;

2) If there is a conflict, it needs to be cautious with the code; if you do not understand the conflict code, you can call the code author to merge;

3) Compile code, perform unit tests corresponding to this CommT, run code, ensure that unit test is passed, and the program is operating normally, and the function satisfies the demand;

4) Commit again, compare the change point, and fill in the commit information;

5, Push code.

6, submit code automation construction (if any)

1) Automation tool listening code submission, automatically build code, execute unit test, if the build fails or unit test failure, send a message notification team;

2) After receiving the failure notice in accordance with the "Immediate Pause Principle" team, PULL code is suspended until the PULL code is not allowed to receive successful notice; the problem code authors need to solve the problem immediately, and resubmit.