Bamboo vs Concourse

Overview

Bamboo

Stacks504

Followers549

Votes17

Concourse

Stacks254

Followers393

Votes54

GitHub Stars7.6K

Forks870

Bamboo vs Concourse: What are the differences?

Introduction

Bamboo and Concourse are two popular continuous integration and continuous deployment (CI/CD) tools used by developers for automating the software development process. Despite serving the same purpose, there are key differences that set them apart.

Pipeline Configuration: Bamboo uses a graphical user interface for defining pipelines, whereas Concourse uses a declarative code (YAML) approach, making pipeline configurations more code-centric and easier to version control.
Scalability: Bamboo is known to struggle with scalability when handling a large number of concurrent builds, whereas Concourse is designed to be highly scalable and distributed, making it more suitable for large and complex projects.
Resource Utilization: Concourse excels in resource utilization by running each task in its own container, ensuring efficient resource isolation and management, whereas Bamboo may share resources among tasks leading to potential bottlenecks.
Dependency Management: Bamboo relies on plugins for integrating with different tools and services, which may create compatibility issues, while Concourse offers built-in resource types for easier dependency management without the need for extensive plugin support.
Community Support: Concourse has a strong open-source community contributing to its development and providing support, whereas Bamboo, being a proprietary tool by Atlassian, may have limited community-driven updates and enhancements.
User Interface: Bamboo offers a visually appealing and user-friendly interface, making it easier for less technical users to navigate and use, while Concourse focuses more on functionality over aesthetics, catering to a more technical audience.

In Summary, Bamboo and Concourse differ in pipeline configuration, scalability, resource utilization, dependency management, community support, and user interface, all of which contribute to their suitability for different development environments and projects.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Bamboo, 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

Bamboo	Concourse
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.	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 -	GitHub Stars 7.6K
GitHub Forks -	GitHub Forks 870
Stacks 504	Stacks 254
Followers 549	Followers 393
Votes 17	Votes 54
Pros & Cons
Pros 10 Integrates with other Atlassian tools 4 Great notification scheme 2 Great UI 1 Has Deployment Projects Cons 6 Expensive 1 Low community support 1 Bad integration with docker 1 Bad UI	Pros 16 Real pipelines 10 Containerised builds 9 Flexible engine 6 Fast 4 Open source Cons 2 Fail forward instead of rollback pattern
Integrations
Confluence Jira Bitbucket HipChat	No integrations available

What are some alternatives to Bamboo, 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.

Related Comparisons

Bamboo vs Concourse: What are the differences?

Introduction

Pipeline Configuration: Bamboo uses a graphical user interface for defining pipelines, whereas Concourse uses a declarative code (YAML) approach, making pipeline configurations more code-centric and easier to version control.
Scalability: Bamboo is known to struggle with scalability when handling a large number of concurrent builds, whereas Concourse is designed to be highly scalable and distributed, making it more suitable for large and complex projects.
Resource Utilization: Concourse excels in resource utilization by running each task in its own container, ensuring efficient resource isolation and management, whereas Bamboo may share resources among tasks leading to potential bottlenecks.
Dependency Management: Bamboo relies on plugins for integrating with different tools and services, which may create compatibility issues, while Concourse offers built-in resource types for easier dependency management without the need for extensive plugin support.
Community Support: Concourse has a strong open-source community contributing to its development and providing support, whereas Bamboo, being a proprietary tool by Atlassian, may have limited community-driven updates and enhancements.
User Interface: Bamboo offers a visually appealing and user-friendly interface, making it easier for less technical users to navigate and use, while Concourse focuses more on functionality over aesthetics, catering to a more technical audience.

Bamboo vs Concourse

Overview

Bamboo vs Concourse: What are the differences?