Continuous integration build breakage rationale: Travis data case study

Continuous Integration (CI) has a prominent role in software engineering. However, little research that involves quantitative results has been done upon the verifiable outcomes of this practice. TravisTorrent, a freely available data set based on Travis CI and GitHub provides deep analysis of the project source code, process and dependency status of 1,359 projects that use CI. In this paper, we analyze this data set and explore the features in order to get the information about the factors that affect build breakage.

[1]  Georgios Gousios,et al.  The GHTorent dataset and tool suite , 2013, 2013 10th Working Conference on Mining Software Repositories (MSR).

[2]  Daniel M. Germán,et al.  The promises and perils of mining git , 2009, 2009 6th IEEE International Working Conference on Mining Software Repositories.

[3]  Leon J. Osterweil,et al.  Software processes are software too , 1987, ISPW.

[4]  Daniel M. Germán,et al.  Cohesive and Isolated Development with Branches , 2012, FASE.

[5]  Georgios Gousios,et al.  TravisTorrent: Synthesizing Travis CI and GitHub for Full-Stack Research on Continuous Integration , 2017, 2017 IEEE/ACM 14th International Conference on Mining Software Repositories (MSR).

[6]  Daniela E. Damian,et al.  The promises and perils of mining GitHub , 2009, MSR 2014.

[7]  Georgios Gousios,et al.  Oops, my tests broke the build: An analysis of Travis CI builds with GitHub , 2016, PeerJ Prepr..

[8]  Georgios Gousios,et al.  When, how, and why developers (do not) test in their IDEs , 2015, ESEC/SIGSOFT FSE.

[9]  Jacob Cohen,et al.  Applied multiple regression/correlation analysis for the behavioral sciences , 1979 .

[10]  Ian H. Witten,et al.  The WEKA data mining software: an update , 2009, SKDD.