Concourseย vsย Jenkins Xย vsย Testling

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

Concourse

261
393
+ 1
54
Jenkins X

149
370
+ 1
16
Testling

112
6
+ 1
2
Advice on Concourse, Jenkins X, and Testling
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 ยท 442.1K 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
Needs advice
on
CircleCICircleCIGitLab CIGitLab CI
and
Jenkins XJenkins X

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
on
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
on
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
on
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
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Concourse
Pros of Jenkins X
Pros of Testling
  • 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
  • 7
    Kubernetes integration
  • 5
    Scripted Pipelines
  • 4
    GitOps
  • 2
    Quality

Sign up to add or upvote prosMake informed product decisions

Cons of Concourse
Cons of Jenkins X
Cons of Testling
  • 2
    Fail forward instead of rollback pattern
  • 1
    Complexity
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    No Stats
    - 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 Jenkins X?

    Jenkins X is a CI/CD solution for modern cloud applications on Kubernetes

    What is Testling?

    Sign in with your browserling account. free for open source. No sign-up required. Just configure a github webhook.

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

    Jobs that mention Concourse, Jenkins X, and Testling as a desired skillset
    What companies use Concourse?
    What companies use Jenkins X?
    What companies use Testling?

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

    What tools integrate with Concourse?
    What tools integrate with Jenkins X?
    What tools integrate with Testling?
      No integrations found

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

      What are some alternatives to Concourse, Jenkins X, and Testling?
      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