I just got the O’Reilly Open Source Award 2011 at OSCON at Portland, for my work on Jenkins. I’m quite humbled and honored, (and I certainly hope I can finally convince my wife that I’m doing my part in making the world better.)
For the past 7 years of the life of this project, I’ve really just simply doing what I enjoyed — writing software, making users happy, and working with other great people. Yes, I did get the ball started, but the next thing I knew there are other people around me, and together we’ve been pushing things forward in a pace that I couldn’t dream of. And now it’s almost as if the project has its own life. If anything, I think the Jenkins community as a whole deserves the award, not me. So here is a big thank you to you all.
The “divorce” drama early this year between Hudson/Jenkins was a drag, but now that that’s behind, Jenkins joined SPI, lots of community initiatives, and exciting things happening at CloudBees, I’m really looking forward to continue pushing the ball forward for years to come.
Long live Jenkins!
As a follow up to the successful sessions we held in London, San Francisco, and Tokyo, CloudBees will be holding two additional Jenkins training sessions in the coming few months, in San Francisco and New York City. The San Francisco session has already sold out, but there are several remaining slots for the New York session (interested individuals can register here).
I’m pleased to announce that I will be personally running the New York session. Our intent is to keep the number of participants low so as to allow for maximum interaction — aside from the caricculum, I often end up discussing challenges and problems individual attendees are facing with them, and it works only if we have a smaller room, and people seem to like that. As I’ve noted before, interacting with Jenkins users is always an enlightening experience and it’s also extremely helpful for me personally as I continuously work on software improvements for the project.
Like our London session, this will be aimed at users that already have a working knowledge of Jenkins. Once you get the build and tests automated, what can you do from there? The idea with these sessions is to help improve on advanced Jenkins functionalities to answer this question, including creating bigger automated workflows / broader choreographies, code quality metrics, automated deployment, and so on.
I look forward to seeing you there!