Not logged in.
Quick Search - Contribution
Contribution Details
| Type | Conference or Workshop Paper |
| Scope | Contributions to practice |
| Published in Proceedings | Yes |
| Title | Un-Break My Build: Assisting Developers with Build Repair Hints |
| Organization Unit | |
| Authors |
|
| Presentation Type | paper |
| Item Subtype | Original Work |
| Refereed | Yes |
| Status | Published in final form |
| Language |
|
| Page Range | 41 - 51 |
| Event Title | 26th Conference on Program Comprehension, ICPC 2018 |
| Event Type | conference |
| Event Location | Gothenburg, Sweden |
| Event Start Date | May 27 - 2018 |
| Event End Date | May 28 - 2018 |
| Place of Publication | New York, United States |
| Publisher | ACM |
| Abstract Text | 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 developers find Bart useful to understand build breaks and that using Bart substantially reduces the time to fix a build break, on average by 41%. |
| Related URLs | |
| Digital Object Identifier | 10.1145/3196321.3196350 |
| Other Identification Number | merlin-id:20335 |
| PDF File |
Download from ZORA
|
| Export |
BibTeX
EP3 XML (ZORA)
|