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

Codecov

805
308
+ 1
98
Travis CI

11.1K
6.2K
+ 1
1.8K
Add tool

Codecov vs Travis CI: What are the differences?

Developers describe Codecov as "Hosted coverage reports with awesome features to enhance your CI workflow". Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security. On the other hand, Travis CI is detailed as "A hosted continuous integration service for open source and private projects". 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.

Codecov can be classified as a tool in the "Code Coverage" category, while Travis CI is grouped under "Continuous Integration".

Some of the features offered by Codecov are:

  • Beautiful Reports
  • Pull Request Comments
  • Interactive Commit Graphs

On the other hand, Travis CI provides the following key features:

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

"More stable than coveralls" is the top reason why over 14 developers like Codecov, while over 505 developers mention "Github integration" as the leading cause for choosing Travis CI.

DuckDuckGo, Tilt, and CodeCombat are some of the popular companies that use Travis CI, whereas Codecov is used by Repro, ContentSquare, and homezen. Travis CI has a broader approval, being mentioned in 666 company stacks & 613 developers stacks; compared to Codecov, which is listed in 49 company stacks and 28 developer stacks.

Advice on Codecov and Travis CI
Needs advice
on
JenkinsJenkinsTravis CITravis CI
and
CircleCICircleCI

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
Senior Developer at Elegant Themes · | 13 upvotes · 416.6K 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 · 400.2K views
Recommends
Travis CITravis 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 CITravis 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 CIGitLab 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
BuildkiteBuildkite

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
Decisions about Codecov and Travis CI

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.

See more

We were long time users of TravisCI, but switched to CircleCI because of the better user interface and pricing. Version 2.0 has had a couple of trips and hiccups; but overall we've been very happy with the continuous integration it provides. Continuous Integration is a must-have for building software, and CircleCI continues to surprise as they roll out ideas and features. It's leading the industry in terms of innovation and new ideas, and it's exciting to see what new things they keep rolling out.

See more

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Codecov
Pros of Travis CI
  • 17
    More stable than coveralls
  • 16
    Easy setup
  • 13
    GitHub integration
  • 11
    They reply their users
  • 9
    Easy setup,great ui
  • 5
    Easily see per-commit coverage in GitHub
  • 5
    Steve is the man
  • 4
    Golang support
  • 4
    Merges coverage from multiple CI jobs
  • 3
    Code coverage
  • 3
    Newest Android SDK preinstalled
  • 3
    JSON in web hook
  • 2
    Cool diagrams
  • 2
    Free for public repositories
  • 1
    Bitbucket Integration
  • 506
    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
    Github Pull Request build
  • 2
    Straightforward Github/Coveralls integration
  • 2
    Easy of Usage
  • 2
    Integrates with everything
  • 1
    Caching resolved artifacts
  • 1
    Docker support
  • 1
    Great Documentation
  • 1
    Build matrix
  • 1
    No-brainer for CI
  • 1
    Debug build workflow
  • 1
    Ubuntu trusty is not supported
  • 1
    Free for students
  • 1
    Configuration saved with project repository
  • 1
    Multi-threaded run
  • 1
    Hipchat Integration
  • 0
    Perfect

Sign up to add or upvote prosMake informed product decisions

Cons of Codecov
Cons of Travis CI
  • 1
    GitHub org / team integration is a little too tight
  • 0
    Delayed results by hours since recent outage
  • 0
    Support does not respond to email
  • 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 Codecov?

Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.

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 Codecov?
What companies use Travis CI?
See which teams inside your own company are using Codecov or Travis CI.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Codecov?
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 Codecov and Travis CI?
Code Climate
After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.
Coveralls
Coveralls works with your CI server and sifts through your coverage data to find issues you didn't even know you had before they become a problem. Free for open source, pro accounts for private repos, instant sign up with GitHub OAuth.
SonarQube
SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
Codacy
Codacy automates code reviews and monitors code quality on every commit and pull request on more than 40 programming languages reporting back the impact of every commit or PR, issues concerning code style, best practices and security.
JaCoCo
It is a free code coverage library for Java, which has been created based on the lessons learned from using and integration existing libraries for many years.
See all alternatives