Moving on to Jenkins

So in case you haven’t heard, there was some drama between the Hudson community and Oracle. I won’t go into detail as there are plenty of articles about what went on.

All of the issues that were opened on the Hudson Jira for the Perforce plugin are still open, but I’m unassigning those that are assigned to me. I’ll continue maintaining the Perforce plugin against Jenkins, so bugs will be tracked there, and any fixes I make will be made in the Jenkins repository. Note that the Jenkins version will still work for Hudson until Oracle/Sonatype and/or the Jenkins Community decide to break cross-compatibility.

I’m not saying the Hudson version is dead, just that it doesn’t have an active maintainer. Someone may take over maintaining it, but as far as I know, only one person has been assigned to working on Hudson and the hundreds of plugins written for it.

2 thoughts on “Moving on to Jenkins

    1. I think plenty of them are valid to a certain degree. Though I believe their PR is mostly just attempting to gain a strong user-base so they can monetize it in the future. Oracle wouldn’t give up the Hudson trademark in order to keep the community around, claiming it “wasn’t a fair deal” for them, so clearly the bottom line is their only priority.

Leave a Reply

Your email address will not be published. Required fields are marked *