CloudBees reports on “The State of Docker, Jenkins and Continuous Delivery”

Data supports the popularity of Jenkins and Docker for accelerating enterprise software delivery.

  • 8 years ago Posted in
CloudBees has published the results from a survey launched at DockerCon Barcelona on “The State of Docker, Jenkins and Continuous Delivery.” The results of the survey prove organizations are aware of the need for an open platform solution that simplifies and accelerates CD adoption. As of June 2016, there have been more than 5 million pulls of the Jenkins image from the Docker Registry. In fact, 83% of survey respondents want to use Docker containers for running Jenkins build servers, evidence that Jenkins and Docker are becoming the standard technologies needed for modern day application delivery.
 
The survey was distributed to DockerCon Barcelona attendees, who responded throughout November and December 2015. Two-thirds of survey takers identified their role as software developer, DevOps practitioner or architect while one-third identified with other titles, including team lead, executive, build manager and QA.
 
"The lethal combination of Jenkins and Docker is proving to be very valuable for DevOps teams. By leveraging the tight integration with source code control mechanisms such as Git, Jenkins can initiate a build process each time a developer commits his code," said Janakiram MSV, analyst at Janakiram & Associates and contributor to Forbes magazine. "This process results in a new Docker image which is instantly available across environments. Organizations are deploying private Docker registries to publish and maintain their internal Docker images."
 
Notable statistics from the survey results include:
?        83% of survey respondents want to use Docker containers for running Jenkins build servers
?        94% of survey respondents have already adopted Docker or plan to adopt Docker in the next 12 months
?        82% of survey respondents want to deliver application infrastructure using Docker
?        68% will run new applications in Docker containers, in both test and production environments
?        55% are working with Docker containers with on-premise virtual machines vs. 48% running in a public cloud
?        96% of respondents think that Docker is suitable for development environments
?        81% of respondents think Docker is suitable for production environments
?        48% of respondents manually manage Docker clusters
 
“DevOps teams see Docker as a huge asset to software delivery as evidenced by the many and varied on- and off-premise environments Docker containers are running in,” said Kohsuke Kawaguchi, CTO of CloudBees and founder of Jenkins. “The power of Docker and Jenkins technologies to automate and significantly accelerate software delivery signifies the next wave in application delivery.”
 
“Pairing these two open source solutions, both leaders in the DevOps movement, gives developers new power to automate their software development, testing and delivery,” said Nick Stinemates, vice president of business development and technical alliances at Docker. “Developers have shown great interest in adopting Docker as their container of choice and integrating it with Jenkins, and I think we will see strong adoption of this pair across DevOps teams.”
SLE Micro is rapidly becoming a critical foundation of customers’ digital transformation, in...
Veritas InfoScale native deployment in Kubernetes environments, including Red Hat OpenShift, will...
Canonical has released Ubuntu 21.10 - the most productive environment for cloud-native developers...
Data from 1,200 respondents and insights from seven industry experts reveal rapid growth, some...
Civo, a pure play “cloud native” service provider, has published the result of its research on...
Now, organizations can quickly set data in motion on their private infrastructure with the...
Kubernetes, supported by a vibrant open source community, can drive outstanding innovation. To help...
New Mendix survey shows that British businesses are investing in low-code to respond to the new...