In São Paulo from this weekend

I’ll be flying to Sao Paulo this week to attend Jenkins meet-up (Saturday) and JavaOne Latin America (next Tuesday and onward).

The last time I visited Brazil was a few years ago, but thanks to Mauricio Leal, whom I tagged around with for a JUG tour around Brazil, it was really a blast. This time around I don’t have the benefit of the local guy to the degree I had before, but I’m really looking forward to it.

The major pre-travel issue was that the Brazilian government run out of the visa stickers. But I made it just in time (or more precisely I hopefully will be — I’ll be picking up my passport Wednesday and flying Thursday. Phew!)

The highlight of the trip will be the first-eve Jenkins meet up in São Paulo — I’ve been a big fan of local communities where there exists a language barrier. I’m from Japan, so I’ve seen it the first hand the value of local communities would bring to the table. The speaker/session line up is amazing, the event is free, and there’ll be a social at the end, so if you are in the area and has been interested in meeting with fellow Jenkins developers and users, please RSVP.

But if you can’t come in person, at least please consider joinining the Brazilian Portaguese mailing list of Jenkins users, which we are launching.

I don’t really have any plans on Sunday and Monday — any sight-seeing suggestions and/or interest of meeting up and chatting about stuff would be more than welcome. Leave the comment here, or see the right for my e-mail address.

POTD: submit a patch to Jenkins, and let him test it for you

Here’s my 2nd after-JavaOne “project of the day” Jenkins plugin. This has been in the back of my mind for quite some time, but it took this gentleman to grill me on this feature during JavaOne for me to finally put it together — so thank YOU for doing that. although I didn’t catch your name.

The plugin is called the “patch parameter” plugin. This plugin lets you submit a patch when scheduling a build, and that gets applied to the checked out source tree before a build would commence. Any failure to apply a patch will result in a build failure.

This plugin can be used for a “pre-tested commit” workflow. You can work on a change locally, have the diff tested on the server, then if you are satisfied, you can commit it. I can imagine this would be also an interesting building block for integration with code review tools.

I should also note that we have the Subversion Merge plugin for a different approach to a similar problem, and distributed VCS can generally do this better (for example I do one for Git in CloudBees Validated Merge plugin.)

My take on Jenkins User Conference

Last week, we had our first ever Jenkins User Conference. More than 30 talks have been proposed (of which we were only able to accomodate 10 or so), 7 companies had helped pay for the event, and more than 250 people attended (out of 400 people registered.) People came from all over the world, from Japan, Korea, Australia, Europe, and so on. One of them even told me that he primarily came from Sweden for JUC, and being able to go to JavaOne was a nice extra. That’s saying something!

For me, to see the project I started 7 years ago to come this far, it was a rather special day. I was able to talk to many people during the day, most of the talks were quite good, and I enjoyed every bit of it. I hope other people felt the same way.

I’ve done the keynote that discusses the current state of the Jenkins project, and the progress we’ve made in the last 8 months since the divorce drama. The slides can be seen below, and I belive the recording will be posted online later.

Thank you for everyone who came, and thank you to those who made this event possible (especially Alyssa, Lisa, and Heidi who did the real hard work of organizing the event and taking care of the logistics.)
There was interest in doing another one in Europe. I certainly hope it would happen!

Calling for your participation in Jenkins User Conference

By now, you are surely aware of the Jenkins User Conference (JUC) that will be held the Sunday before JavaOne – October 2 – at the Marines’ Memorial Hotel in San Francisco, starting 9:00am PDT. This is a major milestone for the Jenkins Community – our first ever User Conference!

The Jenkins community needs to participate in JUC – certainly as an attendee, but also in supporting the organization and promotion of the Conference. Several vendors are helping to organize this first conference, but I think it’d be good for everyone if this is a community-driven event, and for that the Jenkins Community must play a major role, too.

To that end, I’d like to ask everyone to do the following to support JUC:

  • Register to attend. After all, it’s a free event with lots of useful contents!
  • Speak. People often incorrectly think that they need to be a project insider to be “qualified”, but that’s not the case. Lots of users want to hear about how other fellow users are using the software. So please tell us your showing off how you use Jenkins, clever ways you combine various pieces, technical/organizational challenges you faced, an so on. There are some great suggestions for potential topics on the JUC web page.
  • Recruit. If you aren’t comfortable speaking, please recruit someone else you think has an interesting Jenkins-related topic to present to the Community.
  • Promote the Conference. Even if you can’t come, please Tweet about it, re-Tweet posts you see from the @jenkinsconf Twitter account to your followers, email your friends, post to Facebook, and Like the JUC posts already there. If you paste in the JUC web page URL to your Facebook post, it will automatically pull in the cool Jenkins image we created for the conference. All of these things are easy to do and they really make a difference in getting the word out!
  • Sponsor the Conference. Sponsors are actively being recruited. One of the ways companies can give back to the Jenkins project that they’ve benefited from is by sponsoring JUC. Helping the project flourish protects your company’s investment in the use of Jenkins. All sponsorship levels also defray the costs of the Conference, thus keeping it free for attendees. Maybe your company would consider sponsoring? Hit up your favorite vendor to do so, too!

Registrations are coming in daily. So far, we have about 80 attendees, so please keep them coming. If you haven’t registered, register soon before the seats fill up. Making the event successful opens up many interesting options (like organizing other events in the future, etc), and that way it benefits the community as a whole, not to mention continuing to increase the Community’s knowledge and making Jenkins an even better platform in the process.

I look forward to seeing you there – as an attendee, a speaker, and/or a sponsor! We’ll have some more exciting things to announce in the coming weeks, so stay tuned!

See you at JavaOne!

With a week-long Scandinavia tour over, my nexgt big week is JavaOne! JavaOne has always been an incredibly busy week for me, but this year is no exception.

  • Sunday before JavaOne, we’ll be having a full day Hackathon at Digg. If you are around, please RSVP and join us.
  • I’ll be presenting a Hudson talk (S313338 – Sep 20th 10am in Parc55). I’ll discuss the current state of the project, then I’ll spend most of the time talking about various techniques on Hudson that goes beyond simple builds & tests.
  • I’ll be on a 15-minute OTN video interview after that.
  • InfraDNA will have a kiosk outside the JavaOne vendor exhibit area. We’ll be showing our value-add Hudson distribution ICHCI, and we’d be happy to answer any Hudson related questions/comments, so please drop by. I should be at the booth most of the time.

I think it’ll be fun, and I certainly look forward to seeing as many of you as I can!