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

Concourse

231
329
+ 1
49
GitLab CI

1.9K
1.3K
+ 1
71
Add tool

Concourse vs GitLab CI: 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; GitLab CI: GitLab integrated CI to test, build and deploy your code. 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.

Concourse and GitLab CI can be primarily classified as "Continuous Integration" tools.

"Real pipelines" is the primary reason why developers consider Concourse over the competitors, whereas "Robust CI with awesome Docker support" was stated as the key factor in picking GitLab CI.

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

According to the StackShare community, GitLab CI has a broader approval, being mentioned in 210 company stacks & 93 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.

Advice on Concourse and GitLab CI
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 路 161.5K 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
Needs advice
on
Jenkins XJenkins XGitLab CIGitLab CI
and
CircleCICircleCI

We are a mid-size startup running Scala apps. Moving from Jenkins/EC2 to Spinnaker/EKS and looking for a tool to cover our CI/CD needs. Our code lives on GitHub, artifacts in nexus, images in ECR.

Drone is out, GitHub actions are being considered along with Circle CI and GitLab CI.

We primarily need:

  • Fast SBT builds (caching)
  • Low maintenance overhead (ideally serverless)
  • Everything as code
  • Ease of use
See more
Replies (3)
Glenn Gillen
Recommends
BuildkiteBuildkite

I think I've tried most of the CI tools out there at some point. It took me a while to get around to Buildkite because at first I didn't see much point given it seemed like you had to run the agent yourself. Eventually it dawned on me why this approach was more ingenious than I realised:

Running my app in a production (or production-like) environment was already a solved problem, because everything was already in some form of "everything as code". Having a test environment where the only difference was adding the Buildkite agent was a trivial addition.

It means that dev/test/prod parity is simple to achieve and maintain. It's also proven to be much easier to support than trying to deal with the problems that come with trying to force an app to fit into the nuances and constraints that are imposed by the containers/runtime of a CI service. When you completely control all of the environment the tests are running in you define those constraints too. It's been a great balance between a managed service and the flexibility of running it yourself.

And while none of my needs have hit the scale of Shopify (I saw one of their engineers speak about it at a conference once, I can't find the video now though 馃槥) it's good to know I can scale out my worker nodes to hundreds of thousands of workers to reduce the time it takes for my tests to run.

See more
Recommends
jFrogjFrog

I would recommend you to consider the JFrog Platform that includes JFrog Pipelines - it will allow you to manage the full artifact life cycle for your sbt, docker and other technologies, and automate all of your CI and CD using cloud native declarative yaml pipelines. Will integrate smoothly with all your other toolset.

See more
Estu Fardani
Recommends
GitLab CIGitLab CI

more configurable to setup ci/cd: * It can provide caching when build sbt, just add this section to yml file * Easy to use, many documentation

Weakness: * Need use gitlab as repository to bring more powerful configuration

See more
Decisions about Concourse and GitLab CI

Buddy is one of the most easy-to-use tools for CI I ever met. When I needed to set up the pipeline I was really impressed with how easy it is to create it with Buddy with only a few moments. It's literally like: 1. Add repo 2. Click - Click - Click 3. You're done and your app is on prod :D The top feature that I've found is a simple integration with different notification channels - not only Slack (which is the one by default), but Telegram and Discord. The support is also neat - guys respond pretty quickly on even a small issue.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Concourse
Pros of GitLab CI
  • 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
  • 22
    Robust CI with awesome Docker support
  • 12
    Simple configuration
  • 8
    All in one solution
  • 6
    Source Control and CI in one place
  • 5
    Easy to configure own build server i.e. GitLab-Runner
  • 5
    Integrated with VCS on commit
  • 4
    Free and open source
  • 2
    Hosted internally
  • 1
    Pipeline could be started manually
  • 1
    Built-in support of Review Apps
  • 1
    Enable or disable pipeline by using env variables
  • 1
    Gitlab templates could be shared across logical group
  • 1
    Easy to setup the dedicated runner to particular job
  • 1
    Built-in Docker Registry
  • 1
    Built-in support of Kubernetes

Sign up to add or upvote prosMake informed product decisions

Cons of Concourse
Cons of GitLab CI
  • 2
    Fail forward instead of rollback pattern
  • 1
    Works best with GitLab repositories

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

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

What companies use Concourse?
What companies use GitLab CI?
See which teams inside your own company are using Concourse or GitLab CI.
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 GitLab CI?

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

What are some alternatives to Concourse and GitLab CI?
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.
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鈥檚 goals are foremost those of simplicity and maximum ease of use.
See all alternatives