Jenkins determined to go its own way
Written by Alex Armstrong   
Tuesday, 07 June 2011

The Jenkins community seems adamant that it doesn't want to follow a formal process. This effectively rules out any involvement with the Eclipse Foundation and any prospect of reconciliation with Hudson.

 

Now that Oracle has decided to transfer Hudson to the Eclipse Foundation there was some speculation as to whether the Jenkins fork could be persuaded to rejoin the original project.

The answer to this appears to be a resounding no.

At its most recent online meeting the question of possible reconciliation with Hudson as part of Hudson's move to Eclipse was discussed.

However, the Jenkin's community's strong desire to remain at GitHub, to not follow any formal development process, including having to follow a specific means to bring new committers on board, and to release weekly effectively prevent Jenkins from moving either to Eclipse nor to the Apache Foundation, which has also be proposed as a home for Jenkins. 

 

hudson

 

 

Further Information

Hudson becomes Jenkins

Oracle to let go of Hudson

 

Banner


Apple Updates Developer Tools
16/06/2025

Apple has announced a range of improvements to its developer tools at this year's WWDC (WorldWide Developers Conference), including a new foundation models framework and updates to Xcode, Apple's  [ ... ]



The Impact Of Code Club
25/06/2025

In the era of AI, the Raspberry Pi Foundation takes the view that learning how to create with technology has never been more important. Last year it revamped its Code Club network of free co [ ... ]


More News

Last Updated ( Tuesday, 07 June 2011 )