When comparing CloudBees vs GitLab CI, the Slant community recommends GitLab CI for most people. In the question“What are the best hosted continuous integration services?” GitLab CI is ranked 6th while CloudBees is ranked 8th. 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 Great enterprise level support
Quick access to experts who are responsive, helpful, and friendly.
Pro Private and internal SVN and Git repositories
Support for both SVN and Git private repositories.
Pro Highly customisable
Jenkins is by far the most customizable solution on the market. And CloudBees is built on Jenkins. There are over 400 plugins to support building and testing virtually any project.
Pro Free for open source projects
CloudBees offers a solution for owners and developers of free and open source projects to be hosted and built by their service.
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 Java-only solution (without plugins)
Jenkins supports only software built with Java (unless you use plugins)
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.