Here’s the Deal

GitLab CI vs FinalBuilder

78 15

2 1

When comparing GitLab CI vs FinalBuilder, 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 FinalBuilder is ranked 32nd. 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

APIYes

Docker supportYes

GitYes (via GitLab)

LicenseMIT

MercurialNo

PlatformsLinux

SVNNo

Self-hostedYes

No specs yet!

Ranked in these QuestionsQuestion Ranking

Common Questions

What are the best continuous integration tools?

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
Well documented

One of the few websites with useful information about Code Signing with USB Tokens.

Pro
Pre-written scripts available

FinalBuilder has more than 600 pre-written scripts (known as actions) available. These actions help automate common tasks in a build process. This saves a lot of development time because you don't have to write those common tasks yourself.