Knapsack Pro

Buildkite pros & cons features of Continuous Integration server
Why choose Buildkite? See product overview

Buildkite

https://buildkite.com
Unique feature

Runs on own infrastructure, API

Type of product

SaaS

Offers a free plan

Yes

Free for open source projects and selected organizations

Predictable pricing

Yes

Clearly defined monthly and annual plans

Support / SLA

Yes

Depending on the plan, ranging from community support, all the way to an assigned Technical Manager, SLAs and live chat 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

Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs. You can run your tests in isolated Docker container per agent.

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

Yes

Run an unlimited number of concurrent agents, and an unlimited number of concurrent jobs

Containers support / Build environment

Yes

Since the agents run on your own infra, you're free to do whatever

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

The Buildkite UI features great vizualisations that feature build times, error rates, and more.

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

Yes

Self-hosted option

No

Hosted plans / SaaS

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

Pipelines are defined using an Yaml config file and allow for great flexibility in defining what each step of the process does.

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.

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

Integrations for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API). Growing number of community plugins: https://buildkite.com/plugins

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

You can find useful plugins like https://github.com/sj26/rspec-buildkite https://github.com/ticky/simplecov-buildkite etc

Specific language support: JavaScript

No

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

Yes

Integrations for GitHub, GitLab, BitBucket as well as SSO support (Google Suite, SAML, GraphQL API)

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

Yes

Great GraphQL API, allows building your own dashboard with ease

Auditing

Yes

Additional notes

Buildkite parallel agents and how to use them for CI parallelisation

Buildkite parallelism integration

Run tests in parallel on Buildkite in the optimal way and avoid bottleneck parallel jobs.

Get started free