At Sonatype, we’re very excited about the Hudson proposal that has been posted to the Eclipse Foundation website today. We believe Hudson moving to the Eclipse Foundation is the best way forward for both the Hudson and Jenkins projects. Having Hudson at a mature OSS foundation like Eclipse gives enterprise users the confidence that Hudson will remain vibrant and will continue to grow, and provides an opportunity to reconnect the Jenkins and Hudson communities back into a single focused community. Sonatype supports Eclipse as a Strategic Member because we’ve been impressed by the infrastructure, process, and approach to project oversight. It’s an ideal place for Hudson to mature.
Looking at the interested parties in the Hudson proposal it’s apparent that more resources than ever will be poured into the Hudson project. Oracle and Sonatype have been working diligently to add fundamental architectural improvements to Hudson — which has paved the way for a new stream of innovation. VMWare and Tasktop have also indicated that they will be providing additional development resources, and we’re keen to start collaborating with them.
Sonatype also hopes to attract more enterprise-class contributors by taking the lead and contributing our core Hudson innovations to Eclipse. This includes all of the Maven 3.x integration that we have created to date. We were originally only going to provide a portion of our Maven 3.x integration to the OSS community, but we are so excited about Hudson moving to Eclipse we want to stimulate community adoption and wider participation by providing the best Maven integration possible.
The Hudson proposal still needs to go through the 30-day review period within the Eclipse community, but we really think Hudson has found its new home. The Eclipse Foundation is a highly respected organization, has proven to be a vendor neutral, and has fostered many successful projects. Eclipse would be a great place for Hudson and Jenkins to reunite and now would be an ideal time. It can only be a good thing for users and I sincerely hope that the Jenkins team will seriously consider this option.
Hudson plays a key role in Sonatype’s commercial product portfolio so we’re committed to making the project succeed at Eclipse. We will offer commercial support and value added functionality in our ‘Professional’ version of Hudson. We are planning to contribute all commercial work we’ve invested in thus far to the Hudson project but we have more commercial features in the pipeline. Our customers tell us that along with Apache Maven, Nexus, and m2eclipse, Hudson is a critical part of their software development infrastructure. Hudson will be successful at the Eclipse Foundation and Sonatype plans to take an active part in that success.
One important difference between Hudson Open Source and Hudson Professional is how they support Maven 3.
Sonatype has developed state-of-the-art support for Maven 3 focusing on creating seamless integration between the internals of Hudson CI and Maven. Year of work on Maven 3 internals to support more efficient embedding along with our multi-year investment in bringing both JSR-330 support and GWT UI integration to Hudson CI has produced a CI system that support Maven 3 like no other on the market.
If you’ve used Hudson and Maven together in the past, you might be familiar with the Maven 2 project type that provides users with the ability to define a Maven build that is aware of a project’s POM. While we understood the motivation for a Maven-specific project type, we took our Maven support in an entirely difference direction. We created a Maven build that can be used a part of a larger freestyle build, and the reason we did this was to get away for the idea that a Maven build can only include one step, one call to a series of goals.
Sonatype found this to be more of a limitation than an advantage.
Hudson Continuous Integration with Sonatype Professional webinar
Sonatype is hosting a free webinar on continuous integration. Register for this webinar today before spots fill up! Sonatype Professional is the only integrated suite created for Maven-centric builds. The suite includes Sonatype Certified & Integrated Distributions of: Maven, Hudson, Nexus Professional, Eclipse Integration, Developer Onboarding as well as support from the experts. The Sonatype-enhanced distribution of Hudson included in the suite is fully tested, supported and designed to meet the demands of mission-critical software development. Register to learn how Sonatype Professional empowers development teams to realize the promise of agile through continuous integration, while reducing project risk.
- Date: Tuesday, March 29, 2011
- Time: 9:00 am Eastern Daylight Time
- Duration: 30 minutes
- Presenter: Blaine Mincey, Sonatype Senior Systems Engineer
Register for this webinar today!
Sonatype founder and CTO Jason van Zyl will be hosting a free webinar on the future of Hudson next week.
Hudson is a continuous integration (CI) server that helps you check-out source code, build and test your project, publish the results and communicate the results to team members. We’ve been working to make it easier to extend Hudson, to reduce the effort required to write a Hudson plugin, and to put in a new foundation for the next level of Hudson interoperability and performance. We’re excited about the work that has been done and the work yet to come. The benefits of these changes include better leveraging of industry standards, increased performance and stability, and tight integration with Maven 3 that provides greater visibility into running builds. Come to learn more about Hudson CI and future plans for the project.
- Date: Tuesday, March 15, 2011
- Time: 10:30 am Eastern Daylight Time (New York, GMT-04:00)
- Presenter: Jason van Zyl, CTO & Founder of Sonatype
- Register here
Two weeks ago we proposed that [Hudson plugin authors be able to use dependency injection] through the JSR-330 standard. This change makes it easier to write Hudson plugins without having to dig into Hudson internals, it provides greater separation between plugins and Hudson core, and it makes it much easier to test plugins without having to bring along core Hudson objects.
These changes are now [in the core of Hudson]. Even though JSR330 can now be used by plugin authors these changes should, in no way, affect plugin authors using the existing API. Since this question came up on the mailing list, I’ll give a short description of how it works here. The JSR330 integration allows you to take advantage of JSR330, if you wish, by using an alternative plugin strategy. Our new plugin strategy interoperates with the existing, classic plugin strategy. Sonatype’s Hudson Professional distribution actually ships with a mixture of JSR330 plugins and classic plugins and we find this works quite well. We tried to make it easier to use new strategies for wiring up plugin, and [Stuart McCulloch has offered this strategy on the Jenkins development list] and it appears to have been absorbed as part of [JENKINS-8897].