When comparing Buddy vs GitLab CI, the Slant community recommends GitLab CI for most people. In the question“What are the best hosted version control services?” GitLab CI is ranked 7th while Buddy is ranked 9th. 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 Easy Pipeline Setups
The ease to setup custom pipelines are amazing, can easily various settings quickly and then be ready to deploy.
Pro Multitude of Actions
Almost any action you can need and think of is already here, making it easy for you to setup your pipeline.
Pro Nice material design
The design is minimalistic and based on today's standarts on material design. It uses colors which are pleasing to the eye and displays the information in an ordered way. The main view shows the latest activity sorted in a chronological order, displaying commits and pushes.
Every repo has it's own view, on the top there's the repo's name and a dropdown which displays the current branch with the ability to change to another branch or to create a new one.
On the right there's a vertical menu with links to add a new file, show the history or to download the current repository.
Pro Free private repositories
Private repositories are free. Although they are free for up to 3 repos and each repository must be less than 100MB in size.
Pro Lots of integrations, for example discord, slack
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 Unlimited private repositories are not free
To have more than three repositories and to bypass the limit of 100MB per repository it's not free. It costs $3/month.
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.