CircleCI vs Codeship vs Travis CI

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

CircleCI

8.1K
5K
+ 1
957
Codeship

1K
724
+ 1
1.5K
Travis CI

7.5K
5.3K
+ 1
1.8K
Advice on CircleCI, Codeship, and Travis CI
Needs advice
on
Jenkins X
GitLab CI
and
CircleCI

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
Buildkite

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
jFrog

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 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
View all (3)
Needs advice
on
Jenkins
Travis CI
and
CircleCI

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?"

See more
Replies (6)
Dustin Falgout
Developer at Elegant Themes · | 13 upvotes · 189K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit · | 9 upvotes · 166.8K views
Recommends
Travis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
Travis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
GitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
Buildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
View all (6)
Decisions about CircleCI, Codeship, and Travis CI
Vladyslav Holubiev
Software Enginieer at Shelf · | 2 upvotes · 10.3K views
Migrated
from
wercker
to
CircleCI
at
()

We migrated all our CI/CD pipelines to CircleCI back in 2017 and are particularly happy about it since!

Our top loved feature is unlimited parallelism. We can run as many builds concurrently as we want.

We also use orbs, pipeline parameters, reusable commands, build cache, test insights.

For some of the heavier repos, we use a larger resource class and mount RAMdisk to a file system to speed up builds.

See more
Phillip Manwaring
Developer at Coach Align · | 5 upvotes · 7.5K views

The introduction of Orbs a few years ago has really streamlined CircleCI configuration files and made them really easy to work with. Haven't tried GitHub Actions and decided to go with what was familiar instead of trying something new. Tried to make AWS Codepipeline work a few years back on different projects and found it to be incredibly frustrating, lacking support for some of the most basic features and use cases.

See more
Kirill Mikhailov

Jenkins is a friend of mine. 😀

There are not much space for Jenkins competitors for now from my point of view. With declarative pipelines now in place, its super easy to maintain them and create new ones(altho I prefer scripted still). Self-hosted, free, huge community makes it the top choice so honestly for me it was an easy pick.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of CircleCI
Pros of Codeship
Pros of Travis CI
  • 223
    Github integration
  • 175
    Easy setup
  • 151
    Fast builds
  • 94
    Competitively priced
  • 73
    Slack integration
  • 54
    Docker support
  • 44
    Awesome UI
  • 33
    Great customer support
  • 18
    Ios support
  • 14
    Hipchat integration
  • 12
    SSH debug access
  • 11
    Free for Open Source
  • 5
    Mobile support
  • 5
    Bitbucket integration
  • 4
    Nodejs support
  • 4
    AWS CodeDeploy integration
  • 3
    YAML configuration
  • 3
    Free for Github private repo
  • 3
    Great support
  • 2
    Clojure
  • 2
    Simple, clean UI
  • 2
    Clojurescript
  • 2
    OSX support
  • 2
    Continuous Deployment
  • 1
    Android support
  • 1
    Autoscaling
  • 1
    Fair pricing
  • 1
    All inclusive testing
  • 1
    Helpful documentation
  • 1
    Japanese in rspec comment appears OK
  • 1
    Favorite
  • 1
    Build PR Branch Only
  • 1
    Really easy to use
  • 1
    Unstable
  • 1
    So circular
  • 1
    Easy setup, easy to understand, fast and reliable
  • 1
    Parallel builds for slow test suites
  • 1
    Easy setup. 2.0 is fast!
  • 1
    Parallelism
  • 1
    Extremely configurable
  • 1
    Easy to deploy to private servers
  • 1
    Works
  • 215
    Simple deployments
  • 179
    Easy setup
  • 159
    Github integration
  • 147
    Continuous deployment
  • 110
    Bitbucket integration
  • 97
    Easy ui
  • 84
    Slack integration
  • 66
    Fast builds
  • 61
    Great ui
  • 61
    Great customer support
  • 28
    SSH debug access
  • 27
    Free plan for 5 private repositories
  • 27
    Easy to get started
  • 23
    Competitively priced
  • 20
    Notifications
  • 20
    Hipchat, Campfire integrations
  • 16
    Awesome UI
  • 15
    Fast
  • 14
    Great documentation
  • 13
    Great experience
  • 12
    Free for open source
  • 10
    Great Tutorials
  • 4
    GitLab integration
  • 4
    Free
  • 4
    Easy to use, above all and its free for basic use
  • 3
    Easy for CI first timers
  • 3
    BitBucket Support
  • 3
    Very easy to get started
  • 3
    Build private Github repos on the free plan
  • 3
    Awesome
  • 2
    Super easy setup, works great with py.test/tox
  • 2
    Openshift integration
  • 2
    Great support, even on free tier
  • 2
    AppEngine integration
  • 2
    Easy debugging with ssh
  • 2
    Integrates with other free software
  • 2
    Superfast team work integration
  • 2
    Grepping Codeship = 1 day. Grepping Bamboo = 1 month
  • 2
    Easy to set up, very nice GitHub integration
  • 2
    Up and running in few minutes, and above all UI
  • 507
    Github integration
  • 388
    Free for open source
  • 272
    Easy to get started
  • 191
    Nice interface
  • 163
    Automatic deployment
  • 72
    Tutorials for each programming language
  • 40
    Friendly folks
  • 29
    Support for multiple ruby versions
  • 28
    Osx support
  • 24
    Easy handling of secret keys
  • 6
    Fast builds
  • 4
    Support for students
  • 3
    The best tool for Open Source CI
  • 3
    Hosted
  • 3
    Build Matrices
  • 2
    Straightforward Github/Coveralls integration
  • 2
    Easy of Usage
  • 2
    Github Pull Request build
  • 2
    Integrates with everything
  • 1
    Docker support
  • 1
    Configuration saved with project repository
  • 1
    Free for students
  • 1
    Build matrix
  • 1
    No-brainer for CI
  • 1
    Debug build workflow
  • 1
    Great Documentation
  • 1
    Multi-threaded run
  • 1
    Hipchat Integration
  • 1
    Caching resolved artifacts
  • 1
    Ubuntu trusty is not supported
  • 0
    Perfect
  • 0
    One

Sign up to add or upvote prosMake informed product decisions

Cons of CircleCI
Cons of Codeship
Cons of Travis CI
  • 11
    Unstable
  • 6
    Scammy pricing structure
  • 0
    Aggressive Github permissions
  • 3
    Ui could use some polishing
  • 0
    Antiquated ui
  • 0
    Difficult to answer build questions
  • 8
    Can't be hosted insternally
  • 3
    Feature lacking
  • 3
    Unstable
  • 2
    Incomplete documentation for all platforms

Sign up to add or upvote consMake informed product decisions

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

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

What is Travis CI?

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.

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

What companies use CircleCI?
What companies use Codeship?
What companies use Travis CI?

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

What tools integrate with CircleCI?
What tools integrate with Codeship?
What tools integrate with Travis CI?

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

Blog Posts

What are some alternatives to CircleCI, Codeship, and Travis 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.
Azure DevOps
Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
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.
CloudBees
Enables organizations to build, test and deploy applications to production, utilizing continuous delivery practices. They are focused solely on Jenkins as a tool for continuous delivery both on-premises and in the cloud.
Bamboo
Focus on coding and count on Bamboo as your CI and build server! Create multi-stage build plans, set up triggers to start builds upon commits, and assign agents to your critical builds and deployments.
See all alternatives
Reviews of CircleCI, Codeship, and Travis CI
Review of
Codeship

Working for a web agency, I have access to many premium services for all parts of the development process which leads to two things when it comes to working on my personal projects at home.

1: I am more fussy about the quality of tools and services that I use than I was before I went from just messing around with programming to having a developer job.

2: I really don't want to pay a single fee or any kind of subscription to services as after using them all day at work I find it hard to justify personally paying a premium to use them for a bit of time at home after work.

However with Code ship neither of these things caused any issues as I found it to be very high quality and free.

On the subject of it being free, I know there are other CI solutions that are free however if you wish to use it with a private repository then unless you already have private Github repos then the fact that Code Ship integrates with Bitbucket can be extremely convenient as it means you can set up your personal projects with free private repository and a free CI / testing solution for absolutely free.

Overall Codeship has really impressed me in every way from its pricing to its clean and simple UI and its ease of use.

Marc Qualie
Review of
Codeship

Setting up continuous integration is complex and time consuming. I've used Codeship for 1 year now and I would never go back to previous systems such as self hosted Jenkins for any kind of web applications. The ability to change developer access on a per repository basis with the click of a button is very helpful and integration with all our services such as Github and Heroku make testing and deployment happen in the background so we can concentrate on our application and not worry about what state the live code is in. We also find the Slack integration (and flowdock before that) to be a great way to share the current code status with the whole team without getting spammed with emails on each commit and build state change while testing prototype branches or working on pull-requests.

Review of
Codeship

Like most developers I'd love it if my deployment processes were always the same for every project so I never had to think about deployment. However, that's probably never going to happen unless we stop having clients. Codeship allows me to organize all of my deployments into one place and set them up once so that I don't have to remember the process for every nuance of every client.

Whether it's deploying a Drupal or Wordpress site to a private server, a Meteor.js app to Modulus, or just about anything else Codeship gives me the flexibility of writing my own shell scripts for custom jobs (private server) but also one-click solutions for common problems (deployment to Modulus).

Highly recommend them!

Review of
Codeship

It's not easy to differentiate a CI/CD service because integrations matter so much more than the service itself. Didn't even need to read any docs, it just works exactly as you expect it to.

Pros:

  • Pipelines for running tests in parallel (freemium).
  • Easiest setup of any CI service I've tried.
  • Mandatory build status image service.

Cons:

  • Test runners are alright, but not that powerful. Py.test can run tests in parallel on its own, but enabling that feature doesn't seem to speed up Codeship runs.
  • Doesn't detect tox environments, so you have to specify one environment per pipeline manually.
Review of
CircleCI

I use CircleCI as part of a cross platform mobile app to build and test the app as well as deploying .apk files to an s3 bucket.

Alongside CircleCI this repo also has a TravisCI setup for iOS. The CircleCI build has always been quicker and since moving from CircleCI v1 to CircleCI v2 it blows the TravisCI build out of the water. I'm really impressed with the performance gains from moving to v2. I'm pretty sure I could achieve similar results in Travis as well, but it was really easy to setup the Android CI build in Circle making use of Docker.

Ben Gandhi-Shepard
Review of
Codeship

I spent half a day grepping CodeShip and now I have a sweet deployment process for WP sites. After a month of wrestling with Bamboo I decided to give CodeShip a try thanks to an article by CodeShip's Roman Kuba about deploying WP sites

I am now killin' WP development with my CodeShip + WPEngine setup. This is also making WP development/deployment fun for the first time. CodeShip f*cking rocks.

Review of
Travis CI

In the past we used to run Jenkins. The build server always had weird issues and was a pain to maintain. Travis is a great solution for CI. Their Debug build features makes it trivial to figure out why your build broke. The integration with Github is also very slick. One thing they could improve is the documentation on the .travis.yaml format. All in all, great company and very responsive supports. Over here at getstream.io we're a fan. Keep up the good work guys!

VP of Engineering at Jetpack Workflow
Review of
CircleCI

After trying several CI systems, we stuck with CircleCI because of the inference engine in CircleCI 1.0 made setup a breeze. We were up and running quickly. Builds are reliable, nicely integrated into GitHub, and anytime we've had a question, the support team was there to help. The 2.0 system provides Docker support and far more customization and is still fairly easy to set up with helpful documentation.

Review of
CircleCI

CircleCI has become our CI of choice. The UI is really good and it has all the integrations we need. The 2.0 upgrade was not yet possible for one of our projects due to outdated gems, however, I have been able to get it working for a different one.

Information Technology
Review of
CircleCI

It help us with the automated build and test and also provide us with the build artifacts which we can use for the deployment also give use archive for each of our build, this things save us alot of time and cost

Review of
CircleCI

We use CircleCI to deploy to server. It is much easier than other websites like Travis especially for the free tier. It is especially useful for open source projects that need private access behind the scenes.

How developers use CircleCI, Codeship, and Travis CI
datapile uses
Travis CI

Travis CI is our pillar for automated deployment, pull request testing, auto-merging (for non-mission-critical projects), and build testing per commit / release.

It is highly configurable, super cheap, and extremely robust (supports every language and configuration we've thrown at it).

AngeloR uses
CircleCI

We originally used CircleCI as our self-contained build system for our internal node modules. It was very easy to set up and configure. Unfortunately we ended up stepping away from it to Jenkins and then CodePipeline due to better integration with our various applications.

Jeff Flynn uses
CircleCI

We prefer CircleCI because we care about testing our apps. We found it is better to invest the time writing rSPEC tests to ensure we don't insert any regression bugs with new branches. It's also nice to have a fully-automated deployment process from GitHub to Heroku.

Andrew Gatenby uses
Codeship

We use this as a CI tool when working on our API and related tools. The setup is relatively painless and it hooks directly into our Github repo's to provide reports and feedback.

Dieter Adriaenssens uses
Travis CI

Travis CI builds and tests every commit. It's also used to deploy Buildtime Trend as a Service to Heroku and the Buildtime Trend Python library to the PyPi repository.

Marc3842h uses
CircleCI

CircleCI is used as continues integration system for shiro and all of its modules.

It automatically deploys the latest GitHub commit to https://shiro.host/.

Nate Ferrell uses
Travis CI

Travis CI is critical for Linux and macOS CI tests for the Powershell module. Travis runs the same tests we run in AppVeyor in parallel.

RentChek uses
Codeship

Runs a full test suite whenever we push changes to master and if everything is good, automatically deploys our changes to production.

jasonmjohnson uses
CircleCI

CircleCI will be used for deployment and continuous integration using a scripted configuration that deploys to Amazon EC2.

Pathwright uses
CircleCI

Container-based CI service. Runs all of our backend tests, and is equipped to eventually run our client side tests.

Andrew Williams uses
Travis CI

To ensure that what works locally will also work for someone else. Also used to send code coverage to codeintel

Sascha Manns uses
Travis CI

Travis provides more than one Ruby version setting. So i can test my push directly in different Ruby versions.

Kim Do Hyeon uses
Codeship

원래 CircleCI 쓰다가 갑자기 슬랙으로 알림오는게 안돼서 Codeship 쓰는 중 Circle CI가 더 편함

azawisza uses
Codeship

build center and continous deployment for all services

Grubster uses
Codeship

A QA tool that runs the platform's automated tests