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
-
The concept of dragons was probably brought to Japan around 2,000 years ago, along with the technology for paddy agriculture. Their images h...
-
...why was this given the file name of skyfall?... Certain information, while not specific as to target, gives the government reason to beli...
-
Someone that gets it. Service-oriented software, when done correctly in a platform-agnostic way can be flexible, cheap, and can motivate m...
-
Peruvian archeologists have discovered the first full Inca burial site at Machu Picchu since the famous mountaintop citadel was discovered 9...
-
http://www.homestarrunner.com/sbemail94.html
-
http://esamultimedia.esa.int/images/marsexpress/377-260208-2149-6-co-01-HebesChasma_H1.jpg
-
From the bygone debates over DDR vs. RDRAM to the current controversy over Apples DDR implementations, one issue is commonly misunderstood i...
-
In my mind, this is a huge waste of effort. Put a base on Mars instead of the Moon -- there's huge science finds waiting there to be dis...
-
... or, Decemberween. Whatever. http://www.homestarrunner.com/xmas04.html
-
It looks like this might be real -- a Canadian company succesfully demoed a 16-qubit quantum computer which solved sudoku puzzles, seating...
