Imagine a bacon-wrapped Ferrari. Still not better than our free technical reports.

Java Tools and Technologies Landscape for 2014

Continuous Integration Servers

Automation is the foundation of productivity gains in software development nowadays, and the diversity in the ways in which we develop software calls for an open-source platform that can fit any environment. The survey result shows that Jenkins continues to lead this space with its ecosystem, extensibility,
and diversity.

      – Kohsuke Kawaguchi, Jenkins project founder, CloudBees CTO​​

Java tools and technologies landscape 2014 continuous integration CI server used graph

In 2013, only 68% of developers reported using Continuous Integration technology, so it’s good to see that a more representative number from this year’s findings has raised it nearly to 80%. Only about 1 in 5 developers do not use CI technologies whatsoever.

However, more than half of developers (among all respondents) not only use CI, but use Jenkins specifically. When normalized, Jenkins (70%) settles in a comfortably dominant position, possibly amused that it was once considered a rival of Hudson (8%). This market is still maturing, with the majority of developers either using Jenkins or nothing at all. At least the discussion over Jenkins vs Hudson can be put to rest!

Other signs of progression in this area are present, with commercial tools Bamboo (9%) and TeamCity (7.5%) each grabbing some of the CI market, likely enjoying some small usage based on the popularity of Atlassian’s and JetBrains’ tools for developers and software organizations. We saw Travis CI (2%) appear in the past, which offers both open source and professional CI options, and CruiseControl (1%), which had 4% of the market in 2012, seems to be sinking peacefully into oblivion.

For additional resources, please review Release Management for Enterprises plus Why Devs <3 CI: A Guide to Loving Continuous Integration as well as Jenkins CI: The Origins of Butlers, Build Masters and Bowties.