Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing GitLab CI vs Rancher, the Slant community recommends GitLab CI for most people. In the question“What are the best Continuous Integration services with Docker support?” GitLab CI is ranked 1st while Rancher is ranked 11th. 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
Question Ranking
Pros
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.
Pro Web GUI cluster management
Intuitive and easy to use web gui.
Pro Mult-environment cluster system
- Cattle (Rancher default)
- Swarm
- Kubernetes
- Mesos
Pro Service catalog is easy
Rancher provides a catalog of application templates that make it easy to deploy complex stacks.
- Rancher certified catalog
- Community service catalog
Pro Self-service application stack for self-monitoring
Great contributions from the co community who build the service stack catalog.
One of them is the "Prometheus" template which deploys a collection of containers for monitoring a platform. It's capable of querying all aspects of your environment with some nice pre-built dashboards.
Pro Access control polices
Detailed role-based access control policies can be defined independently for each cluster.
Cons
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.
