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

Concourse

232
331
+ 1
49
Shippable

62
53
+ 1
128
Add tool

Concourse vs Shippable: 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; Shippable: Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github & Bitbucket repos. 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.

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

"Real pipelines" is the primary reason why developers consider Concourse over the competitors, whereas "Free private repositories" was stated as the key factor in picking Shippable.

Concourse is an open source tool with 3.92K GitHub stars and 472 GitHub forks. Here's a link to Concourse's open source repository on GitHub.

DigitalOcean, Starbucks, and HelloFresh are some of the popular companies that use Concourse, whereas Shippable is used by Techstars, DrinkIn, and Reviewable. Concourse has a broader approval, being mentioned in 18 company stacks & 17 developers stacks; compared to Shippable, which is listed in 24 company stacks and 4 developer stacks.

Advice on Concourse and Shippable
Needs advice
on
JenkinsJenkins
and
ConcourseConcourse

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 · 157.1K views
Recommends
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 Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Concourse
Pros of Shippable
  • 14
    Real pipelines
  • 9
    Containerised builds
  • 9
    Flexible engine
  • 5
    Fast
  • 3
    Open source
  • 3
    Simple configuration management
  • 3
    No Snowflakes
  • 2
    You have to do everything
  • 1
    Fancy Visualization
  • 18
    Free private repositories
  • 16
    Built on docker
  • 14
    Continuous deployment
  • 13
    Bitbucket integration
  • 12
    Fastest continuous integration and deployment
  • 11
    Team permissions
  • 9
    Flexible Configuration
  • 8
    Matrix builds
  • 8
    Finer GitHub Scope
  • 6
    Intelligent Notifications
  • 4
    Awesome experience
  • 4
    Easy Setup
  • 3
    Fast
  • 1
    Custom docker containers
  • 1
    2x faster than other CI/CD platforms

Sign up to add or upvote prosMake informed product decisions

Cons of Concourse
Cons of Shippable
  • 2
    Fail forward instead of rollback pattern
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    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 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.

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

    What companies use Concourse?
    What companies use Shippable?
    See which teams inside your own company are using Concourse or Shippable.
    Sign up for Private StackShareLearn More

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

    What tools integrate with Concourse?
    What tools integrate with Shippable?

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

    What are some alternatives to Concourse and Shippable?
    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.
    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.
    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.
    See all alternatives