Continuous Integration with Jenkins/Hudson - a new chapter is available

A new chapter of the Continuous Integration with Jenkins and Hudson book is available! The latest chapter is on build notification strategies:
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'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.
- Login or register to post comments
- Printer-friendly version
- johnsmart's blog
- 464 reads





