A Brief Study on Build Failures in Continuous Integration: Causation and Effect

  • Romit JainEmail author
  • Saket Kumar SinghEmail author
  • Bharavi Mishra
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 714)


Continuous Integration (CI) has successfully tackled the problem of bug fixing owing to which it has gained immense popularity among software developers. CI encourages to commit on the go so that each bug can be traced to its source and handled accordingly. However, CI remains a practice at its core, and only a part of it can be implemented. Anything which does not follow good CI practice would pave the way for a greater number of build fails. CI’s continuous nature may cause a clutter in a big team, leading to one developer’s build failing the other. Numerous consecutive build fails can put the project on a standstill till the build is made clean which may cause developers to lose interest eventually. We investigate, in this paper, causation and effect of build failure in CI. We first see whether a large team size contributes to more build failure and second, whether an increasing number of consecutive build failures have any impact on the productivity of developers. We have used data provided in TravisTorrent and analysed the 3,702,595 Travis builds which mostly contain Java and Ruby as the programming language used. For both the languages, we have made a comprehensive analysis of the problem we address.


Continuous integration Build failures Team size Productivity 


  1. 1.
    Vasilescu Bogdan et al., ‘Quality and Productivity Outcomes Relating to Continuous Integration in GitHub’, Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering Pages, (2015) 805–816Google Scholar
  2. 2.
  3. 3.
    Padhye Rohan et al., A study of external community contribution to open-source projects on GitHub, Proceedings of the 11th Working Conference on Mining Software Repositories (2014) 332–335Google Scholar
  4. 4.
    ‘Please stop breaking the build’,
  5. 5.
  6. 6.
    ‘travistorrent _11_1_2017.csv.gz’,
  7. 7.
    Beller, Moritz and Gousios, Georgios and Zaidman, Andy, Travis Torrent: Synthesizing Travis CI and GitHub for Full-Stack Research on Continuous Integration, Proceedings of the 14th working conference on mining software repositories (2017)Google Scholar
  8. 8.
    ‘Software Development and The Broken Window Theory’

Copyright information

© Springer Nature Singapore Pte Ltd. 2019

Authors and Affiliations

  1. 1.The LNM Institute of Information TechnologyJaipurIndia

Personalised recommendations