Free Report: Jenkins CI - The Origins of Butlers, Build Masters and Bowties
Does your butler catch broken builds?
Download This Report Now:
In January 2013, RebelLabs released a report titled Why Devs <3 CI: A Guide to Loving Continuous Integration, which, in addition to extolling the virtues of building and automatically testing your app in development several times a day, also showed how to get started with 3 popular Continuous Integration servers: Jenkins, Bamboo and TeamCity (Travis CI was also given a shout out).
In this report, we wanted to focus on Jenkins/Hudson, famous scism of the CI world, which according to RebelLabs' 2012 Developer Productivity Report is used by as many as 49% of IT organizations and is clearly the significant market power in the realm of Continuous Integration.
Jenkins is an open source project, written entirely in Java, and created by Kohsuke Kawaguchi in 2004 while at Sun Microsystems. Kohsuke, who chatted with RebelLabs in an exclusive interview (see the end of this report), initially called the project Hudson and wanted to wanted to create a small program to fix broken builds before other colleagues were able to notice the problem. Sun Microsystems found this project promising, luckily, and a community of happy CI users has evolved quickly.
"I'm calling it Hudson, because in a sense this system is like a build master in my project, and Hudson sounded like just that kind of a name." - Kohsuke Kawaguchi, mentioning Hudson for the first time in a 2005 blog post on Java.net