Need advice about which tool to choose?Ask the StackShare community!
Fisheye vs GitLab: What are the differences?
Introduction:
In this Markdown document, the key differences between Fisheye and GitLab will be highlighted. Fisheye is a source code management and analysis tool developed by Atlassian, while GitLab is a web-based Git repository management platform.
Integration Capability: Fisheye primarily integrates with other Atlassian products like JIRA, Confluence, and Bitbucket. It allows for seamless integration between these tools, enabling a smooth workflow for software development teams. On the other hand, GitLab is an all-in-one platform that offers not only Git repository management but also integrated CI/CD, issue tracking, wiki, and more. GitLab's integration capabilities extend beyond its own ecosystem, supporting integrations with external services like Jenkins, Kubernetes, and Slack.
Code Review Features: Fisheye provides a comprehensive set of code review features, including side-by-side diffs, commenting, and annotation. It facilitates collaborative code reviews and enables teams to provide feedback directly on the code. In contrast, GitLab also offers code review capabilities with similar features, but it goes a step further by integrating a built-in Continuous Integration/Continuous Deployment (CI/CD) system. This integration allows for automated code testing, validation, and deployment directly from the code review process.
Git Workflow Support: Fisheye is designed to work with multiple version control systems, including Git. While it can be used for Git-based repositories, its primary focus remains on centralized version control systems like Subversion (SVN). On the other hand, GitLab is built specifically for Git-based workflows. It provides native support for Git functionalities, such as branching, merging, and rebasing.
Scalability: Fisheye is a self-hosted tool that is typically installed on a dedicated server. Its scalability is dependent on the hardware and resources allocated to the server. GitLab, on the other hand, offers both self-managed and cloud-based options. The self-managed version allows organizations to deploy GitLab on their own infrastructure, providing scalability based on their own server resources. The cloud-based option offered by GitLab, known as GitLab.com, provides a scalable and managed solution that eliminates the need for organizations to manage their own infrastructure.
Issue Tracking and Project Management: Fisheye does not have built-in issue tracking or project management capabilities. It primarily focuses on code analysis and review. In contrast, GitLab provides a complete project management suite that includes issue tracking, project boards, milestones, and more. This allows teams to manage their software development projects within the same platform, streamlining communication and collaboration.
Community and Support: Fisheye is a proprietary software developed by Atlassian. It has an active user community and receives support from Atlassian through documentation, forums, and support tickets. GitLab, on the other hand, is developed as an open-source project and has a large and active community of contributors. This broad community support provides users with access to a wealth of resources, including forums, community-contributed documentation, and open-source extensions.
In summary, Fisheye is primarily focused on analyzing and reviewing code, with integrations to other Atlassian tools, while GitLab offers an all-in-one platform with native Git support, built-in CI/CD, issue tracking, project management, and scalable deployment options. GitLab also benefits from a larger and active open-source community.
I first used BitBucket because it had private repo's, and it didn't disappoint me. Also with the smooth integration of Jira, the decision to use BitBucket as a full application maintenance service was as easy as 1, 2, 3.
I honestly love BitBucket, by the looks, by the UI, and the smooth integration with Tower.
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?
Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.
SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.
As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?
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.
Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.
Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!
At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.
Pros of Fisheye
Pros of GitLab
- Self hosted508
- Free430
- Has community edition339
- Easy setup242
- Familiar interface240
- Includes many features, including ci137
- Nice UI113
- Good integration with gitlabci84
- Simple setup57
- Free private repository34
- Has an official mobile app34
- Continuous Integration31
- Open source, great ui (like github)22
- Slack Integration18
- Full CI flow14
- Free and unlimited private git repos11
- User, group, and project access management is simple10
- All in one (Git, CI, Agile..)9
- Built-in CI8
- Intuitive UI8
- Both public and private Repositories6
- Full DevOps suite with Git6
- Build/pipeline definition alongside code5
- CI5
- So easy to use5
- Integrated Docker Registry5
- It's powerful source code management tool5
- Issue system4
- Dockerized4
- Unlimited free repos & collaborators4
- Security and Stable4
- On-premises4
- It's fully integrated4
- Mattermost Chat client4
- Excellent4
- Great for team collaboration3
- Built-in Docker Registry3
- Low maintenance cost due omnibus-deployment3
- I like the its runners and executors feature3
- Free private repos3
- Because is the best remote host for git repositories3
- Not Microsoft Owned3
- Opensource3
- Groups of groups2
- Powerful software planning and maintaining tools2
- Review Apps feature2
- Kubernetes integration with GitLab CI2
- It includes everything I need, all packaged with docker2
- Multilingual interface2
- HipChat intergration2
- Powerful Continuous Integration System2
- One-click install through DigitalOcean2
- The dashboard with deployed environments2
- Native CI2
- Many private repo2
- Kubernetes Integration2
- Published IP list for whitelisting (gl-infra#434)2
- Wounderful2
- Beautiful2
- Supports Radius/Ldap & Browser Code Edits1
Sign up to add or upvote prosMake informed product decisions
Cons of Fisheye
Cons of GitLab
- Slow ui performance28
- Introduce breaking bugs every release8
- Insecure (no published IP list for whitelisting)6
- Built-in Docker Registry2
- Review Apps feature1