Original source is: http://cliparts.co/clipart/2478772
Jenkins is the leading CI and CD server in the world, choking the market with a solid 70% share and boasting over 111,000 active installations around the world building 5,190,252 jobs as of 2015. This represents a 34% growth in the number of active installations and a 69% growth in the number of running build jobs. In other words, Jenkins is blowing up.
With such explosive growth also comes some pains. One of the great challenges of Jenkins is keeping up with its latest and greatest features, of which there are many given the 1,000+ plugins available today. It’s a Herculean effort, but it’s one that CloudBees customers have unanimously been itching for us to undertake.
Some of this knowledge already exists in the Jenkins community , but a lot of it has also been floating around CloudBees as “tribal knowledge.” At CloudBees, we have seen a rainbow of plugins, use cases, installation sizes and pipelines, so much so that our engineering, support and solutions architect teams have been maintaining their own internal guides and knowledgebases on what works and what doesn’t.
As much as I’m sure the support team enjoys giving these recommendations over Zendesk, it’s not necessarily the most efficient way to disseminate it, and to not formally document it paywalls this information from the rest of the Jenkins community.
Given all of this, CloudBees is proud to announce the release of the first version of our use-cases and best practices eBook -- Jenkins Cookbook: Cutting Edge Best Practices for Continuous Delivery. This guide will cover information that Jenkins users of all levels will appreciate, from hardware and sizing recommendations for a Jenkins installation to guidelines on leveraging Jenkins Workflow with Docker for continuous delivery.
As this guide evolves in its next few releases, it will expand to cover topics such as security, Jenkins cloud installations, mobile development, and guidelines for optimizing builds.