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
Popular Posts
-
...These measures, based on the US Digital Millennium Copyright Act (DMCA) give far too much power to publishers, at the expense of individu...
-
The concept of dragons was probably brought to Japan around 2,000 years ago, along with the technology for paddy agriculture. Their images h...
-
Finally went out and picked up a Nintendo Wii. My god the thing is fun. Ridiculously, ludicrously fun. Hiyat and I had to tear ourselves...
-
His system, he said, starts with a laser that sends part of its beam into photo detectors which produce electrical signal that feed back to ...
-
...why was this given the file name of skyfall?... Certain information, while not specific as to target, gives the government reason to beli...
-
The challenge of having the United States as a neighbour was one of the topics discussed Tuesday during a meeting with Mexican President Vic...
-
When it comes to buying equipment, think g, not b. New 802.11g hardware is nearly five times faster than 802.11b gear, and it will interoper...
-
Here's my (edited) journal entry for this event dated 12/01/98: Wow. I just sessioned and started reading "The Tao of Physics"...
-
Someone that gets it. Service-oriented software, when done correctly in a platform-agnostic way can be flexible, cheap, and can motivate m...
-
This edition provides a prose rendering of The Epic of Gilgamesh, the cycle of poems preserved on clay tablets surviving from ancient Mesopo...
