Skip to main content

Hudson 1.222, update center, and community updates

Posted by kohsuke on June 9, 2008 at 2:13 PM PDT

I just posted a new version of Hudson — 1.222. The most noteworthy change in this release is the update center for finding and installing Hudson plugins. Since the community developed plugins have always been one of Hudson's strong points, hopefully this will encourage the use/development of plugins more. As usual, if you discover issues or have usability improvements idea, please let me know.

To give you more incentive to switch to 1.222, there's another recent improvement in Hudson to considerably speed up the execution of the native Maven2 job types. The root cause of this bug was that I was carelessly using FilterOutputStream, which converts a bulk write "write(byte[])" into a series of byte write "write(int)". You can imagine how it could slow things down if Hudson writes to a network socket one byte at a time! Interestingly, FilterInputStream doesn't have this problem. So I guess someone really messed up FilterOutputStream implementation.

On community front, issue #1800 was filed on June 4th. Looking back #1700 was May 15th, #1600 was April 26th, #1500 was April 2nd. So I guess we are getting about 300 issues in 2 months, or 5 per day. I'll try to keep up with the pace, but it's harder now than before :-)

LinkedIn has also posted their JavaOne talk, which includes Hudson. They said they run a large scale Hudson cluster of 20+ nodes. The screenshot on slide 10 is also interesting. Speaking of JavaOne slides, you can also now see the "Using FindBugs in Anger" talk from Bill Pugh (AKA Mr.FindBugs), which also mentions Hudson quite favorably. There's also a DZone article about "what's your favorite java.net projects", and Hudson is mentioned there, too.

On another topic, Cliffano Subagio did a nice Firefox extension to monitor Hudson build results. I think a good feature would be for this extension to talk to Hudson so that you can go to your Hudson page, then add the projects from there without ever going through the configuration dialog.

Finally, for Japanese users, Trac Lightening now bundles Hudson instead of Continuum. Hudson being localized to Japanese should make this combination really nice.

Related Topics >>

Comments

Oh and removing the build timeout option DOES bypass this error, so it seems to be only related to that option.

FYI: I just upgraded to 1.222, created a new maven2-style build and am receiving the following message:

At revision 1786 Parsing POMs Discovered a new module com.fidelity.shares:shares shares Discovered a new module com.fidelity.shares:shares-parent shares-parent Discovered a new module com.fidelity.shares.build:shares-build shares-build Discovered a new module com.fidelity.shares:shares-domain shares-domain Discovered a new module com.fidelity.shares:shares-util-datainit shares-util-datainit Discovered a new module com.fidelity.shares:shares-dal shares-dal Discovered a new module com.fidelity.shares:shares-external shares-external Discovered a new module com.fidelity.shares:shares-infra shares-infra Discovered a new module com.fidelity.shares:shares-app-data shares-app-data Discovered a new module com.fidelity.shares:shares-app shares-app Discovered a new module com.fidelity.shares:shares-web shares-web FATAL: The plugin 'hudson.plugins.build_timeout.BuildTimeoutWrapper' still uses deprecated setUp(Build,Launcher,BuildListener) method. Update the plugin to use setUp(AbstractBuild, Launcher, BuildListener) instead. java.lang.AssertionError: The plugin 'hudson.plugins.build_timeout.BuildTimeoutWrapper' still uses deprecated setUp(Build,Launcher,BuildListener) method. Update the plugin to use setUp(AbstractBuild, Launcher, BuildListener) instead. at hudson.tasks.BuildWrapper.setUp(BuildWrapper.java:124) at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:293) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:231) at hudson.model.Run.run(Run.java:771) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:202) at hudson.model.ResourceController.execute(ResourceController.java:70) at hudson.model.Executor.run(Executor.java:82)

Let me know if you want me to open an issue for this.

Thanks! Leo

Great new feature, hudson keeps getting better!