A CI pipeline turns red. A developer opens the logs, searches for the error, checks the code, and starts investigating.
Sometimes the problem is obvious. Other times, the same failure has appeared before, someone has already investigated it, and the team is repeating work that should not have been necessary.
This is one of the frustrating parts of software development: debugging knowledge is often temporary. A developer may discover the actual cause of a failure, fix it, and move on. Weeks later, another developer encounters a similar problem but has no easy way to retrieve the previous investigation.
We explored this problem while building FlakeTrail, a debugging assistant that uses Hindsight to remember previous CI investigations and retrieve relevant knowledge when similar failures occur.
Why CI failures are difficult to investigate
Continuous Integration (CI) systems automatically build and test software after code changes.β¦