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


ACM Adopts Open Access Publishing Model
05/04/2024

ACM, the Association for Computing Machinery, the professional body for computer scientists, has relaunched Communications of the ACM, the organization’s flagship magazine, as a web-first  [ ... ]



Falco On Track To Version 1.0.0
02/04/2024

Falco is a cloud native runtime security tool for the Linux operating system, designed to detect abnormal behavior and warn of potential security threats in real-time. Now it's about to release its fi [ ... ]


More News

Last Updated ( Tuesday, 07 June 2011 )