When comparing Hudson vs GitLab CI, the Slant community recommends GitLab CI for most people. In the question“What are the best continuous integration tools?” GitLab CI is ranked 2nd while Hudson is ranked 27th. The most important reason people chose GitLab CI is:
All build setup are stored in .gitlab-ci.yml file, which is versioned and stored in the project. Like Travis do.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Most of the features found on Jenkins are also available for Hudson
Since Jenkins and Hudson share much of the same code base, they also share many of the same features. Hudson is also very easy to install: there is simply a single .war file which is run inside the root of the directory where Hudson will be installed.
Pro File based configuration
All build setup are stored in .gitlab-ci.yml file, which is versioned and stored in the project. Like Travis do.
Pro Free and open source
All of GitLab CI's code is open source and under the MIT license.
Pro Parallel builds lessen test times
Tests are parallelized across multiple machines in order to reduce test times considerably.
Pro Docker intergration
Good integration with Docker.
Pro Highly scalable
The tests of GitLab CI run parallel to each other and are distributed on different machines. Developers can add as many machines as they want or need, making GitLab CI highly scalable to the development team's needs.
Pro Quick setup for projects hosted on GitLab
Since it uses the GitLab API for setting up hooks, the setup of GitLab CI for projects hosted on GitLab can be done in one click.
Pro Kubernetes integration
Easy to test and deploy on Kubernetes.
Cons
Con Superseded by Jenkins
Jenkins is a fork from Hudson and therefore inherits most of it's source code. But Jenkins has far more commits and is a lot more active on the development side than Hudson. A lot of plugin developers have also chosen to support Jenkins and develop their product for Jenkins only.
Con Not lightweight
Not a lightweight solution, demanding and memory hungry.
Con Cost
Larger projects will need upgraded version
Con Security risks
Con Windows not supported
No Windows support, but it's possible to use a Bitnami stack.