Our code support 20+ more hardware platform, we need to make sure the code can work well at all the 20+ platform. In the past few years, we use post-commit and Jenkins Poll SCM . When the bad code check in, we will freeze the branch until the problem is fixed. It wastes other developer's time , it is difficult to guarantee that the code always works.
So we'd like to make a pre-commit CI system, if anyone who want to commit his code, we will build and test it first , if the CI passed the build and test , then it can merge to branches.
We have 2 plan:
Plan A ( 2015 we had make a linux svn issue plugin like this ,but it is easy ,just replace the svn program , see it at attachment):
1. Make a perl script to replace the svn program, rename svn bin to svn-org;
2. User can use svn commit command to commit his code ( in fact , the perl script will start) , the script will store the patches, and send it to our build system. Also script will start a daemon program work at user's computer to listen the build result.
3. When the build finished, daemon will tell user the result . We plan use svn mucc to commit the file ,then update the working copy.
Plan B (search it at google ):
1. Create a merge (pull) branch from the trunk and check that out.
2.Merge you development check-out branch into the "pull" branch.
3.Run test threads and do compares to verify the merge.
4.Integrate with the trunk.
R & D Management Group
Hangzhou Hikvision Digital Technology Co.,Ltd
No.555 Qianmo Road, Binjiang District, Hangzhou 310052, China
This e-mail and its attachments contain confidential information from HIKVISION, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
发件人: Julian Foad [mailto:julianfoad_at_apache.org]
发送时间: 2018年11月30日 21:20
收件人: Nico Kadel-Garcia; 钱海远(Nathan)
抄送: Johan Corveleyn; Subversion
主题: Re: Can SVN pull request same as GIT?
Nico Kadel-Garcia wrote:
> On Thu, Nov 29, 2018 at 10:31 PM 钱海远(Nathan) <qianhaiyuan_at_hikvision.com> wrote:
>> We want to develop a feature like git pull request .
> This seems infeasible. The working copy in which the merges would occur does not exist in the Subversion workflow.
Hello Nico! What do you mean? If Nathan is developing a Subversion pull request workflow, his software can create a WC when it needs one.
Hello Nathan. I am having difficulty knowing what you really require. "Like git pull request" could mean lots of different things. It would help if you can describe exactly what you require.
This electronic message is intended to be viewed only by the individual or entity to whom it is addressed. It may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any dissemination, distribution or copying of this communication is strictly prohibited without our prior permission. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, or if you have received this communication in error, please notify us immediately by return e-mail and delete the original message and any copies of it from your computer system. For further information about Hikvision company. please see our website at www.hikvision.com<http://www.hikvision.com>
Received on 2018-12-03 03:06:05 CET