Codecov vs Jenkins: 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, Jenkins is detailed as "An extendable open source continuous integration server". 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.
Codecov can be classified as a tool in the "Code Coverage" category, while Jenkins 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, Jenkins provides the following key features:
- Easy installation
- Easy configuration
- Change set support
"More stable than coveralls" is the primary reason why developers consider Codecov over the competitors, whereas "Hosted internally" was stated as the key factor in picking Jenkins.
Jenkins is an open source tool with 13.2K GitHub stars and 5.43K GitHub forks. Here's a link to Jenkins's open source repository on GitHub.
According to the StackShare community, Jenkins has a broader approval, being mentioned in 1753 company stacks & 1479 developers stacks; compared to Codecov, which is listed in 49 company stacks and 28 developer stacks.
What is Codecov?
What is Jenkins?
Want advice about which of these to choose?Ask the StackShare community!
All of our pull requests are automatically tested using Jenkins' integration with GitHub, and we provision and deploy our servers using Jenkins' interface. This is integrated with HipChat, immediately notifying us if anything goes wrong with a deployment.
Jenkins is our go-to devops automation tool. We use it for automated test builds, all the way up to server updates and deploys. It really helps maintain our homegrown continuous-integration suite. It even does our blue/green deploys.
- Continuous Deploy
- Dev stage: autodeploy by trigger push request from 'develop' branch of Gitlab
- Staging and production stages: Build and rollback quicly with Ansistrano playbook
- Sending messages of job results to Chatwork.
Currently serves as the location that our QA team builds various automated testing jobs.
At one point we were using it for builds, but we ended up migrating away from them to Code Pipelines.