[Lewisham]

For a little bit of context, I've done some plug-in commits in my time and met the important guys in this project.

Unlike some categorizations in the comments here, I wouldn't say that the devs are anti-Oracle, they're pro-Hudson. I think they've tried to work with Oracle as much as they can, and certainly shown more patience than I think I would have. Once it became clear Oracle didn't necessarily have Hudson's best intentions at heart, things started to go downhill.

Oracle has not been especially communicative, and it's not especially respectful to literally pull the plug on a project's infrastructure without decent prior warning. For all the failings of java.net, when it was run by Sun, they did at least make sure people knew ahead of time of planned outages (the unplanned we don't discuss).

From my POV, it looks like Oracle has two heads: there's the nasty, legal head that is happy to sue everyone with Sun's patent arsenal, and there's the plain incompetent head that doesn't have a clue how to interact with open-source development. We're seeing the latter here, and I guess the community is just fortunate that Hudson isn't patent-encumbered (as far as I know). I don't think there's any particular malice here, just a general level of incompetence and hubris.

[j_baker]

I agree. This sounds like it's just a classic case of Not Invented Here syndrome more than anything else. I've been in a similar situation before: a big company is insistent that everyone use their own internal infrastructure because they're skeptical of the reliability of others' networks. Of course, they ignore the fact that their network is terribly unreliable in making this decision.