Oracle acquired Sun, inherited Hudson, and the community split. Most developers created Jenkins. We stayed on Hudson longer than we should have — now it’s time to switch.
Migration Is Simple¶
Jenkins is a fork of Hudson — jobs, build history, and plugins are compatible. Stop Hudson, install Jenkins, copy the HOME directory, start it up. Some plugins need to be reinstalled. We recommend running both in parallel on a different port to verify everything first.
New Capabilities¶
Distributed builds (master-slave), an updated Plugin Manager, CLI for scripting jobs. A typical pipeline: SVN checkout, Maven build, JUnit report, Cobertura coverage, deploy to test, Selenium smoke tests. 12–15 minutes.
Security¶
LDAP authentication, Matrix Authorization, HTTPS via reverse proxy, the Audit Trail plugin. By default Jenkins is wide open — configure security immediately.
In Conclusion¶
If you’re still using Hudson, migrate. The entire ecosystem has moved to Jenkins.
Need help with implementation?
Our experts can help with design, implementation, and operations. From architecture to production.
Contact us