-
Type:
Suggestion
-
Resolution: Fixed
-
Component/s: Notifications
-
None
-
Environment:Using standalone - version 1.1.2 build 305 - May 31, 2007 - Solaris Intel.
The broken build e-mails in bamboo would be a lot more helpful if they included more context on why the build broke. We have a large team (50+ developers) and it's not always obvious if your change broke the build, especially if it's a downstream component or an integration test.
Right now all the e-mail says is: The build has 1 failed test and 90 successful tests.
The Bamboo build page gives great info about new/old/fixed tests, why not include that in the e-mail?
There is a similar problem with compile failures, all it says is that "No failed tests found, a possible compilation error." Not sure if that's specific to maven2 builds or not.
This feature would be great for big teams - I get 25+ build message a day for broken/fixed builds and it would be great to know which ones I might have caused.