Need advice about which tool to choose?Ask the StackShare community!
Bitbucket vs Fisheye: What are the differences?
Introduction
In this Markdown code, we will discuss the key differences between Bitbucket and Fisheye, which are both tools commonly used in the software development industry.
Code Hosting: Bitbucket is primarily a code hosting platform that allows users to host and share their repositories, including version control features like Git and Mercurial. On the other hand, Fisheye is a code viewer that provides a centralized place to browse and search across multiple repositories from different version control systems.
Integration with Jira: Bitbucket has a strong integration with Jira, Atlassian's issue tracking system. It provides seamless integration with Jira, allowing developers to link their code changes to Jira issues for better traceability and collaboration. Fisheye, on the other hand, does not have direct integration with Jira and requires additional plugins to achieve similar functionality.
Code Review: Bitbucket has built-in code review capabilities, providing a collaborative environment for teams to review and discuss code changes before merging them into the main branch. Fisheye, on the other hand, lacks native code review features and requires the use of additional tools or plugins to facilitate code reviews.
Supported Version Control Systems: Bitbucket supports both Git and Mercurial as version control systems, providing flexibility for developers to choose their preferred system. Fisheye, on the other hand, supports a wider range of version control systems, including Git, Mercurial, Subversion, and Perforce, making it suitable for organizations that use different systems across their projects.
Repository Management: Bitbucket offers advanced repository management features, allowing users to create and manage branches, set up permissions and access controls, and define workflows specific to their projects. Fisheye, on the other hand, focuses more on code browsing and search capabilities rather than extensive repository management.
Pricing Model: Bitbucket offers free hosting for small teams and offers a flexible pricing model based on the number of users for larger teams or organizations. It also provides options for self-hosted deployments. Fisheye, on the other hand, is a commercial product that requires a paid license, making it more suitable for enterprises or organizations with specific requirements.
In summary, Bitbucket is primarily a code hosting platform with integrated code review and Jira integration, supporting Git and Mercurial as version control systems, while Fisheye is a code viewer with support for a wide range of version control systems and focuses more on code browsing and search capabilities. Bitbucket also offers more extensive repository management features and has a flexible pricing model, whereas Fisheye is a commercial product with a paid license.
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?
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.
Pros of Bitbucket
- Free private repos905
- Simple setup397
- Nice ui and tools349
- Unlimited private repositories342
- Affordable git hosting240
- Integrates with many apis and services123
- Reliable uptime119
- Nice gui87
- Pull requests and code reviews85
- Very customisable58
- Mercurial repositories16
- SourceTree integration14
- JIRA integration12
- Track every commit to an issue in JIRA10
- Deployment hooks8
- Best free alternative to Github8
- Automatically share repositories with all your teammates7
- Source Code Insight7
- Compatible with Mac and Windows7
- Price6
- Login with Google5
- Create a wiki5
- Approve pull request button5
- Customizable pipelines4
- #2 Atlassian Product after JIRA4
- Unlimited Private Repos at no cost3
- Also supports Mercurial3
- Continuous Integration and Delivery3
- Mercurial Support2
- Multilingual interface2
- Teamcity2
- Open source friendly2
- Issues tracker2
- IAM2
- Academic license program2
- IAM integration2
Pros of Fisheye
Sign up to add or upvote prosMake informed product decisions
Cons of Bitbucket
- Not much community activity19
- Difficult to review prs because of confusing ui17
- Quite buggy15
- Managed by enterprise Java company10
- CI tool is not free of charge8
- Complexity with rights management7
- Only 5 collaborators for private repos6
- Slow performance4
- No AWS Codepipelines integration2
- No more Mercurial repositories1
- No server side git-hook support1
Cons of Fisheye
Sign up to add or upvote consMake informed product decisions
What is Bitbucket?
What is Fisheye?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Fisheye?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Fisheye?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+4
+32+34