AWS CodePipeline vs Concourse

Overview

AWS CodePipeline

Stacks551

Followers933

Votes30

Concourse

Stacks254

Followers393

Votes54

GitHub Stars7.6K

Forks870

AWS CodePipeline vs Concourse: What are the differences?

Introduction:

AWS CodePipeline is a fully managed continuous delivery service that helps automate the release process for application updates. On the other hand, Concourse is an open-source continuous integration and continuous delivery (CI/CD) platform that enables teams to build, test, and deploy software efficiently. Now, let's explore the key differences between AWS CodePipeline and Concourse.

Architecture: AWS CodePipeline follows a centralized architecture, where the pipeline configuration is maintained within the CodePipeline service. In contrast, Concourse follows a decentralized architecture, where pipeline configuration is defined in a YAML file that resides in a source code repository.
Integration with AWS Services: AWS CodePipeline seamlessly integrates with various AWS services like AWS CodeBuild, AWS CodeDeploy, and AWS Elastic Beanstalk for building, testing, and deploying applications. On the other hand, while Concourse is a flexible CI/CD platform, it requires additional configuration and integration efforts to work with AWS services.
Visibility and Monitoring: AWS CodePipeline provides a comprehensive web dashboard that offers visibility into the entire pipeline, including the current status, execution details, and historical trends. In contrast, Concourse offers a web-based user interface, but the level of visibility and monitoring depends on the additional monitoring tools and configurations implemented by the user.
Ease of Use: AWS CodePipeline is designed to be user-friendly, with a simple and intuitive console interface for pipeline creation and management. Concourse, being an open-source tool, requires more configuration and setup efforts, making it relatively more complex to use compared to AWS CodePipeline.
Community Support: AWS CodePipeline is a fully supported service provided by Amazon Web Services (AWS). As a result, users can benefit from comprehensive documentation, official support channels, and frequent updates. On the other hand, Concourse being an open-source project, the level of support and documentation might vary depending on the user community and contributors.
Pricing: AWS CodePipeline offers a pay-per-use pricing model, where users only pay for the resources they use in their pipelines, such as build minutes, deployment actions, and storage. Concourse, being an open-source tool, is free to use, but users need to allocate resources and infrastructure to run and maintain their Concourse server.

In Summary, AWS CodePipeline provides a centralized and user-friendly continuous delivery service with seamless integration with AWS services, while Concourse offers a flexible, decentralized CI/CD platform that requires additional setup effort and may have varying levels of community support.

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 AWS CodePipeline, 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

AWS CodePipeline	Concourse
CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.	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.
Workflow Modeling;AWS Integrations;Pre-Built Plugins;Custom Plugins;Declarative Templates;Access Control	-
Statistics
GitHub Stars -	GitHub Stars 7.6K
GitHub Forks -	GitHub Forks 870
Stacks 551	Stacks 254
Followers 933	Followers 393
Votes 30	Votes 54
Pros & Cons
Pros 13 Simple to set up 8 Managed service 4 GitHub integration 3 Parallel Execution 2 Automatic deployment Cons 2 No project boards 1 No integration with "Power" 365 tools	Pros 16 Real pipelines 10 Containerised builds 9 Flexible engine 6 Fast 4 Open source Cons 2 Fail forward instead of rollback pattern
Integrations
Runscope Amazon S3 GitHub Jenkins CloudBees BlazeMeter Ghost Inspector AWS Elastic Beanstalk Amazon EC2	No integrations available

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

Buddy

Git platform for web and software developers with Docker-based tools for Continuous Integration and Deployment.

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.

Related Comparisons

AWS CodePipeline vs Concourse: What are the differences?

Introduction:

Architecture: AWS CodePipeline follows a centralized architecture, where the pipeline configuration is maintained within the CodePipeline service. In contrast, Concourse follows a decentralized architecture, where pipeline configuration is defined in a YAML file that resides in a source code repository.
Integration with AWS Services: AWS CodePipeline seamlessly integrates with various AWS services like AWS CodeBuild, AWS CodeDeploy, and AWS Elastic Beanstalk for building, testing, and deploying applications. On the other hand, while Concourse is a flexible CI/CD platform, it requires additional configuration and integration efforts to work with AWS services.
Visibility and Monitoring: AWS CodePipeline provides a comprehensive web dashboard that offers visibility into the entire pipeline, including the current status, execution details, and historical trends. In contrast, Concourse offers a web-based user interface, but the level of visibility and monitoring depends on the additional monitoring tools and configurations implemented by the user.
Ease of Use: AWS CodePipeline is designed to be user-friendly, with a simple and intuitive console interface for pipeline creation and management. Concourse, being an open-source tool, requires more configuration and setup efforts, making it relatively more complex to use compared to AWS CodePipeline.
Community Support: AWS CodePipeline is a fully supported service provided by Amazon Web Services (AWS). As a result, users can benefit from comprehensive documentation, official support channels, and frequent updates. On the other hand, Concourse being an open-source project, the level of support and documentation might vary depending on the user community and contributors.
Pricing: AWS CodePipeline offers a pay-per-use pricing model, where users only pay for the resources they use in their pipelines, such as build minutes, deployment actions, and storage. Concourse, being an open-source tool, is free to use, but users need to allocate resources and infrastructure to run and maintain their Concourse server.

AWS CodePipeline vs Concourse

Overview