Code Climate vs Hound: What are the differences?
Developers describe Code Climate as "Automated Ruby Code Review". 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. On the other hand, Hound is detailed as "A hosted service that comments on Ruby style guide violations in your GitHub pull requests". Take care of pesky code reviews with a trusty Hound. Hound reviews GitHub pull requests for style guide violations.
Code Climate and Hound belong to "Code Review" category of the tech stack.
Some of the features offered by Code Climate are:
- Automated Git Updates- Nothing to install. Code Climate runs everytime you push a new commit.
- Activity Feeds- Up-to-the-minute information so you can see when and how code changes.
- Instant Notifications- Major security and quality changes pushed to where you work: email, Campfire, HipChat, and RSS feeds.
On the other hand, Hound provides the following key features:
- Open source
- Free for public repos
- Automated reviews of GitHub pull requests for style guide violations
"Auto sync with Github" is the top reason why over 68 developers like Code Climate, while over 3 developers mention "Comments on style so I don't have to" as the leading cause for choosing Hound.
Hound is an open source tool with 1.72K GitHub stars and 393 GitHub forks. Here's a link to Hound's open source repository on GitHub.
According to the StackShare community, Code Climate has a broader approval, being mentioned in 144 company stacks & 48 developers stacks; compared to Hound, which is listed in 10 company stacks and 3 developer stacks.
What is Code Climate?
What is Hound?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Hound?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
The continuous integration process for our Rails backend app starts by opening a GitHub pull request. This triggers a CircleCI build and some Code Climate checks.
The CircleCI build is a workflow that runs the following jobs:
- check for security vulnerabilities with Brakeman
- check code quality with RuboCop
- run RSpec tests in parallel with the knapsack gem, and output test coverage reports with the simplecov gem
- upload test coverage to Code Climate
Code Climate checks the following:
- code quality metrics like code complexity
- test coverage minimum thresholds
The CircleCI jobs and Code Climate checks above have corresponding GitHub status checks.
Once all the mandatory GitHub checks pass and the code+functionality have been reviewed, developers can merge their pull request into our Git
master branch. Code is then ready to deploy!
This is one of the key tools I can't leave out when I'm working on a project, basically it is mandatory for me to use it on my Ruby on Rails projects. I think the price is a little expensive for a "Solo plan" but if you can get your client to pay, it's definitely worth it. You or the future developers that will continue with the project will thank you!
We use it as part of CI process to check code quality, to ensure that we're not inadvertently making common mistakes and can keep the smells and scope of code changes in line and clean. Having this step here should make future support and additions much more efficient and easy to understand.
Check duplicate code, complexity and common pitfalls. Code coverage indicator for Github README file.
checking our repo code quality.