Integration Watch: The quickly changing market for continuous integration
June 9, 2009 —
(Page 1 of 2)
Continuous integration (CI) is a practice that, I believe, is very quietly gaining acceptance in IT. Two years ago, when I first wrote about CI, most folks who were not active in the agile community had never heard of it. Today, most everyone I speak to knows something about it.
I am a judge for the Jolt industry awards, presented by another company, and this year we had several CI products to examine for the first time. While adoption has steadily increased, my view is that the market is maturing quickly, with the predictable effect that users are consolidating around specific packages while ignoring other products.
Before getting into which products will make the cut, it’s necessary to first address an even more fundamental division in the market: enterprise vs. workgroup-scale CI servers. The distinction between the two levels is important in the selection of products. Enterprise CI servers are designed to manage more than builds, running tests and gathering metrics. They have an application development life-cycle management capability, including bill-of-materials inventory, deployment capabilities, release management, and deeper and more extensive process management tools.
In the category of enterprise CI servers, there are three products: Electric Cloud’s Electric Commander, IBM’s Build Forge and UrbanCode’s Anthill Pro. All three are big, expensive propositions that deliver considerable automation to build processes, as well as the early warning alerts implied by the term continuous in CI. UrbanCode provides a free copy to qualifying open-source projects. (To be clear, there is an open-source version of Anthill that’s been around for several years. However, it is completely unrelated to UrbanCode’s current product.)
The heart of the CI market is really in the sub-enterprise servers. These systems focus primarily or exclusively on managing the build, running tests, and storing metrics and statistics. This area has long been dominated by free, open-source products. The grandfather of them all is Cruise Control, which for several years defined the CI market.
Cruise Control was originally developed by ThoughtWorks, then was spun out as OSS, and now parts of it serve as the basis of ThoughtWorks’ new foray into CI, called Cruise. (Note, however, that Cruise is not at all a productized superset of Cruise Control but a different product entirely.)
Related Search Term(s): continuous integration
Share this link: http://sdt.bz/33527
Most Read Latest News Blog Resources
Zeichick’s Take: The handheld and the tablet, circa 1976
Texas Instruments' and Hewlett-Packard's calculators were doing things decades ago we take for granted today
|
|
Google talks tools at AnDevCon III
New 3D debugging tool and recent ADK changes are detailed by Google developers at the third Android Developer Conference
|
|
Android is the focus of two new design tools
Anywhere Software and Xamarin provide ways for developers to create and test their applications on PCs
|
|
Achievements and learning: Gamification comes to businesses and schools
Startup takes page from gamers by offering achievement marks to get developers more engaged in their projects
|
Virtualization: Not just for machines anymore
Network virtualization allows multi-tiered applications to behave as though they were in a physical network
|
|
Achievements and learning: Gamification comes to businesses and schools
Startup takes page from gamers by offering achievement marks to get developers more engaged in their projects
|
|
Google talks tools at AnDevCon III
New 3D debugging tool and recent ADK changes are detailed by Google developers at the third Android Developer Conference
|
|
SmartBear rolls out new quality solution: API Complete
Software gives organizations ability to write test scripts and monitor APIs by bridging the DevOps divide
|
Creation
To write better software, cultivate your ability to be creative.
|
|
Slick...but who needs it?
compilr.com is a well-designed site and the folks behind it seem to have their heart in the right place. But...who needs it?
|
|
How to be a better software developer
Want to be a better developer? You won't get there by mastering an interesting language or learning a new set of APIs.
|
|
Wooing Galatea
Do yourself a favor and check out Galatea 2.2, a wonderful book by novelist Richard Powers.
|
Five SCM Best Practices
Two-thirds of all software projects fail, according to the Standish Group’s CHAOS study. Improper usage of software configuration management...
|
|
|
Best Practices for Branching and Merging Patterns
Development teams often create a branching pattern, usually drawn out on a white board or in a Visio document, that is used as a model to...
|
|
Automated Error Reporting
We invite you to read a short e-zine that tells you all about automated error reporting for .NET applications. This 8-page e-zine is packed...
|
|
The End of Application Redeploys
Imagine that every time you wanted to write, send or receive an email, you needed to restart your computer. How much time would this take, a...
|
Related Articles
Continuous integration: Not just for agile anymore
Organizations are gleaning good things from continuous integration even if they are using slower methodologies
|
IBM updates InfoSphere for data integration
Big Blue has announced two new editions of InfoSphere products that address product information management and data integration. Support for internationalization plays heavily in the data integration release.
|
Jitterbit 2.0 focuses on reuse in integration
The update to the company's open-source integration platform features improvements to its user interface and integration server. Pipeline customization, which allows the creation of reusable scripts in the integration process, is also included.
|