What if Hudson loses its plugins?

http://java.net/projects/hudson/lists/dev/archive/2011-02/message/117

by tomeast • 15 years ago

101 26 15 years ago

eitland• 15 years ago

Good stuff! Apparently even MS responds to inconvinient stuff entering HN front page. (http://blogs.msdn.com/b/tims/archive/2011/02/15/a-modern-bro...)

Now lets see how Oracle responds.

masklinn3• 15 years ago

Correlation is not causation. The post they responded to is big, by Mozilla and made the rounds.

I see no mention of HN, on which basis do you infer they responded because it was on HN's front page?

limmeau• 15 years ago

Is that a comment on Hudson/Jenkins plugins? (Puzzled look)

ximeng• 15 years ago

"It seems that others share this view. The discussion on YCombinator starts with this comment" - from the article.

cookiecaper• 15 years ago

MS's post there is embarrassing. They responded with only marketing buzzwords, mentioning only the vaguest technical points that don't really mean much by themselves. They proceed to quote two people that like IE.

We know Oracle won't do better than that if they respond (which I don't think they will), but it's just a little sad.

selectnull• 15 years ago

I applaud the willingness of Jenkins developers to stand up against Oracle. I wish you all the best guys!

Tyrant505• 15 years ago

http://i.imgur.com/F8FIb.jpg -fixed the menu ;)

ojosilva• 15 years ago

Could you also fix the tags underneath each section? They all say "java" in big letters for some strange reason.

bhrgunatha• 15 years ago

Is there any standard or most common orientation for vertical text - somehow it seems off to me reading bottom-to-top rather than top-to-bottom.

jrockway3• 15 years ago

There's not, in English anyway, but most books these days are designed to have the spine text upright when the book is stacked with the cover facing up. Not surprisingly, Oracle went with the opposite.

I believe there is a Wikipedia article that discusses the direction of text on book spines in detail, but I can't recall the name of it.

fierarul3• 15 years ago

This was as overdramatic as I have learned to expect ever since the whole fork thing started.

Hudson cannot "lose" its plugins right now because there are no signifiant API/ABI changes between the two forks.

Also, I wonder how much these plugins are actually used? I've only installed mercurial on my servers and I'm pretty sure that will continue to be supported on any fork. As for the rest, as long as they are open-source they can always be forked too.

It's getting a bit tiresome to watch this unfold -- can't the new Jenkins community just go on with their life and make their fork as good as they can? They got what they wanted -- why the constant need to somehow prove something to Oracle?

Having such a big face-less enemy is the best thing that happened to this community as it gaves them something to bond against. I'm curios what will happen when the rush is gone.

buster• 15 years ago

As a developer i wouldn't want to get spammed by users for a software i don't support anymore. It's only the devs unsubscribing. Nothing wrong here. Also, i think to request the removal in a public mailinglist is fine, too. As a user of one of those plugins i'd like to know what happened when i find the plugin not working anymore.

danik• 15 years ago

I don't know. I mean, if you feel Oracle treated you like shit you can behave like this if you want to. To be the bigger man can be noble and all but blowing off some steam is pretty healthy.

thibaut_barrere• 15 years ago

It's a delayed issue: as time will go, the chances to see API changes will become more likely.

fierarul3• 15 years ago

Yes, but it's too premature to think about it.

Even if API changes do happen popular plugins will either get patched to support both APIs or some parallel plugins will emerge.

ehutch79• 15 years ago

Part of it is PR. If you're getting screwed by a company, you need to make sure people know.

The grunts in the field need to have a lot to backup any claims that company x will screw their organization over. If they don't have a solid laundry list of examples, it will never get past the 'steak and strippers' sales pitch.

By making this public the could save many, many, companies from being dependent on technology that oracle has crippled.

fierarul3• 15 years ago

I don't think the answer is as simple because we don't know Oracle's side so to speak and from what I've read, I don't see where all the evil-ness is.

So, I don't know who's getting screwed here, but I'm siding with Oracle.

I wonder how would you feel to pay somebody full time for years to work on a project and then, when they leave your company, they fork the project and try their best to alienate all your users. Now, I've heard of burning bridges, but this takes it to a whole new level. If you think about it now, what exactly did Sun pay for when Kohsuke was working as an employee on Hudson? Apparently nothing.

ataggart• 15 years ago

Could someone please provide some context?

jrockway3• 15 years ago

Oracle, the owner of the Hudson trademark, said that Hudson could not move itself to github even though the community wanted to. Oracle said the community would face legal action if they did the move anyway. The Hudson community responded by abandoning Hudson and renamed the Free code to Jenkins to avoid Oracle's trademark. Now all the plugin developers that previously wrote "Hudson" plugins are saying that they are now writing "Jenkins" plugins, and that Oracle has effectively killed one of their more popular open source projects.

Oooooops.....

Luyt• 15 years ago

Oracle strikes back with:

"You'll see more code coming from Oracle as well now that we are mostly caught up after having parts of the Hudson infrastructure stolen away from us during the Jenkins fork."

http://java.net/projects/hudson/lists/dev/archive/2011-02/me...

oozcitak• 15 years ago

- Hudson is a free continuous integration (CI) tool written by Kohsuke Kawaguchi in Sun. [1]

- Oracle took control of Hudson as part of their Sun acquisition.

- Hudson devs wanted to move the infrastructure from Java.net to Github due to frustration with Java.net.

- Oracle objected the move to Github. Oracle said they owned the trademark to the Hudson name and the devs were free to fork under a different name if they wanted to. [2]

- Devs forked Hudson as Jenkins. [3]

- BONUS: Hudson also moved to Github. [4]

[1] http://en.wikipedia.org/wiki/Hudson_(software)

[2] http://groups.google.com/group/hudson-users/msg/cf0d72a7d97f...

[3] http://jenkins-ci.org/content/jenkins

[4] http://java.net/projects/hudson/lists/dev/archive/2011-02/me...

jrockway3• 15 years ago

Tichy• 15 years ago

I haven't really followed it all, but my guess would be: Hudson is now Jenkins, and Hudson is dead. Except for a name change, no biggie.

What if Hudson loses its plugins?

Related Stories