The unintended consequences of mining software build systems

on YouTube ↗10m

" summary

A tool called Build Medic consumes build failure logs, classifies failures, selects repair strategies and rewrites build scripts (Maven examples, Log4j fixes) and is evaluated on 84 unseen breakage pairs; it automatically fixes a little more than half, with three quarters of successes in one iteration, reproducing developers' exact fix one third of the time and modifying the same elements 44% of the time. The evaluation also reveals noise: ~12% of passing builds hide failed jobs and two thirds of failing builds are stale.

AI-written summary · about

" chapters (5)

1. 0:00Introduction
2. 1:12Our story
3. 3:38Build medic
4. 6:58Limitations
5. 8:46Conclusion

" related talks

• 44mImproving Software Quality with JenkinsManfred Moser · Jenkins User Conference San Francisco 2012
• 16mA Model for Detecting Faults in Build SpecificationsStefanos Chaliasos, Thodoris Sotiropoulos, Dimitris Mitropoulos, Diomidis Spinellis · OOPSLA 2020
• 28mTowards Automated Updates of Software DependenciesDhanushka Jayasuriya · SPLASH 2022 Doctoral Symposium
• 01h 57mAutomatically improving Java codebases with Error ProneRick Ossendrijver · Voxxed Days Luxembourg 2024
• 47mHow to win in software development with tighter feedback loopsBrian Lucas · Breakpoint 2020
• 06mHow Automated Tools Can Communicate Effective Strategies for Fixing BugsJustin Smith · Strange Loop 2022
• 08mHow to Recommend Tools for Finding and Fixing Software ErrorsChris Brown · Strange Loop 2022
• 46mPainless Organisation and Maintenance of Maven BuildsSandra Parsick · JCON EUROPE 2026