The release candidate for Hudson 3.0 from Eclipse is now available for download and evaluation from the Eclipse Download page. This version previews the production Hudson 3.0 release which, barring show-stopper problems should be released in a couple of weeks.
The fourth and final milestone release of Hudson 3.0 from Eclipse is now available. This milestone finalizes the library versions used by the release, polishes off the new features such as the initial setup screens and provides an improved plug-in management center. The next scheduled release after this one will be the formal Hudson 3.0 Release Candidate. M4 can be downloaded for evaluation from the Eclipse Download page.
Milestone 2 is next latest step in the Eclipse Alpha Release process. The key purpose of this milestone was to further consolidate libraries, in particular to remove dependencies on third party code that was not compatible with the Eclipse IP guidelines. This new version can be downloaded for evaluation from the Eclipse Download page.
Milestone 1 is the latest step in the Eclipse Alpha Release process. The key purpose of this milestone was to reduce the number of third party libraries used by Hudson and to update them where relevant. This new version can be downloaded for evaluation from the Eclipse Download page.
Hudson 2.2.0 is a signifiant release introducing the new cascading projects capability, build blocking for matrix jobs and user account creation notification. There are also 22 other improvements and bugfixes available in this release. As per usual, you can head over to the changelog for the complete list.
Hot on the heels of JavaOne, the latest regular iteration of the 2.1.n train is now available for download and production use. This new release contains 12 bugfixes and 10 enhancements. For the full list of changes and fixes, check out the changelog.
JavaOne is here at last and there's a whole bunch of Hudson content. Here's the rundown for your diaries
|11.00 am||The Future of Java Build and Continuous Integration – Panel
||Hotel Nikko Ballroom|
|2.30 pm||Hudson: Onward and Upward
Susan Duncan, Winston Prakash
|Parc 55 - Embarcadero|
|12:00 pm||ALM Automation with Mylyn and Hudson
Mik Kersten (Tasktop, Mylyn)
|Parc 55 - Divisidero|
|10:30 am||Using Hudson's Development Framework to Build Your First Hudson Plug-in - Hands On Lab||Hilton San Francisco - Franciscan Room|
|1.30 pm||Maximize Team Productivity with Hudson, Maven, and Team Productivity Center in JDeveloper
|Marriott Marquis - Golden Gate A
|8:30 am||Using Hudson for a Lot More Than Just Continuous Integration
Tim O'Brien (Sonatype)
|Parc 55 - Embarcadero|
|JavaOne Demo grounds||Oracle At Eclipse||Hilton|
The latest regular iteration of the 2.1.n train is now available for download and production use. This new release contains 38 bugfixes and 9 new features and enhancements. For the full list of changes and fixes, check out the changelog.
Concurrent with the work to tidy Hudson up in preparation for Eclipse we've been able to devote some time to providing a beta version of the eagerly awaited 2.1.0 release which importantly introduces support for Maven 3 and GIT into core.
At the moment the beta is available only as a WAR file. If you need a production quality release the 2.0.1 distribution is available. This beta is for evaluation only and could possible cause problems with . If you are running production Hudson instances wait for the official 2.1.0 production release.
There are a few known issues with this release"
Concurrently with this new release we encourage you to take a look at the ongoing Hudson Book project. This complete guide to Hudson can be downloaded from the Hudson-ci site and it's free! The book is still undergoing development and we encourage you to provide feedback via the Hudson email lists.
On schedule, Hudson 2.0.1 has been released into the wild. This release contains a significant number (45!) of bugfixes and several new features.
The key new features to note are:
For more information check out the Hudson changelog.
In order to improve the openness and predictability of the Hudson project it was proposed today that the project, its associated domain name and trademarks would transfer to the Eclipse Foundation.
We're pleased to announce the general availability of Hudson 2.0.0. As well as marking the start of a new numbering scheme, this release addresses 29 bug fixes and enhancements, many of which were voted for by the community.
The key features to note are:
For more information check out the Hudson changelog.
Discussion has been flowing on the Dev lists with respect to the current versioning scheme. The current proposal is that the scheme will change from the current two part n.nnn scheme to a more granular 3 part scheme where:
In order to switch to this new scheme the proposal is that the numbering will reset to 2.0.0 with the next regular release. This way the scheme can be introduced without messing up the update center.
We're pleased to announce the availability of Hudson 1.398. This release introduces streamlining of the plugin development and release process as explained here in the Hudson wiki. Additionally more infrastructure cleanup has been done and bugs are fixed in the Emma and Perforce plugins amongst others. For more information check out the changelog.
To help with the future governance of Hudson as a strong and open community based project, we've defined some process documents that clearly outline the release and development process and the responsibilities of committers. These documents are also linked from the main documents page under "Process Documents":
Comments or feedback on these documents can be recorded on the Hudson wiki.
We're pleased to announce the availability of Hudson 1.396. The main purpose of this release was to correct the Update center used by Hudson to it's real home at the Hudson project. We did however, take the opportunity to do a full set of multi-platform regression and integration tests on the bits before release. As we move forward there will be more and more of this kind of testing baked into the release process so you can be confident about the quality of the code that is published.
Many of you may be aware that Andrew Bayer and Cloudbees (where Kohsuke Kawaguchi now works) have confirmed their intent to fork Hudson into a new community. We want the Hudson community to know that we have a dedicated team that includes people from Oracle, as well as some of our partners and current Hudson community members who will continue to build and grow the Hudson project and community. Your current installations will continue to run fine, and you won't need to change any code. You can still come to http://www.hudson-ci.org/ for all things Hudson.
As part of the fork, the current Hudson mailing list on google groups are being taken away. We will go back to using the Hudson mailing list on java.net that we were using up until early December. We will announce when that takes effect, sometime early this week. Also as part of the fork, the Hudson github project is being taken away. We have a mirror of the Hudson github repository (in git) on hudson.java.net where people can continue to check things in. We can discuss moving this back to github once we get things settled.
Our primary goals over the next months will be to fix high-priority bugs in the current edition of Hudson and formalize a development and release process that will allow users of Hudson to have more insight into what is being changed, why it is being changed, and when their bugs will be fixed. We will also continue the discussion that I started last month about what the next version of Hudson (v2) looks like. I look forward to working closely with the community on where to go from here.
The Hudson mailing lists and new forums are available on java.net. These replace the google-groups that were temporarily adopted due to problems with the old java.net infrastructure
$LastChangedDate: 2012-08-21 17:30:18 +0100 (Tue, 21 Aug 2012) $