After a couple weeks of slacking, this Wednesday Sept. 31st we're holding another scheduled project meeting. In our defense, many of the core project leaders (such as Kohsuke) were either traveling or otherwise unavailable.
This week's meeting agenda is long, we have much to discuss so please join us on IRC!. We'll be discussing, among other things:
- Determining a policy on plugin deprecations
- Details about the Jenkins User Conference
- Handling plugin pull requests that seem to remain open in excess of 30 days.
- Preparing the release of Jenkins LTS 1.409.2
- Official commit workflow for core committers
- Feedback on the request for official definitions of stable, unstable, failure
- Starting to accept donations on behalf of the project to cover infrastructure costs.
We hope to see you on IRC at 11:00 PDT (or 18:00 UTC)!
The first Jenkins User Conference (JUC) brings Jenkins experts and enthusiasts together for an invaluable day of Jenkins-focused learning and networking opportunities.
Join other Jenkins developers at this FREE event to learn and discuss best practices, plug-in development, building on-premise Java or cloud applications and more.
- plug-in development
- Specific Jenkins applications that solve testing/building problems in particular areas: mobility, enterprise/web/cloud applications, and UI testing
- Beyond Java (i.e Jenkins w/ PHP, Ruby, etc)
- Jenkins best practices, lessons learned, case studies, tips and tricks
- Lightning Talks (10 min)
IMPORTANT: Submit your proposal as soon as possible to CFP alias. Call for Papers closes Sept 1, 2011.
Sessions are 50 min long. In your proposal pls include the following info:
- Job Title
- twiter id
- Paper Title
- Audience Level (General, Beginner, Intermediate, Advance)
- Paper Abstract
- Your bio
This doesn't mean that we're done and that you can go forth and write pure ruby plugins... not by any stretch of the imagination. Instead, what it does mean, is that the Jenkins mainline is much more friendly to runtime analysis of classes with which it is not familiar.
When analyzing plugin classes, Jenkins uses just about every kind of metadata you can think of to get information about them: Class name, Field names, method names, member modifiers, annotations, you name it. It even uses the containing class relationship for inner classes to match Descriptors with what they describe.
It's all a great example of convention over configuration (CoC). In fact, I've never really seen CoC implemented in a Java project before as successfully as it has been in Jenkins. Plugin authors don't have to duplicate any metadata that Jenkins can figure out for you -- and it's alot! The drawback though, is that extensions depend very heavily on conforming to the structure of a conventional Java class.
The changes in this merge, and in several of the modules on which Jenkins depends, allow more than ever to get this information by asking an object directly rather than querying its private class structure.
We're still working on the ruby runtime and tools which will provide as crisp a Ruby development experience as we can. I don't want to proffer an estimate of when those will begin to be useable, but it is important to mark this very important milestone and explain what it does and does not mean.
We need you!
There is still much work to be done to enable a writing Jenkins plugins in Ruby, we are looking for people who know Ruby and feel like pitching in: writing Rake tasks, improving the glue layer, documentation, etc.
If you're interested, most of the action is happening on the firstname.lastname@example.org mailing list, so join us!
We've done meetups, we've done sessions, we've done workshops, now it's about time we went ahead and did user conference don't you think?
Our pals over at CloudBees (Harpeet specifically) have taken the initiative in starting to organize just that: a Jenkins User Conference on October 2nd.
If you have your calendar at the ready, you'll notice that October 2nd is the Sunday before JavaOne kicks off this year in San Francisco.
The details are still coming together, but a proposed agenda has already been posted by Harpeet.
As this is a community event, I'll be sure to keep the updates coming on this site but you may want to add the CloudBees' Blog to your feed reader just in case (or just follow them on Twitter: @CloudBees).