Concourse vs Packer: 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; Packer: Create identical machine images for multiple platforms from a single source configuration. Packer automates the creation of any type of machine image. It embraces modern configuration management by encouraging you to use automated scripts to install and configure the software within your Packer-made images.
Concourse and Packer are primarily classified as "Continuous Integration" and "Infrastructure Build" tools respectively.
"Real pipelines" is the top reason why over 8 developers like Concourse, while over 24 developers mention "Cross platform builds" as the leading cause for choosing Packer.
Concourse and Packer are both open source tools. Packer with 9.03K GitHub stars and 2.46K forks on GitHub appears to be more popular than Concourse with 3.92K GitHub stars and 472 GitHub forks.
Conceptboard, Instacart, and SendGrid are some of the popular companies that use Packer, whereas Concourse is used by Starbucks, DigitalOcean, and HelloFresh. Packer has a broader approval, being mentioned in 113 company stacks & 20 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.