StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Go.CD vs Travis CI

Go.CD vs Travis CI

OverviewDecisionsComparisonAlternatives

Overview

Travis CI
Travis CI
Stacks28.0K
Followers6.7K
Votes1.7K
GoCD
GoCD
Stacks205
Followers325
Votes207
GitHub Stars7.3K
Forks980

Go.CD vs Travis CI: What are the differences?

Comparing Go.CD and Travis CI

Go.CD and Travis CI are both popular continuous integration and delivery (CI/CD) tools that help teams automate the process of building, testing, and deploying software. While they have similar goals, there are key differences between the two.

  1. Deployment Options and Scalability: Go.CD provides more flexibility in deployment options as it supports a wider range of infrastructure choices such as cloud-based, on-premise, or hybrid environments. It also offers better scalability with support for complex multi-stage pipelines, allowing teams to handle large-scale projects more effectively.

  2. Configuration as Code: Travis CI has a stronger focus on configuration as code, allowing developers to define build and deployment pipelines using a declarative YAML-based language. This provides better transparency and reproducibility of the pipeline configuration, making it easier to track changes and collaborate on the pipeline setup.

  3. Plugin Ecosystem: Go.CD offers a rich plugin ecosystem that allows extending its functionality with a wide range of community-contributed plugins. These plugins enable integration with various tools and services, providing more flexibility in customizing the CI/CD pipeline to fit specific project requirements.

  4. Build Variability and Matrix Testing: Travis CI has built-in support for build variability, allowing developers to define matrix builds that execute different combinations of build configurations. This is particularly useful for testing software against multiple versions of dependencies or different platforms, providing better coverage and confidence in the build results.

  5. Integration with Version Control Systems: Go.CD supports a broader range of version control systems, including Git, Mercurial, and Subversion, offering more options for integrating with the team's preferred source code repositories. Travis CI focuses mainly on Git integration, being tightly integrated with popular Git hosting platforms such as GitHub or Bitbucket.

  6. Enterprise-grade Features: Go.CD provides additional enterprise-grade features like advanced access control, LDAP integration, and support for enterprise plugins. These features make it suitable for larger organizations with complex security and compliance requirements.

In summary, Go.CD is a versatile CI/CD tool that excels in deployment options, scalability, and enterprise-grade features, while Travis CI's strengths lie in its configuration as code approach, plugin ecosystem, and build variability capabilities. Choosing between the two depends on the specific needs and priorities of the development team.

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)
or
Manual

Advice on Travis CI, GoCD

Felipe
Felipe

May 24, 2020

Needs advice

My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.

198k views198k
Comments
StackShare
StackShare

Apr 17, 2019

Needs advice

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

529k views529k
Comments
Tatiana
Tatiana

Nov 16, 2019

Decided

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

734k views734k
Comments

Detailed Comparison

Travis CI
Travis CI
GoCD
GoCD

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.

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.

Easy Setup- Getting started with Travis CI is as easy as enabling a project, adding basic build instructions to your project and committing code.;Supports Your Platform- Lots of databases and services are pre-installed and can simply be enabled in your build configuration, we'll launch them for you automatically. MySQL, PostgreSQL, ElasticSearch, Redis, Riak, RabbitMQ, Memcached are available by default.;Deploy With Confidence- Deploying to production after a successful build is as easy as setting up a bit of configuration, and we'll deploy your code to Heroku, Engine Yard Cloud, Nodejitsu, cloudControl, OpenShift, and CloudFoundry.
Model complex workflows with dependency management and parallel execution; Easy to pass once-built binaries between stages; Visibility into your end-to-end workflow. Track a change from commit to deploy at a glance; Manual triggers allow deployment any version at anytime. And it's securable and auditable; Run tests written in most languages or frameworks, provides informative testing report; Compare both files and commit messages across any two arbitrary builds; Eliminate Bottlenecks by providing trivial parallel execution across pipelines, platforms, versions, branches, etc.; Easily reuse pipeline configurations via template system.
Statistics
GitHub Stars
-
GitHub Stars
7.3K
GitHub Forks
-
GitHub Forks
980
Stacks
28.0K
Stacks
205
Followers
6.7K
Followers
325
Votes
1.7K
Votes
207
Pros & Cons
Pros
  • 506
    Github integration
  • 388
    Free for open source
  • 271
    Easy to get started
  • 191
    Nice interface
  • 162
    Automatic deployment
Cons
  • 8
    Can't be hosted insternally
  • 3
    Feature lacking
  • 3
    Unstable
  • 2
    Incomplete documentation for all platforms
Pros
  • 32
    Open source
  • 27
    Pipeline dependencies
  • 25
    Pipeline structures
  • 22
    Can run jobs in parallel
  • 20
    Very flexible
Cons
  • 2
    Lack of plugins
  • 2
    Horrible ui
  • 1
    No support
Integrations
Amazon S3
Amazon S3
Heroku
Heroku
AWS CodeDeploy
AWS CodeDeploy
MySQL
MySQL
Red Hat OpenShift
Red Hat OpenShift
Nodejitsu
Nodejitsu
npm
npm
GitHub
GitHub
Engine Yard Cloud
Engine Yard Cloud
cloudControl
cloudControl
Docker
Docker
Kubernetes
Kubernetes
Slack
Slack

What are some alternatives to Travis CI, GoCD?

Jenkins

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.

Codeship

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

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

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

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Shippable

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.

Buildkite

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Snap CI

Snap CI

Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.

Appveyor

Appveyor

AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana