Knapsack Pro

Solano CI vs Heroku CI comparison of Continuous Integration servers
What are the differences between Solano CI and Heroku CI?

Solano CI

https://xebialabs.com/technology/solano-ci/

Heroku CI

https://www.heroku.com/continuous-integration
Unique feature

N/A

Heroku Flow

Type of product

N/A

SaaS

Offers a free plan

No

Their website only mentions a free trial

No (partial)

For CI only, the cost starts at $10 for pipeline, plus a variable amount depending on how long the build runs for (prorated per second). The servers used for CI cost $250 for a full month, which means you get about 3 hours for $1. For hosting, there's a free tier, limited to 1 web/1 worker with 512 MB RAM. One of the more annoying limitations is that free dynos are put into sleep mode after 30 min. of inactivity, which increases loading times considerably.

Predictable pricing

No

Very hard to get any information on pricing. It seems like they target enterprise clients only.

Yes

Clearly defined, offers a calculator.

Support / SLA

N/A

Yes

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

N/A

They mention that by paralellizing tests they get a huge performance boost (10x to 80x) but details are severly lacking.

Yes

Up to 16 nodes. You can ask Heroku support to enable up to 32 parallel dynos.

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

N/A

Containers support / Build environment

Yes

Yes

Builds run in isolation on new dynos (Heroku containers). Wide support via buildpacks: https://devcenter.heroku.com/articles/buildpacks

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 wording they use implies that this is possible.

Yes

Great visual overview built-in.

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

N/A

Yes

One of the more mature solutions for teams on the market, Heroku Teams is available for free for 1-5 people, and comes at a cost for 6+ team members: https://www.heroku.com/pricing#team-comparison. Allows setting roles and app-level permissions with ease.

Self-hosted option

N/A

No

Hosted plans / SaaS

N/A

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

The wording they use suggests that this is possible.

Yes

Very easy and intuitive process that allows defining a pipeline from code commit, to code review (review apps), user acceptance testing and production deployment, via Heroku Flow. Works best if the project is also hosted on Heroku.

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

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?

N/A

Probably not, considering how non-transparent this product is.

Yes

Wide array of 3rd party add-ons available via Heroku Elements: https://elements.heroku.com/addons. Custom buildpacks are also available for almost any stack you might be using (over 5500 buildpacks available at the moment)

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.

N/A

Yes

Although not specifically built in to Heroku, it's guaranteed that any Ruby specific need that might arise would be solved via add-ons, buildpacks or other integrations available.

Specific language support: JavaScript

N/A

Yes

Although not specifically built in to Heroku, it's guaranteed that any Javascript specific need that might arise would be solved via add-ons, buildpacks or other integrations available.

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

N/A

Yes

The strongest built-in integrations are with GitHub and Slack (ChatOps) but even allows integrating 3rd party CI servers in the workflow if you so require, among others.

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

Yes

Offers a feature rich API that allows CRUD operations on the most important features, such as promoting an app to production, or inspecting a specific pipeline.

Auditing

N/A

Yes

Additional notes

It seems like Solano CI has been retired, and the new solution is the XebiaLabs DevOps Platform, but which integrates Jenkins and Travis, among others: https://xebialabs.com/products/devops-platform-overview/

How to leverage Heroku CI to run your tests faster?

Introduction to Knapsack Pro Heroku add-on

Heroku CI parallelism integration

Start using Knapsack Pro with Solano CI or Heroku CI

Sign up and speed up your tests.

Get started free