Need advice about which tool to choose?Ask the StackShare community!

Concourse

259
390
+ 1
54
Spinnaker

225
352
+ 1
13
Add tool

Concourse vs Spinnaker: What are the differences?

# Introduction

Concourse and Spinnaker are both popular continuous delivery tools used by software development teams to automate their build, test and deployment processes. While they serve a similar purpose, they have key differences that differentiate them in terms of functionality and use cases.

1. **Architecture**: Concourse follows a pipeline-based architecture, where tasks and resources are defined in a YAML file to create a linear workflow. On the other hand, Spinnaker uses a Kubernetes-style declarative API with stages and pipelines defined in a JSON format, offering more flexibility and scalability for complex deployment scenarios.

2. **Integration**: Concourse is heavily integrated with containerization platforms like Docker and Kubernetes, making it a preferred choice for teams working with containerized applications. In contrast, Spinnaker provides integrations with a wide range of cloud providers, offering support for multi-cloud deployments and hybrid environments with ease.

3. **Approval Process**: Concourse lacks built-in support for an approval process, which means that all stages in a pipeline run sequentially without human intervention. In contrast, Spinnaker offers an approval process where designated users can manually approve or reject each stage, providing greater control over deployment workflows.

4. **Rollback Mechanism**: Concourse does not have a native rollback mechanism, making it challenging to revert to previous versions in case of issues during deployment. On the other hand, Spinnaker provides a robust rollback mechanism that allows users to easily roll back to a previous, stable version in case of failures or bugs in the current deployment.

5. **Community Support**: While both Concourse and Spinnaker have active communities contributing to their development, Spinnaker has a larger user base and a more extensive support network, making it easier for users to find resources, documentation, and solutions to their deployment challenges.

In Summary, Concourse and Spinnaker have distinct architectural differences, with Concourse being more focused on pipelines and containerization, while Spinnaker offers a broader range of integrations and features for managing complex deployment workflows.
Advice on Concourse and Spinnaker
Needs advice
on
ConcourseConcourse
and
JenkinsJenkins

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 !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG · | 2 upvotes · 392.3K views
Recommends
on
ConcourseConcourse

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Concourse
Pros of Spinnaker
  • 16
    Real pipelines
  • 10
    Containerised builds
  • 9
    Flexible engine
  • 6
    Fast
  • 4
    Open source
  • 3
    No Snowflakes
  • 3
    Simple configuration management
  • 2
    You have to do everything
  • 1
    Fancy Visualization
  • 13
    Mature

Sign up to add or upvote prosMake informed product decisions

Cons of Concourse
Cons of Spinnaker
  • 2
    Fail forward instead of rollback pattern
  • 3
    No GitOps
  • 1
    Configuration time
  • 1
    Management overhead
  • 1
    Ease of use

Sign up to add or upvote consMake informed product decisions

What is Concourse?

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.

What is Spinnaker?

Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Concourse and Spinnaker as a desired skillset
What companies use Concourse?
What companies use Spinnaker?
See which teams inside your own company are using Concourse or Spinnaker.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Concourse?
What tools integrate with Spinnaker?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to Concourse and Spinnaker?
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.
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.
GitLab CI
GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
Ansible
Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
See all alternatives