Posts Tagged ‘jenkins’

Jenkins HackCamp at Tokyo

October 14th, 2011

Right after JavaOne, I traveled to Tokyo, and attended a 3-day hack camp. The Jenkins community had done several 1-day hackathon around the world, but this is the first that spanned across multiple days.

14 people came to a small traditional hotel in this small sea-side city of Ito, a 90 minutes train ride away from Tokyo city center, complete with a spa. Japanese people have a special place in their hearts for a spa, so we had to have one!

We stayed there for close to 48 hours, and the hacking was literally around the clock! I was still somewhat jet-lagged, so I went to sleep earlier, but when I woke up next morning around 6am, some people were still hacking code!

In between the hacking, we ate, drunk, talked, and took a bath. Some of us played board games that one of us brought (there seems to be a non-trivial intersection between the board game fans and open-source hackers.) There were a wide variety of activities, ranging from Arduino hardware hacking for XFD to automatic slave registration based on Android devices connected to USB, a bunch of automatic tool installers to classloader enhancements. Those results should be made online once people recovered from the trip.

One lesson for me for the next occasion is to plan for more ice-breaker events (which involves more drinking!) Maybe asking everyone to do a 5-10 minutes mini-talk about what they do and who they are.

jenkins , ,

My take on Jenkins User Conference

October 13th, 2011

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!

jenkins , ,

Calling for your participation in Jenkins User Conference

August 22nd, 2011

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!

jenkins , ,

O’Reilly Open Source Award 2011

July 28th, 2011

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!

jenkins , ,

Jenkins training in New York next week

July 5th, 2011

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!

jenkins , ,

IP rights on my Hudson contributions

May 6th, 2011

There seems to be some confusion/mis-information about the IP claim I made in my previous post, so let me clarify why I think they are valid. There are two parts to it.

First, about contributions I made during the early days of the project, when it was still my hobby project. It is generally true that corporations want to own as much IP as possible that employees create (and justifiably so, since that’s what we get paid for), and Sun was no exception. However, there’s California labor code section 2870, which says employees get to retain rights under certain conditions. The question here is whether something like Hudson was “actual or demonstrably anticipated research or development of the employer.” If it’s interpreted broadly, I suppose one could say any tools can be “anticipated development for Sun.” But if the emphasis is on “demonstrably”, maybe I get to keep the rights. I honestly don’t know. (For fairness, there’s also considerable portions of code that I created that are undoubtedly owned by Sun and hence now by Oracle — I never said I own everything.)

Second, there are contributions I made after I left Oracle, before we moved on to Jenkins. I think it’s pretty clear that that portion doesn’t belong to Oracle.

If I guess Oracle’s position correctly, based on a comment from Ted in my blog, I believe their approach is that the copyright owner doesn’t really matter, as the whole thing is licensed under the MIT license. It is true that the MIT license is very non-restrictive, and one can combine it with just about any other licenses without making whole thing incompatible.

The MIT license says the following, so I’m still not sure how it can be re-licensed to any other license, but it certainly can be put side by side with code under EPL, so maybe that’s what they intend to do. Again, I just don’t know:

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the “Software”), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

I hope that clarifies what I mean.

jenkins , ,

Oracle proposes to move Hudson to Eclipse

May 4th, 2011

I was about to go into my session in JAX 2011 when I learned that Oracle made a proposal to move the Hudson project to the Eclipse foundation. Needless to say, I was quite surprised!

One one hand, I think this definitely shows the great success of the Jenkins project post divorce. As I discussed in these slides with concrete numbers. Were it not for the succcess of Jenkins, they wouldn’t be giving up the project.

But at the same time, I just wish Oracle saw that coming a few months earlier, while we were still seeking the middle ground. We were very interested in having the trademark moved under the custody of a neutral 3rd party, but they were very clear that that’s not acceptable to them. And it also disppoints me that they decided not to reach out to the Jenkins community about this move, when we’ve been conducting our governance meeting all open out there for anyone to join. But I guess they are never really interested in working with us.

I’m also curious how they intend to handle some IP related issues. Two things come off the top of my mind. The current logo, which is a Microsoft clipart. We’ve mentioned that to a representative in Oracle some time ago, but we haven’t heard back. Then there are about 6-month worth of my contributions after I left Oracle, which I don’t think Oracle can unilatelarly donate to the Eclipse foundation.

jenkins , ,

Upcoming Webinar “State of Jenkins”

April 25th, 2011

A few weeks back, I’ve presented the current state of the Jenkins project in the Silicon Valley CI Summit. This wednesday, I’ll be doing a re-run of this talk as a webinar.

The talk focuses on concrete numbers that illustrate the progress of the Jenkins project, and while any numbers need to be taken with a grain of salt, I think it helps convince those who are interested in switching to Jenkins. This is also your chance to ask questions!

Looking forward to seeing you this Wednesday 10am PDT / 1pm EDT / 5pm GMT. Please RSVP.

jenkins ,

Upcoming Webinar “Mastering Jenkins Security”

March 23rd, 2011

I’ll be doing another Jenkins webinar titled “Mastering Jenkins Security” in the next Thursday 10am Pacific Time. It’s a free event, so please register.

After the first webinar, I got a number of feedbacks about the future webinar topics. So when we thought about doing the next one, this came fairly naturally. Unlike the first one, this time the idea is to pick one topic and go do some in-depth discussions. It’s harder to do in a conference, and so I think it’s better suited for webinars.

By default, no security is enabled in Jenkins, so in an environment where a stricter access control is more benefitial, an administrator needs to set this up to suit their needs, and there’s just a lot of different ways people want to configure it. So in this webinar, I’ll start by outlining the basic design of the security system in Jenkins — authentication and authorization — so that you can build a sufficient mental model of how it works, how they interact, and how it can be made to fit your needs.

We’ll then go through the major implementations of those two pluggability points, so that you can pick the right implementation for your needs. There are some plugins, like Active Directory plugin or OpenID plugin, that tightly integrates with respective systems that provide great integration experience. Then there are other plugins, like script security realm, which provides a general purpose mechanism that can be used to integrate Jenkins with arbitrary systems with little effort. Then there’s an entirely different approach of delegating authentication outside Jenkins to the front end reverse proxy. On the authorization side, there are lesser but still a number of options that you can choose from.

Aside from the authentication/authorization, I’ll discuss the security implications of running builds in Jenkins and other standard webapp security considerations, such as cross-site scripting problems, cross-site request forgery issues, and other attack vectors. I think it’d be useful for those who run Jenkins for a larger team.

So once again, please register if you are interested in attending, and if you have future topic suggestions, please let me know!

jenkins, Uncategorized , ,

One last plea for Hudson/Jenkins vote

January 26th, 2011

As Andrew posted, the vote for Jenkins is open now. You need to be a member of the users or the dev list to be eligible, and the detailed instruction can be found here. I thought I’d take the opportunity to make one last plea to the community.

When the representative of Oracle says it to my face that I should just go find something else to work on, or that I need to immediately stop making [infrastructure] changes or the next email I will receive will be from their lawyers, or when you hear him describe me as a hurdle to the community, I think writing on the wall is pretty clear to me.

As such, regardless of the outcome of the vote, I find it very unlikely that I can continue to contribute to the Hudson project, and thus I will move on on Jenkins. I can’t control what others do, but I can at least decide what I personally do. While days leading up has been rather hard on me emotionally, now that I made up my mind, I actually feel good (besides, it’s such a nice day in San Jose today.) I’m confident that many key core and plugin contributors (who has made Hudson what it is today) will join me, and I hope users will follow us too (which is the other part of what made Hudson what it is today.)

What I’d like to ask the broader Hudson community is to have your voice heard and give us your support by voting. That you want to be with us. It lets us maintain the continuity of the project, it gives us legitimacy, and it sends a singal to the unaware silent majority which way they should follow. It’s the best way to maintain our community.

So please let your voice heard, and help us spread the word. For one last time.

hudson ,