Atlassian Bamboo is an automated build system like TeamCity, Jenkins, Travis, or CircleCI. It doesn't have the greatest user interface. When a build fails because of a test failure (say, JUnit), it does a good job of indicating that in the UI. But if the build fails for less common reasons (compilation error, missing code coverage, etc.), you have to resort to opening the build logs, and searching for the failure. Seeq's build logs are long and unfriendly to new developers, so this isn't much fun at all!
Bambot is a side project I developed at Seeq and launched in August 2019. It should be run on a schedule with a tool like cron or SystemD. Bambot scans the Atom feed of recent build failures, looks for known failure patterns, and posts a comment with an excerpt of the logs.
Here's what a Bambot comment looks like in Bamboo
If you want to teach bambot how to detect a new type of build failure,
scanString in bambot.go is responsible for identifying errors in the logs
- Clone the repository
- Fetch dependencies:
go get -v -t -d ./... - Run the tests:
go test -v ./... - Make your change (be sure to add a test to
bambot_test.go) - Put up changes for PR!
- Clone the repository
- Run the tests
docker build . - Make your change (be sure to add a test to
bambot_test.go) - Put up changes for PR!