Prevalence of Botched Code Integrations

Research output: Chapter in Book/Report/Conference proceedingConference paper

6 Citations (Scopus)
134 Downloads (Pure)


Integrating code from different sources can be an error-prone and effort-intensive process.
While an integration may appear statically sound, unexpected errors may still surface at run time.
The industry practice of continuous integration aims to detect these and other run-time errors through an extensive pipeline of successive tests.
Using data from a continuous integration service, Travis CI, we look into the prevalence of integration errors.
We find code integration causes failure less often than regular commits.
Repairing is usually done the same day and takes less than ten lines of code, largely in the source code.
These results indicate that applying proper practices mitigates many issues associated with code integration.
Original languageEnglish
Title of host publicationProceedings - 2017 IEEE/ACM 14th International Conference on Mining Software Repositories, MSR 2017
Number of pages4
ISBN (Electronic)978-1-5386-1544-7
Publication statusPublished - 29 Jun 2017
EventInternational Conference on Mining Software Repositories - Buenos Aires, Argentina, Buenos Aires, Argentina
Duration: 20 May 201721 May 2017


ConferenceInternational Conference on Mining Software Repositories
Abbreviated titleMSR
CityBuenos Aires
Internet address


  • code integration
  • empirical
  • GHTorrent
  • GitHub
  • merge commit
  • Mining Software Repositories
  • Travis CI
  • TravisTorrent


Dive into the research topics of 'Prevalence of Botched Code Integrations'. Together they form a unique fingerprint.

Cite this