#BreakingBuilds
Tweet
Published on 12/17/2014 by Kohsuke Kawaguchi
+ A lot of us has grown fond of our loyal butler Mr.Jenkins over time, which was created by https://frontside.io/[Frontside] and chosen as https://jenkins-ci.org/content/the-polls-are-open-for-the-jenkins-logo-contest[a result of a logo contest]. In the true open-source style, the logo has since evolved into many different derivative works, such as https://wiki.jenkins.io/display/JENKINS/Emotional+Jenkins+Plugin[a plugin], https://jenkins-ci.org/content/jenkins-figure-available-shapeways[a 3D model], and https://jenkins-ci.org/content/behind-scenes-jenkins-user-conference-palo-alto[a bobble head]. + +
+ Our friends at CloudBees are running a https://twitter.com/search?q=%23BreakingBuilds[#BreakingBuilds] social media contest through Jan 5th to have some fun with Mr.Jenkins. https://ow.ly/FbZDb[Read Sacha Labourey's blog post], where he draws parallels between what a butler does and what continuous delivery can do. + +
+ I especially agree with him on this point: + +
+ I always loved the idea of using a butler to represent what Jenkins is about, as it projects all of the qualities that define continuous delivery: it is built to be proactive, it will help you fix problems before they happen, it orchestrates your entire pipeline to production without you having to worry about the sophisticated underlying sequence of steps and, if things go wrong Jenkins uses his fingerprint database to trace back the source of the issue. Full service. As your right arm, Jenkins is the reliable and trustworthy guy you want on your team! +
+ +
+ https://ow.ly/FdEBD[Check out the contest rules] and participate. Let's raise the visibility of Jenkins and have some fun in the process! + +