Oracle donates Hudson to Eclipse Foundation
May 4, 2011 —
(Page 3 of 3)
Related Search Term(s): Eclipse, Hudson, open source, Oracle
Al Hilwa, program director for application software development at IDC, said that Oracle was given a bad rap by the Jenkins split, and that this move validates its non-commercial intent for Hudson. “Eclipse is a good home for an enterprise-oriented product. I think there has been a lot of misinterpretation of Oracle's intent on this. I don't think they ever wanted to commercialize Hudson per se as much as make it more suitable for commercial and enterprise use and broaden its adoption,” he said.
The original split between Hudson and Jenkins came primarily over stability issues in the Hudson development process. Kawaguchi and the Hudson community favored extreme velocity over stable releases, and often skipped unit tests in their race for agility. In reaction to this, Oracle asserted control over the project's trademark, which cause the actual split.
But despite the whispers of Oracle's perceived bad intentions, Farrell said the project, under Oracle's leadership, has focused heavily on those issues, despite the limited period of time since the fork. “Since the fork, we've basically been spending our time on the stability and robustness of Hudson," he said.
"We added a test harness to the code, and we're working on the plug-ins. We changed the development cycle from randomly to every four weeks. This provides more predictability."
Oracle staffers will be leading the project at Eclipse, but the actual release cycles and project specifics will be decided through the Eclipse Foundation's Hudson team, which will include members of the commercial supporters of the project.
For its part, the Jenkins team has been focusing on these exact same goals. Two weeks ago, Kawaguchi said that he and the Jenkins community had already standardized on a stable release cycle that would push out one long-term supported version of Jenkins every few months. In addition, the Jenkins team had been going over plug-ins to ensure they were compatible with new builds of Jenkins, removing the need for users on older versions to upgrade simply to make plug-ins work.
In the end, the goals of both sides seem to be the same, and their efforts since the split have essentially been duplicates of each other. Jenkins has been addressing the exact concerns raised by Oracle, and with the proposed move to Eclipse, Hudson has now addressed the concerns of the Jenkins community.