+ 1

What is Hudson?

It monitors the execution of repeated jobs, such as building a software project or jobs run by cron. Among those things, currently it focuses on the two jobs
Hudson is a tool in the Continuous Integration category of a tech stack.
Hudson is an open source tool with GitHub stars and GitHub forks. Here’s a link to Hudson's open source repository on GitHub

Who uses Hudson?


9 developers on StackShare have stated that they use Hudson.

Hudson Integrations

JavaScript, HTML5, Java, Experitest, and psake are some of the popular tools that integrate with Hudson. Here's a list of all 5 tools that integrate with Hudson.

Hudson's Features

  • Easy installation
  • Easy configuration
  • Change set support
  • Permanent links
  • RSS/E-mail/IM Integration
  • After-the-fact tagging
  • JUnit/TestNG test reporting
  • Distributed builds
  • File fingerprinting
  • Plugin Support

Hudson Alternatives & Comparisons

What are some alternatives to Hudson?
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Travis CI
Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.
GitHub Actions
It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
GitLab CI
GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
See all alternatives

Hudson's Followers
17 developers follow Hudson to keep up with related blogs and decisions.