A Craftsman looks at continuous integration

This post advocates for a more rigorous approach to Continuous Integration (CI) beyond simple daily builds. It emphasizes the importance of triggering builds on every check-in, building all code and libraries, running all unit and acceptance tests, and failing the build if any errors occur. The author stresses that a CI process is more than just the build itself and includes automated testing as a critical component. It also highlights the need to take CI server notifications seriously and fix failures immediately rather than ignoring them.