Al igual que OpenSolaris y OpenOffice, Hudson se bifurca y nace Jenkins.

El día de ayer surgió esta noticia. Hudson, la herramienta más utilizada para Continous Integration se ha bifurcado debido al futuro incierto que tiene junto a Oracle. Nace un fork bajo el nombre de Jenkins.

Hace un rato me llegó esto de parte de Justin Kestelyn de Oracle:

JUG Leaders and Java Champions,

I just want to make you aware of this announcement from the Hudson team (Specifically, Susan Duncan on that team):

All, Now that the fork has happened, we can start to put this saga
behind us and get back to work. At this point we want to reassure you
that Hudson-ci continues and has our full commitment. We have a
dedicated team that includes people from Oracle, as well as some of our
partners and current Hudson community members who will continue to
build and grow the Hudson project and community.

Your current installations will continue to run fine, and you won't
need to change any code. You can still come to the newly designed
for all things Hudson. Later this week we
will announce a new release of Hudson. This release will primarily
de-couple the Hudson code from the old auto-update center back to the
official Hudson update center. If you use auto-update with version
1.395 or earlier, the auto-update will take you to a site that will ask
you to install jenkins which will remove your Hudson installation. If
you want to continue to use Hudson, you should install Hudson v1.396 or
later when it becomes available later this week

We have reverted to using the Hudson mailing lists on java.net but are
open to discussion about creating a new google group. In addition
java.net provides a forum that can be used to discuss user problems,
ideas and other issues. There is a link to get to that at the top of
the hudson-ci.org website. I would urge you to engage with other
users.

Also as part of the fork, the Hudson github project has been taken
away. We have a current git repository on hudson.java.net where people
can continue to check things in. We can also discuss moving this back
to github once we get things settled. If you are interested in getting
involved, and are not already registered as a committer, please let us
know. This is your opportunity to help shape the future of Hudson.

Our primary goals over the next months will be to fix high-priority
bugs in the current edition of Hudson and formalize a development and
release process that will allow users of Hudson to have more insight
into what is being changed, why it is being changed, and when their
bugs will be fixed. We will also continue the discussion that Winston
started last month about what the next version of Hudson (v2) looks
like. I look forward to working closely with the community on where to
go from here.

As always, is home URL involved. You can also follow @hudsonci on Twitter for Hudson news.

El sitio del nuevo fork es:

¿Tú cuál usarás?

Salute.