Automated Build Systems

Pizza, beer, and mingling

"Developing at Speed with Jenkins"
Robert Harker (http://www.linkedin.com/in/rlh100) - Sr. Support Engineer, Yahoo! Sports

"Building and Deploying Netflix in the Cloud"
Gareth Bowles (http://www.linkedin.com/in/garethbowles) - Senior Tools Engineer, Netflix
Brian Moyles (http://www.linkedin.com/in/bmoyles) - Senior DevOps Engineer - Cloud Tools, Netflix

"Automated Build System at RelayHealth"
Ron Cordell (http://www.linkedin.com/pub/ron-cordell/1/4b4/212) - Architect, RelayHealth

For our May event, I want to hear about automated build systems, also known as "build servers," for enabling "continuous integration."

There appear to be many to choose from, including Bamboo, Jenkins, Buildbot, CruiseControl, etc. Here are some things it would be interesting to hear about. Which build system do you use, and why? What do you like about it? What do you dislike about it? Do you use it for anything other than just building your code, such as running regression test suites, or even for continuous deployment? Did you have to do anything special to the base system to get what you needed out of it? Do you have any tips or tricks for running your build system, and keeping it running? If you're using an interpreted language (no compilation step) for your project, what do you use your build server for? Do you have any policies and procedures around build failures, test failures, or anything else, and how do you enforce them? Do you run your builds on a cloud provider, or on your own hardware? Have you got experience with multiple build systems, and could you compare them for us?

I'm looking for two to four 20-25 minute talks. If you can give a talk, please contact me, Chris Westin, through meetup.

As well as the evening's theme talks, we can fit in 2-3 five minute lightning talks at the beginning of the evening; any topic that would be interesting to the #lspe audience is welcome. If you're interested in giving a lightning talk, contact me, Chris Westin, through meetup.