Making noices with Hudson/Jenkins

This is an extract from the upcoming book #039;Continuous Integration with Hudson#039;, an open source book on Hudson/Jenkins freely available online, soon to be published in paper form by O#039;Reilly. While it is important to get your build server building your software, it is even more important to get your build server to let people know when it can#039;t do so. A crucial part of the value proposition of any Continuous Integration environment is to improve the flow of information about the health of your project, be it failing unit tests or regressions in the integration test suite, or other quality related issues such as a drop in code coverage or code quality metrics. In all cases, a CI server must let the right people know about any new issues, and it must be able to do so fast. This is what we call Notification. If you have your Jenkins/Hudson instance running on a machine that is physically located in proximity to the development team, you may also want to add sounds into the mix of notification strategies. This can be an effective strategy for small co-located teams, though it becomes trickier if the build server is set up on a virtual machine or elsewhere in the building. There are two ways to integrate audio feedback into your build process in Hudson: the Hudson Sounds plugin and the ...

Date: January, 31 2011
Url: http://www.java.net/blog/johnsmart/archive/2011/01/31/making-noices-hudsonjenkins

Others News