Knapsack Pro

Github Actions vs Gitlab CI comparison of Continuous Integration servers
What are the differences between Github Actions and Gitlab CI?

Github Actions

https://github.com/features/actions

Gitlab CI

https://about.gitlab.com/product/continuous-integration/
Unique feature

Best GitHub integration possible

AutoDev Ops / Allows keeping code management and CI in the same place

Type of product

SaaS / On Premise

SaaS / On Premise

Offers a free plan

Yes

The on premise plan (not yet available) will be free, 2000 build minutes included in the free cloud plan. Completely free plan for open source projects.

Yes

Very generous free plans for both the SaaS version as well as the on premise version.

Predictable pricing

Yes (partial)

While it's clear what the cost is (priced per build-minute), figuring out costs can be a hassle, especially as the price can vary quite a bit depending on commits to the project. One advantage for GitHub Actions is that the tiers define a maximum amount of minutes, so it's easier to predict the final cost. You can also purchase aditional runners with pricing dependent on the platform (MacOS, Linux, Windows)

Yes

Clear and affordable pricing for both SaaS and self-hosted versions.

Support / SLA

Yes

Community support available for any tier, unclear at what point and if dedicated support is available. Safe to assume that eneterprise clients can access technical support.

Yes

All paid plans include next business day support.

Paralellism
Every CI servers tends to address this differently (parallel, distributed, build matrix). Some of it is just marketing, and some is just nuance. For this table, parallel means that tasks can be run concurrently on the same machine, distributed means that tasks can be scaled horizontally, on multiple machines
How to split tests in parallel in the optimal way with Knapsack Pro

Yes

Matrix builds allow concurrent jobs, even multi-platform.

Yes

Easily configure jobs you want to be run in parallel via the YML config file (gitlab-ci.yml)

Distributed builds
distributed means that tasks can be scaled horizontally, on multiple machines
How to split tests in parallel in the optimal way with Knapsack Pro

N/A

No specific mention, but given the fact that tasks can be run on multiple platforms, it's likely that distributed builds are also available.

Yes

Containers support / Build environment

Yes

Linux, macOS, Windows, and containers, or run directly in a VM.

Yes

The Docker Container Registry is integrated into GitLab by default

Analytics / Status overview
Analytics and overview referrs to the ability to, at a glance, see what's breaking (be it a certain task, or the build for a specific project)

Yes

Minimal status overview definitely available, with live logs and GitHub integration. Unclear how far it goes.

Yes

Management support
How easy is it to manage users / projects / assign roles and permissions and so on

N/A

Unclear from the available documentation

Yes

Self-hosted option

Yes

Coming soon, not available yet.

Yes

Hosted plans / SaaS

Yes

Yes

Build pipelines
A continuous delivery pipeline is a description of the process that the software goes through from a new code commit, through testing and other statical analysis steps all the way to the end-users of the product.

Yes

Called GitHub Action Workflows, they are defined in separate Docker containers, using the YAML syntax (they used to support HCL, but they're migrating away from that)

Yes

Defined via YML config files

Reports
Reports are about the abilty to see specific reports (like code coverage or custom ones), but not necesarily tied in into a larger dashboard.

N/A

Unclear from the available documentation

Yes

Ecosystem
Besides the official documentation and software, is there a large community using this product? Are there any community-driven tools / plugins that you can use?

Yes

Thanks to the large following, GitHub Actions already enjoys a wide varierty of available pre-made workflows, which you can browse right on the homepage: https://github.com/features/actions

Yes

Specific language support: Ruby
Some CI servers have built-in support for parsing RSpec or Istanbul output for example and we mention those. Some others make it even easier by detecting Gemfiles or package.json and automate parts of the process for the developer.

Yes

Unclear how, but they mention Ruby support specifically on the homepage

Yes

Although not built into GitLab CI by default, the Docker support allows solving any Ruby specific need that may arise.

Specific language support: JavaScript

Yes

Unclear how, but they mention Javascript (Node.js) support specifically on the homepage

Yes

Although not built into GitLab CI by default, the Docker support allows solving any Javascript specific need that may arise.

Integrations
1st party support for common tools (like Slack notifications, various VCS platforms, etc)

Yes

Integrations made possible via the shared third party workflows available (AWS, Azure, Zeit, Kubernetes and many more)

Yes

Plenty of third party integrations available throughout GitLab, most notably Kubernetes and GitHub, but also plenty of others: https://docs.gitlab.com/ee/integration/README.html

API
Custom integreation is available, via an API or otherwise, it's mentioned separately as it allows further customization than any of the Ecosystem/Integration options

N/A

Unclear at the moment, but assume GitHub Actions will be integrated with the GitHub GraphQL API (one of the more mature GraphQL API implementations available)

Yes

Provides a REST API and a (new) GraphQL API, with plans to maintain the GraphQL API only going forward. Allows doing almost anything that can be done via the interface, at least in terms of CI needs.

Auditing

N/A

Yes

Additional notes

The Auto DevOps feature might be interesting to people looking for a very hands-off experience with getting a CI/CD process up and running https://docs.gitlab.com/ee/topics/autodevops/

GitHub Actions testing Ruby on Rails with RSpec and parallel jobs (matrix feature)

How to run Jest tests on GitHub Actions - JS parallel jobs with matrix feature (NodeJS YAML config)

GitHub Actions Cypress.io E2E testing parallel jobs with matrix feature (NodeJS YAML config)

GitLab CI parallelisation - how to run parallel jobs for Ruby & JavaScript projects

Github Actions parallelism integration

Gitlab CI parallelism integration

Start using Knapsack Pro with Github Actions or Gitlab CI

Sign up and speed up your tests.

Get started free