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 Lets Fortnite Back In The App Store
21/05/2025

After 5 years of banishment, Fortnite is back in the US App Store.  Has Apple turned over a new leaf and is now playing nice? Probably not.



Early 2025 Java Conferences Galore Part 3
23/05/2025

We continue the lowdown on Java conferences. Having looked initally at sessions from three Voxxed events, last week we explored two Devoxx events and JavaOne. This week it's the turn of JCha [ ... ]


More News

Last Updated ( Tuesday, 07 June 2011 )