Repositories settings
Followed by the previous article. Enter http: // battleship in the browser, and then enter the Administrator's username (I am here admin) and password. After the logon is successful, the admin link is displayed in the menu in the upper right corner. Click to go to the Management page.
Add a new repository in the repositories selection, and set the hosting as follows:
The reason for choosing custom is that we have adopted the old gitosis.
SSH private key settings
Select the settings menu to go to the SSH settings page.
Upload your private key file. For private key and public key settings in git, refer to my article on git.
Create user
Go back to the dashboard/users page, create two users, C1 and C2, email is shu_chen@esri.com and csfreebird@gmail.com respectively
Specify SMTP information for sending emails for the Review Board
On the settings/Email page, enter your company's SMTP server and account password.
Set Review Group
In the dashboard/review groups group, add a new group agol review. You do not need to set the mailing list and add the C1 and C2 users to the group.
Initiate a review request from a webpage
Now, log on with the C1 user. Click the new review request menu. What you see is this page:
The diff file can be generated using git diff> A. diff in your git project maventest. Then upload the file through DIFF: choose file.
Click Create review request. The review page is displayed. Specify the review group and user C2, set the summary, and click the publish button.
Well, now csfreebird @ gmail registered with C2 has received an email.
This is an automatically generated e-mail. to reply, visit: http: // battleship/R/41/ |
Review request for agol reviewer, Li Jing and Chen Shu. By Chen Shu. Description
Testing
Diffs
- Src/main/Java/COM/ESRI/util/Bytearrayutil. Java (121947f)
View diff |
Click it to go to the website and you will see the diff content.
If yes, click ship it.
If you have any comments, click review, enter your comments, and click Publish. In this way, C1 will soon receive an email notification.
After C1 modified the code, click review and enter comments. C2 will soon be notified by email. Finally, click ship it for approval.
C1 can submit the code.