Impact of Continuous Integration on Code Reviews

Abstract: Peer code review and continuous integration often interleave with each other in the modern software quality man- agement. Although several studies investigate how non-technical factors (e.g., reviewer workload), developer participation and even patch size affect the code review process, the impact of continuous integration on code reviews is not yet properly understood. In this paper, we report an exploratory study using 578K automated build entries where we investigate the impact of automated builds on the code reviews. Our investigation suggests that successfully passed builds are more likely to encourage new code review participation in a pull request. Frequently built projects are found to be maintaining a steady level of reviewing activities over the years, which was quite missing from the rarely built projects. Experiments with 26,516 automated build entries reported that our proposed model can identify 64% of the builds that triggered new code reviews later.

 

Experimental Data

Available upon request. Please contact masud.rahman@usask.ca for the experimental data.

Related Publication(s)

@INPROCEEDINGS{msrch2017masud, 
author={M. M. Rahman and C. K. Roy}, 
booktitle={ Proc. MSR}, 
title={Impact of Continuous Integration on Code Reviews}, 
year={2017}, 
pages={499-502} }
 

← Check out other tools by Masud Rahman

© Masud Rahman, Computer Science, University of Saskatchewan, Canada.