Automation for the people: Continuous feedback
Receive immediate feedback with every source code change
In the fourth installment of his "Automation for the people" series, Stelligent CTO, Paul Duvall, evaluates various feedback mechanisms that one can incorporate into CI systems and explains why without feedback mediums, like email or RSS, builds in a broken state have the tendency to stay broken.
Published by the popular IBM developerWorks, Paul uses this article to demonstrate how adding a few feedback techniques not only kicks off action so that teams can fix a broken build but enlivens the mood and generates interest in the information these mechanisms are providing.
The Automation for the people series explores the practical uses of automating software development processes and teaching you when and how to apply automation successfully. If you have thoughts, questions, or comments explore developerWorks' "Improve Your Java Code Quality" discussion forum.
|
