Prevalence of Botched Code Integrations

Onderzoeksoutput: Conference paperResearch

6 Citaten (Scopus)
133 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.
Originele taal-2English
TitelProceedings - 2017 IEEE/ACM 14th International Conference on Mining Software Repositories, MSR 2017
Aantal pagina's4
ISBN van elektronische versie978-1-5386-1544-7
StatusPublished - 29 jun 2017
EvenementInternational Conference on Mining Software Repositories - Buenos Aires, Argentina, Buenos Aires, Argentina
Duur: 20 mei 201721 mei 2017


ConferenceInternational Conference on Mining Software Repositories
Verkorte titelMSR
StadBuenos Aires
Internet adres


Duik in de onderzoeksthema's van 'Prevalence of Botched Code Integrations'. Samen vormen ze een unieke vingerafdruk.

Citeer dit