Still, Oracle's Eclipse route for Hudson could serve to reunite the divided Hudson and Jenkins efforts, said IDC analyst Al Hilwa. "I would guess that this may surprise the Jenkins folks because there appears to have been a conspiracy theory that Oracle was going to do some bad thing with Hudson, like turn it into a commercial product. It may be time to come together again under one code base now that it's under the Eclipse Foundation."
Licensing and other changes expected for HudsonChanges afoot for Hudson include altering license requirements so the software is not bound to the Gnu LPGL (Lesser General Public License), which requires release of all code affected by the licensed code. Third-party libraries in Hudson use this "viral" license, which makes it difficult to repackage software with other software because it all must be released, said Oracle's Farrell. Corporations don't like this license requirement, he added. An Apache or Eclipse license is expected to replace LGPL.
Also planned are a capability for high availability and swapping out of a proprietary Web services stack with standard technology. Oracle has no commercial Hudson offering but does offer commercial support for it.
This article, "Oracle hands Hudson to Eclipse, but Jenkins fork seems permanent," was originally published at InfoWorld.com.
Sign up for Computerworld eNewsletters.