Hound

This is an uncompleted project

Feel free to skip or look through

Inspiration

The motivation behind the creation of Hound is based on my personal experience and observation of engineers who come across build failures that don't make sense to them. For organizations keeping CI builds green is a priority, When a build fails it can be quite disruptive, especially in large mono repos. This can impact a developer's productivity if failures are not quickly identified and mitigated. What if we had a tool that could help developers or built shepherds identify errors quickly within CI and Explain a possible cause for the error and suggest a fix. Better yet what if we had a tool that could automate the process of investigating whether a PR pipeline or workflow Is also failing on the main development branch and determine who to reach out to.

What it does

Hound is a build engineer's best friend. Technically speaking Hound is a Github action that runs at the end of workflows and uses Gen AI to analyze failed workflow job logs to easily Identify failures within the job, explain the cause, and try to suggest a fix. It also helps build shepherds or engineers track down responsible parties for broken tests or builds from prior builds on the default development branch that might be unrelated to the initial changes.

How we built it

Hound is a typescript Github action, Within the Github action i used the GitHub octokit JS library to gather information about the current workflow run, jobs that are running in it, logs, and also to get workflow runs on the default dev branch for comparison. From the action, we would reach out to a queue and trigger a cloud function to pass on information about what failed and what job etc.. In turn, the function would format the information into a prompt to be sent to the vertexAI model and the output would be sent back to the GitHub action formatted in markdown for display in the job summary or comments

Challenges we ran into

The biggest challenge for me was time as I started the hackathon pretty late and had a lot of competing priorities (Work, family, vacation, school) while trying to complete the hackathon without a team!