Test Kitchen vs Concourse | What are the differences?

Overview

Test Kitchen

Stacks197

Followers45

Votes15

GitHub Stars1.9K

Forks582

Concourse

Stacks260

Followers393

Votes54

GitHub Stars7.6K

Forks870

Concourse vs Test Kitchen: What are the differences?

Concourse: Pipeline-based CI system written in Go. Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control; Test Kitchen: Integration tool for developing and testing infrastructure code and software on isolated target platforms. Test Kitchen has a static, declarative configuration in a .kitchen.yml file at the root of your project. It is designed to execute isolated code run in pristine environments ensuring that no prior state exists. A plugin architecture gives you the freedom to run your code on any cloud, virtualization, or bare metal resources and allows you to write acceptance criteria in whatever framework you desire.

Concourse and Test Kitchen belong to "Continuous Integration" category of the tech stack.

"Real pipelines" is the primary reason why developers consider Concourse over the competitors, whereas "Automated testing" was stated as the key factor in picking Test Kitchen.

Concourse and Test Kitchen are both open source tools. It seems that Concourse with 3.99K GitHub stars and 482 forks on GitHub has more adoption than Test Kitchen with 1.62K GitHub stars and 543 GitHub forks.

🔥 Trending in Continuous Integration on StackShare

TeamCity Pipelines Continuous Integration

JetBrains' next gen CI/CD with self-optimizing pipelines

Try it View Docs Alternatives

Try

0

3

Advice on Test Kitchen, Concourse

veera

Jan 27, 2020

Needs advice

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

521k views521k

Comments

Detailed Comparison

Test Kitchen	Concourse
Test Kitchen has a static, declarative configuration in a .kitchen.yml file at the root of your project. It is designed to execute isolated code run in pristine environments ensuring that no prior state exists. A plugin architecture gives you the freedom to run your code on any cloud, virtualization, or bare metal resources and allows you to write acceptance criteria in whatever framework you desire.	Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.
Statistics
GitHub Stars 1.9K	GitHub Stars 7.6K
GitHub Forks 582	GitHub Forks 870
Stacks 197	Stacks 260
Followers 45	Followers 393
Votes 15	Votes 54
Pros & Cons
Pros 6 Automated testing 4 Detect bugs in cook books 2 Integrates well with vagrant 2 Can containerise tests in Docker 1 Integrates well with puppet	Pros 16 Real pipelines 10 Containerised builds 9 Flexible engine 6 Fast 4 Open source Cons 2 Fail forward instead of rollback pattern

What are some alternatives to Test Kitchen, Concourse?

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.