The two most significant bottlenecks in code merging are the build process and the unit tests. However, as the number of items to be checked in a code review increases, that code review becomes a bottleneck for code merging as well. Because of the dependency structure between code review services, an error in one service affects the entire service. As a result, whenever a service error occurs, it is crucial to have methods for determining which code review service has ultimately caused the error. With the goal of achieving a non-stop & non-breakable code review service, this paper describes an early error detection method along with a case study of the service.
翻译：代码合并的两个最重要的瓶颈是构建过程和单位测试。但是,随着代码审查中要检查的项目数量的增加,代码审查也成为代码合并的瓶颈。由于代码审查服务之间的依赖性结构,一个服务的错误影响到整个服务。因此,每当服务错误发生时,关键是掌握确定代码审查服务最终导致错误的方法。为了实现一个不可停止和不可破代码审查服务的目标,本文件描述了早期错误探测方法,同时对服务进行了案例研究。
相关内容
微信扫码咨询专知VIP会员