Pipelines are amazing in enabling agile development, making continuous deployment possible. As software projects grow in complexity, as the number of tests increase, and pipelines grow and become less maintainable. The primary purpose of piplines is to provide feedback on the release readiness, and when they grow beyond a certain point, the feedback becomes fuzzy, and ownership of breaking changes becomes blurry. Therefore, I saw a need for a tool to parse the logs and extract the failing tests, call stack, and the relevant code changes.
PipeVision consists of two main components, a data aggregation tool that executes periodically to analyze pipelines and parse test execution logs, then updates the database; and a web interface to show analytical data about failed tests.
