Why Automate builds? Because we all make mistakes (and boy, I can testify to that based on my BottomFeeder work :) ) This is Randy Coulman from Key Technologies:

Randy's tracing his ideas about automating builds back to continuous integration from the original XP projects, and it needed translation forward from the Envy-specific things. They also use multiple languages and tools, so they wanted something that would work across the board - so they use CruiseControl with ANT.

And with that Randy is off to VW to show us how it works - he's got a bit of unpublished code that he's pushing into Store, and that should kick off an automated build (he has CruiseControl watching Store and SVN). The build kicks off an RTP script, which is pretty cool. The build for the demo kicked off an email with a verbose explanation as to what happened.

Randy submitted Store specific support into the latest CruiseControl, stream, and it's now (as of 2.7.2) part of the product. Hooking Store up meant a Java plugin that has VW check Store for changes (using StoreForGlorp), which drops results out via stdout, and the Java plugin reads that.

Technorati Tags: smalltalk, smalltalk solutions