Bamboo Screenshot tour
Features – Build Telemetry
Statistics about your builds that you can't get anywhere else.
Numbers, numbers, numbers
Bamboo's Build Telemetry helps your software team learn from the massive amounts of output produced by continuous integration (CI).
Simply put, Bamboo turns raw data into useful information.
With traditional CI systems, all you can see is that your application is building successfully. But how is it doing compared to three months ago? Are the builds still breaking as often as before? These questions, which are essentially unanswerable under traditional CI, are the core focus of Bamboo's Build Telemetry.
See this in action 
(Flash Video 11m 30s)
Your build at a glance
Builds are made to be fixed, but how quickly does your team do it? Bamboo summarises all the important statistics about your build in a single location:
- Completion times, run times, average failures, completion success rate
- How many runs to fix the build? Time to fix? Longest time to fix?
The handy Build Results Filter lets you choose the date range for which you wish to view build results summary information and charts.
Follow the white rabbit...
Drill down to see important information about a particular build result: was it successful? Which tests failed? What was the compile error?
Bamboo intelligently analyses build results:
- Which failing tests are new?
- Which ones were already failing in the previous build?
- In which build did these failures originally occur?
- Which tests did this build fix?
- Which build fixed the failure?
- How long has the build been failing for?
In this way, Bamboo displays information from the perspective of a build. It can also show you the same information from the perspective of your tests or your team.
The big picture
Bamboo collates information across build results to provide insightful statistics on how your project has performed. Charts highlight trends in important metrics such as test failures and build times.
Usage example: The chart below shows the percentage of successful builds and the average build time, per month.
Interpreting this chart:
- As time taken to build increased from March until July, the build quality fell
- Noticing this trend, the team took action and almost halved their build time by September
- As a result of these efforts, the build success rate improved steadily
We know quicker builds mean faster failures and more rapid fixes. Most teams survive on gut feel, Bamboo teams have concrete proof.
You can also compare build results between projects and plans in a variety of useful report formats.