Bitbucket vs Codacy

Overview

Bitbucket

Stacks41.1K

Followers33.4K

Votes2.8K

Codacy

Stacks313

Followers551

Votes248

Bitbucket vs Codacy: What are the differences?

Bitbucket: One place to plan projects, collaborate on code, test and deploy, all with free private repositories. Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users; Codacy: Automated Code Review. Codacy is an automated code review tool for Scala, Java, Ruby, JavaScript, PHP, Python, CoffeeScript and CSS. It's continuous static analysis without the hassle. Save time in Code Reviews. Tackle your technical debt.

Bitbucket and Codacy are primarily classified as "Code Collaboration & Version Control" and "Code Review" tools respectively.

Some of the features offered by Bitbucket are:

Unlimited private repositories, charged per user
Best-in-class Jira integration
Built-in CI/CD

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

Monitoring of Technical Debt
Automated Code Review
New and Fixed Issues per commit

"Free private repos" is the primary reason why developers consider Bitbucket over the competitors, whereas "Automated code review" was stated as the key factor in picking Codacy.

CircleCI, Bitbucket, and Pandora are some of the popular companies that use Bitbucket, whereas Codacy is used by Codacy, DocEngage, and InstaGIS. Bitbucket has a broader approval, being mentioned in 1735 company stacks & 1450 developers stacks; compared to Codacy, which is listed in 44 company stacks and 23 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 Bitbucket, Codacy

Weverton

CTO at SourceLevel

Aug 3, 2020

Review

Do you review your Pull/Merge Request before assigning Reviewers?

If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:

Pick the correct target branch
Make Drafts explicit
Name things properly
Ask help for tools
Remove the noise
Fetch necessary data
Understand Mergeability
Pass the message
Add screenshots
Be found in the future
Comment inline in your changes

Read the blog post for more detailed explanation for each item :D

What else do you review before asking for code review?

1.19M views1.19M

Comments

Weverton

CTO at SourceLevel

Jul 22, 2020

Review

One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.

It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.

1.1M views1.1M

Comments

Detailed Comparison

Bitbucket	Codacy
Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.	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.
Unlimited private repositories, charged per user;Best-in-class Jira integration;Built-in CI/CD;Deployment visibility;Embedded Trello boards; Command Instructions;Source Browser;Git Powered Wikis;Integrated Issue Tracking;Code reviews with inline comments;Compare View;Newsfeed;Followers;Developer Profiles;Autocompletion for @username mentions;Support for Mercurial	Available for cloud and self-hosted repositories;Static code analysis for +40 languages;Analysis for cloud infrastructure-as-code frameworks;Automatic analysis integrated in your CI;Code coverage tracking;Support for linter configuration files;1-click autofixes for GitHub;Static IP addresses for allowlisting Codacy;
Statistics
Stacks 41.1K	Stacks 313
Followers 33.4K	Followers 551
Votes 2.8K	Votes 248
Pros & Cons
Pros 905 Free private repos 397 Simple setup 349 Nice ui and tools 342 Unlimited private repositories 240 Affordable git hosting Cons 19 Not much community activity 17 Difficult to review prs because of confusing ui 15 Quite buggy 10 Managed by enterprise Java company 8 CI tool is not free of charge	Pros 45 Automated code review 35 Easy setup 29 Free for open source 20 Customizable 18 Helps reduce technical debt Cons 6 No support for private Git or Azure DevOps git
Integrations
Git AWS Cloud9 Sentry Microsoft Azure npm Trello Slack Confluence Docker Jira	GitHub GitLab Slack Jira

What are some alternatives to Bitbucket, Codacy?

GitHub

GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

GitLab

GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.

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.

RhodeCode

RhodeCode provides centralized control over distributed code repositories. Developers get code review tools and custom APIs that work in Mercurial, Git & SVN. Firms get unified security and user control so that their CTOs can sleep at night

AWS CodeCommit

CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools.

Phabricator

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

Gogs

The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows.

Gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD. It published under the MIT license.

PullReview

PullReview helps Ruby and Rails developers to develop new features cleanly, on-time, and with confidence by automatically reviewing their code.

Gerrit Code Review

Gerrit is a self-hosted pre-commit code review tool. It serves as a Git hosting server with option to comment incoming changes. It is highly configurable and extensible with default guarding policies, webhooks, project access control and more.

Related Comparisons

Some of the features offered by Bitbucket are:

Unlimited private repositories, charged per user
Best-in-class Jira integration
Built-in CI/CD

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

Monitoring of Technical Debt
Automated Code Review
New and Fixed Issues per commit

"Free private repos" is the primary reason why developers consider Bitbucket over the competitors, whereas "Automated code review" was stated as the key factor in picking Codacy.

Bitbucket vs Codacy