When comparing GitLab CI vs Nevercode, 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 Nevercode is ranked 14th. 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 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 Ability to run tests on real devices
Simulating or emulating tests is good - actually testing on real hardware is better as you'll catch device (manufacturer) specific issues that would kill your app ratings in the wild.
Pro Multiple integrations to cover your needs
Simplifies the instant access to the latest state of your apps.
Pro Easy to setup
There's no configuration files to write, nothing to download or install, nothing to really configure. Setting it up takes basically only adding your Git repository and waiting for the clone, build and test to finish.
Pro Focused on mobile app development
It's dedicated to mobile platforms and supports Andorid, iOS native apps + a couple of cross-platform frameworks such as Cordova and Ionic.
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.