Oracle acquired and then supported Hudson Continuous Integration through 2016. Oracle no longer updates or supports Hudson. It was available free and open source under an MIT license, but it is no longer being developed, and is no longer available.
$0
per month
Jenkins
Score 8.4 out of 10
N/A
Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
N/A
Pricing
Hudson CI (discontinued)
Jenkins
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Hudson CI (discontinued)
Jenkins
Free Trial
No
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Hudson CI (discontinued)
Jenkins
Considered Both Products
Hudson CI (discontinued)
No answer on this topic
Jenkins
Verified User
Analyst
Chose Jenkins
Unfortunately I can't weight on decision making points since selection of Jenkins was made prior to me joining the company.
Though it has a few setup issues, once you are done with setup it works like charm so one time setup issues won't bother. Reporting, version tracking, debugging everything is helpful and more clear and it reduces effort, in our scenario our QA team integrated their script with Hudson so that after every release it will get triggered automatically and developers will know if there is any major issue.
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
The setup needs to be more user friendly, currently for first time users CI doesn't provide more guidelines.
JMeter tool can be integrated but it's not easy, user has to follow and do research before setup. A simpler way would help make the process more user friendly.
Selenium tool like JMeter can be integrated, if its Webservice it's easy but for UI automation integration not enough information is provided.
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
Oracle CI in terms of setup lags behind all above products, but then its use is also limited to release management so we can't really compare. Majority of organizations have dedicated team to help with CI Process so they take care of managing all jobs and setup.
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
