Back to overview

Un-break my build: assisting developers with build repair hints

Type of publication Peer-reviewed
Publikationsform Proceedings (peer-reviewed)
Author Vassallo Carmine, Proksch Sebastian, Zemp Timothy, Gall Harald C.,
Project SURF-MobileAppsData
Show all

Proceedings (peer-reviewed)

Editor , Siegmund Janet; , Roy Chanchal K.; , Khomh Foutse
Page(s) 41 - 51
Title of proceedings Proceedings of the 26th Conf on Program Comprehension, ICPC 2018
DOI 10.1145/3196321.3196350

Open Access

Type of Open Access Repository (Green Open Access)


Continuous integration is an agile software development practice. Instead of integrating features right before a release, they are constantly being integrated in an automated build process. This shortens the release cycle, improves software quality, and reduces time to market. However, the whole process will come to a halt when a commit breaks the build, which can happen for several reasons, e.g., compilation errors or test failures, and fixing the build suddenly becomes a top priority. Developers not only have to find the cause of the build break and fix it, but they have to be quick in all of it to avoid a delay for others. Unfortunately, these steps require deep knowledge and are often time consuming. To support developers in fixing a build break, we propose Bart, a tool that summarizes the reasons of the build failure and suggests possible solutions found on the Internet. We will show in a case study with eight participants that developersfind Bart useful to understand build breaks and that using Bart substantially reduces the time to fix a build break, on average by 41%.