For information on exhibition and sponsorship opportunities at the convention, contact Sharon Cordesse at email@example.com
Download the OSCON Java Sponsor/Exhibitor Prospectus
For information on trade opportunities with O'Reilly conferences or contact mediapartners@ oreilly.com
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of convention news and annoucements, please sign up for the OSCON email bulletin (login required)
View a complete list of OSCON contacts
One of Jenkins’ greatest strengths is its flexibility – via its plugin system, it supports a diverse array of source control systems, build tools, reporting tools and much, much more. This means there is no one right way to set up your Jenkins configuration – rather, Jenkins, and your build process in general, should adapt to fit your distinct needs. But this doesn’t mean that you can’t learn from other Jenkins setups! In my 2.5 years using and developing Jenkins, I’ve had three very different use cases, ranging from building and unit testing a small number of pure Java projects at Cisco, to pre-tested commits and continuous deployment of a production webapp written primarily in PHP and Python at Digg, and now a combination of Java builds, unit testing and reporting, native packages for a number of Linux distributions, and automated smoke, integration and performance testing on all those platforms as well.
This has given me a fairly broad experience with different uses for Jenkins, and for the common trends across those different uses. I’ll talk about what I’ve learned, what mistakes I’ve made, and what best practices I’ve settled on across all these use cases. I’ll also put on my “Jenkins committer and governance board member” hat to talk a bit about the current state of the Jenkins project itself, and where the Jenkins development community is planning to take it in coming months.
Andrew Bayer is the build engineer at Cloudera, Inc., and a member of the Jenkins governing board. He has been developing and maintaining build tools for over 9 years, and has been involved with Jenkins since early 2009. He is a contributor to Jenkins core, and the creator and/or maintainer of a number of prominent Jenkins plugins, including the Git plugin.