Solano CI vs Concourse CI

Solano CI offers safe parallel execution and dynamic task distribution which finish builds automatically and up to 80x faster.

Solano CI offer highly-responsive customer support, while extensive documentation and tutorial materials help customers keep Solano CI running in optimal condition.

Solano CI has a CLI interface available, making it less time-consuming to work with and allowing for remote usage over the internet.

Solano CI supports popular languages seamlessly such as Java, C/C++, Python, Ruby, Javascript, Scala, PHP, and Go. It also works with Mercurial, Git, and Perforce via Git Fusion.

Solano CI provides cost-effective and resizable capacity. It also manages time-consuming systems' administration tasks, freeing you up to focus on your applications and business.

Solano CI has a simple dashboard view that allows you to see test results in real-time, providing all relevant system output for failed tests.

Build Pipelines allow users to chain together multiple Solano CI sessions into a Continuous Deployment pipeline. Each step represents a separate session, so each can run with its own set of parallel workers.

Debugging on remote build agents is a nightmare (especially without isolated builds). Concourse CI can be run locally. When there are problems with the pipeline definition, it can be run and debugged locally. That means it takes less time to find and fix problems.

Resources are to Concourse as plugins are to Jenkins. In other words, resources allow Concourse CI to do just about any work necessary in a build. But resources follow a "service provider interface" that makes them easy to build in any language (not just JVM languages) and have a clearly defined computing model, built for composition. Resources don't clutter UI or tax performance.

BOSH is an open source tool for release engineering, deployment, lifecycle management, and monitoring of distributed systems. Since Concourse CI is built on top of BOSH, Concourse can scale across many servers or be run in the Cloud.

Build isolation keeps workers "clean". There's no configuration drift of agents. Or flaky interactions between build jobs.

Visual pipeline view makes it clear what the automation does. Simple navigation to logs makes it easy to understand what happened in a build.

Concourse defines three primitives that, together, can express arbitrary features and pipelines.