Codecov vs Codeship

Overview

Codeship

Stacks1.0K

Followers730

Votes1.5K

Codecov

Stacks2.8K

Followers325

Votes102

Codecov vs Codeship: 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, Codeship is detailed as "A Continuous Integration Platform in the cloud". 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.

Codecov can be classified as a tool in the "Code Coverage" category, while Codeship 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, Codeship provides the following key features:

Run you automated tests | Easily set up Codeship with Github or Bitbucket and trigger your automated tests with a simple push to your repository.
100 builds & 5 private projects free per month.
Free for OSS.

"More stable than coveralls" is the primary reason why developers consider Codecov over the competitors, whereas "Simple deployments" was stated as the key factor in picking Codeship.

According to the StackShare community, Codeship has a broader approval, being mentioned in 277 company stacks & 82 developers stacks; compared to Codecov, which is listed in 49 company stacks and 29 developer stacks.

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)

Manual

Advice on Codeship, Codecov

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

Detailed Comparison

Codeship	Codecov
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.	Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.
Run you automated tests \| Easily set up Codeship with Github or Bitbucket and trigger your automated tests with a simple push to your repository.; 100 builds & 5 private projects free per month.;Free for OSS.;Configure deployment pipelines \| Set up powerful deployment pipelines that let you deploy with ease and confidence multiple times a day.;Notifications \| Intelligent notifications and integrations keep your team up-to-date.;SSH debug access \| Easily ssh into a debug build to get more insights.;Use your resources to build amazing products. Codeship takes care of managing and scaling your test and delivery infrastructure.	Beautiful Reports;Pull Request Comments;Interactive Commit Graphs;Chrome Extension;Github Commit Status;Easy to Integrate;Hipchat Integration
Statistics
Stacks 1.0K	Stacks 2.8K
Followers 730	Followers 325
Votes 1.5K	Votes 102
Pros & Cons
Pros 215 Simple deployments 179 Easy setup 159 Github integration 147 Continuous deployment 110 Bitbucket integration Cons 3 Ui could use some polishing 0 Antiquated ui 0 Difficult to answer build questions	Pros 17 More stable than coveralls 17 Easy setup 14 GitHub integration 11 They reply their users 10 Easy setup,great ui Cons 1 GitHub org / team integration is a little too tight 0 Support does not respond to email 0 Delayed results by hours since recent outage
Integrations
Slack GitLab CI GitHub HipChat Google Compute Engine Ninefold Amazon EC2 Google App Engine AWS CodeDeploy Bitbucket	HipChat Jenkins Bitbucket GitLab GitHub CircleCI Heroku

What are some alternatives to Codeship, Codecov?

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.

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.

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 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 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 is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

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.

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

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

Related Comparisons

Some of the features offered by Codecov are:

Beautiful Reports
Pull Request Comments
Interactive Commit Graphs

On the other hand, Codeship provides the following key features:

Run you automated tests | Easily set up Codeship with Github or Bitbucket and trigger your automated tests with a simple push to your repository.
100 builds & 5 private projects free per month.
Free for OSS.

"More stable than coveralls" is the primary reason why developers consider Codecov over the competitors, whereas "Simple deployments" was stated as the key factor in picking Codeship.

Codecov vs Codeship