Hudson vs. Jenkins

In my last blog post, I mentioned, that we are still using Hudson instead of the new community fork Jenkins. You can ask now why we are doing this. This is mainly a personal decision, and it is not about Oracle and their „relationship“ to open source communities, but more about Sonatype and their involvement in the future of Hudson (see blog post here, here and here). I think that if the leader of Maven (Jason van Zyl) is investing time and resources into the hudson project, it is definitly worthwhile to stay there. Lets see if this is going to work out.

For more information about this story please also visit:

Hudson and Jenkins now on GitHub
Hudson vs. Jenkins – more thoughts

Ein Gedanke zu „Hudson vs. Jenkins

  1. Pingback: » Hudson and Jekins now on GitHub

Kommentare sind geschlossen.