An important part of any software development process is getting reliable builds of the software. Despite its importance, we are often surprised when this isnt done. Here we discuss the process that Matt has put into place on a major project at ThoughtWorks, a process that is increasingly used throughout the company. It stresses a fully automated and reproducible build, including testing, that runs many times a day. This allows each developer to integrate daily thus reducing integration problems.
http://www.martinfowler.com/articles/continuousIntegration.html
Sunday, September 25, 2005
Popular Posts
-
Very dry, dull book with some basic financial info like ROI and cash flow. Not a lot here.
-
Some good stuff from a Canadian futurist: - The rising power of the knowledge worker - Continuous training replaces job security; respect is...
-
I had the pleasure to attend the IBM Think conference in wet and chilly San Fran from Feb 11-14th of this year. The event overall was ...
-
It's been almost exaclty three years since I've updated this blog. In that three years, I've achieved a lot -- I've gone aft...
-
Not a bad audio book, but I expected more. Big ideas: Build a high performance, high-trust culture; Identify desired results and un...
-
Nother confirmation Of einstein... the first images of light escaping a black hole show that they lose energy. In this case, it was a superm...
-
Here's my (edited) journal entry for this event dated 12/01/98: Wow. I just sessioned and started reading "The Tao of Physics...
-
I'm sure someone else has written the rules of business out in terms of the Bushido, but here's my take: Truthfulness You must speak...
-
... or, Decemberween. Whatever. http://www.homestarrunner.com/xmas04.html
-
Increasingly, the overstretched and overburdened have a new answer to work lives of gunning harder for what seems like less and less: Dont j...