Code Climate vs Jenkins

Overview

Code Climate

Stacks740

Followers497

Votes285

Jenkins

Stacks59.2K

Followers50.4K

Votes2.2K

GitHub Stars24.6K

Forks9.2K

Code Climate vs Jenkins: What are the differences?

Code Climate: 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; Jenkins: 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.

Code Climate can be classified as a tool in the "Code Review" category, while Jenkins is grouped under "Continuous Integration".

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, Jenkins provides the following key features:

Easy installation
Easy configuration
Change set support

"Auto sync with Github" is the top reason why over 68 developers like Code Climate, while over 497 developers mention "Hosted internally" as the leading cause for choosing 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.

Facebook, Netflix, and ebay are some of the popular companies that use Jenkins, whereas Code Climate is used by Airbrake, Chargify, and DNSimple. Jenkins has a broader approval, being mentioned in 1753 company stacks & 1479 developers stacks; compared to Code Climate, which is listed in 134 company stacks and 45 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 Code Climate, Jenkins

Balaramesh

Apr 20, 2020

Needs adviceon

Azure Pipelines

.NET

Jenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

663k views663k

Comments

StackShare

Apr 17, 2019

Needs advice

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

530k views530k

Comments

Tatiana

Nov 16, 2019

Decided

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.

734k views734k

Comments

Detailed Comparison

Code Climate	Jenkins
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.	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.
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.;Team Sharing- Instant access for your whole team to maximize code visibility across projects.;Hotspots- A hit list for refactoring. Target your messiest areas one-by-one.;Duplication Detection- Fuzzy matching algorithm finds DRY-violations that human reviewers might miss.;Email Notification- Instant email notifications to let you know when new security and code issues arise;Security Dashboard- Organized listing of your app's vulnerabilities, including when they were first introduced and how to address them.;Alerts for New Rails Disclosures- Going beyond Gemfile analysis to let you know whether you're at high risk based on how your specific code uses a vulnerable library.;Start Fixing with One Click- Full integration with Pivotal Tracker, GitHub Issues, and Lighthouse lets you open tickets instantly.;GitHub Integration- Post-receive hooks for instant updates and GitHub drilldown links throughout.;Test Coverage Integration- Surfacing coverage information at the repo, class, and source listing level.;Private, Safe, and Secure- All data is private by default. SSL encryption everywhere.	Easy installation;Easy configuration;Change set support;Permanent links;RSS/E-mail/IM Integration;After-the-fact tagging;JUnit/TestNG test reporting;Distributed builds;File fingerprinting;Plugin Support
Statistics
GitHub Stars -	GitHub Stars 24.6K
GitHub Forks -	GitHub Forks 9.2K
Stacks 740	Stacks 59.2K
Followers 497	Followers 50.4K
Votes 285	Votes 2.2K
Pros & Cons
Pros 71 Auto sync with Github 49 Simple grade system that motivates to keep code clean 45 Better coding 30 Free for open source 21 Hotspots for quick refactoring candidates Cons 2 Learning curve, static analysis comparable to eslint 1 Complains about small stylistic decisions	Pros 523 Hosted internally 469 Free open source 318 Great to build, deploy or launch anything async 243 Tons of integrations 211 Rich set of plugins with good documentation Cons 13 Workarounds needed for basic requirements 10 Groovy with cumbersome syntax 8 Plugins compatibility issues 7 Lack of support 7 Limited abilities with declarative pipelines
Integrations
GitHub HipChat Campfire Semaphore	No integrations available

What are some alternatives to Code Climate, Jenkins?

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.

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.

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.

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.

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.

Phabricator

Phabricator is a collection of open source web applications that help software companies build better software.

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.

Related Comparisons

Bitbucket vs GitHub vs GitLab

AWS CodeCommit vs Bitbucket vs GitHub

Docker Swarm vs Kubernetes vs Rancher

Grunt vs Webpack vs gulp

Grafana vs Graphite vs Kibana

Code Climate vs Jenkins: What are the differences?

Code Climate can be classified as a tool in the "Code Review" category, while Jenkins is grouped under "Continuous Integration".

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, Jenkins provides the following key features:

Easy installation
Easy configuration
Change set support

"Auto sync with Github" is the top reason why over 68 developers like Code Climate, while over 497 developers mention "Hosted internally" as the leading cause for choosing 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.