Bitbucket

Pros

Great integration with other Atlassian tools that we utilise within company already.

Cons

No easy online IDE built-in for quick fixes/updates/work online without own local IDE.

Pros

It’s a brilliant way to house and visualize your repos, review and comment on pr’s and see your full commit history in one place

Cons

It can be a bit buggy at times which can really hinder being able to work collaboratively

Pros

It is deeply integrated with the Atlassian suite of tools which is convenient for using Jira alongside Bitbucket.

Cons

It is not as feature rich, significantly buggier and more difficult to use than its main competitors.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

Bitbucket holds everything you would need for a development team. Having code versioning and branches in Bitbucket makes things organised and professional. The lower tier Bitbucket is good bang for your bucks, but the premium holds for example privacy/security settings that you might consider using, especially if you are aiming for privacy/security certificates.

Cons

As quite often, Atlassian's products are somewhat hard to start with, but when you get to know their ways of thinking, everything is quite straight forward – and to be honest, their products are being developed with UX in mind these days.

Pros

Good integration with Atlassian products

Cons

I don't like the graphic interface, this could improve

Pros

Bitbucket works nicely with other Atlassian tools like Jira and Confluence. Makes managing projects and CI/CD easier. It has built-in tools for code reviews, like inline comments and pull requests.

Cons

Bitbucket is sometimes slow in performance such s slow loading of pages. There are no revert features of the built-in tools. code once committed cannot be rolled back.

Pros

It's a great tool for VCS, and you can easily track back commits and changes.

Cons

It is not easy to find commits through different branches

Pros

When working on a new feature for our project, I created a pull request on Bitbucket. My team members were able to review the changes, leave comments directly on the code, and suggest improvements. This streamlined our collaboration process and ensured that the final code was of the highest quality before merging it into the main branch.

Cons

Its occasional slowness in loading larger repositories and navigating between branches.

Pros

Our team uses Bitbucket for VCS and storing all our code.

Cons

Nothing specific I dislike from Bitbucket, it has met all my expectations

Pros

It makes project management a breeze. For instance, I can easily create branches directly from my Jira issues, streamlining our workflow.

Cons

It can be slow at times, especially with large projects. Waiting for actions to finish can be frustrating.

Pros

Gitbucket offers robust access controls and permissions, allowing our team to define and manage user access at various levels, enhancing security.

Cons

It requires some learning curve for individuals who are new to version control systems.

Pros

It is a great productRepositories are organised and managed easilyAccess control is done easily ( can create groups and provide specific acces and later add users to these groups)Branching is availableCan be used for issue tracking and integration with JiraPIpelines and deployments can also be set up

Cons

Nothing to dislike about bitbucketWe use the managed service by Atlassian

Pros

Integration with jira is a must.. easy to integrate devils process from comments in commits and organyze release easly

Cons

Some graphic view are not so easy to understand and easy to use

Pros

the JIRA integration, linking with the tasks or stories. Failure tacking, risk analysis, continuous integration

Cons

it works great both the web and desktop instances

Pros

I could easily setup CI/CD pipelines using BitBucket Pipelines.

Cons

I found managing an organization on BitBucket quite difficult.

Pros

Easy to use, very clean and intuitive interface, easy to manage teams, good integrations with the likes of Jira... In short, one of the best (if not the best), code repository software out there, especially if you use other Atlassian software as it has unparalleled integration within that ecosystem.

Cons

More dashboard views would be nice but that's just nick picking, it is not a key feature

Pros

I used Bitbucket because of its integration with Jira, which also provides easier source code management and easier version control to manage the CI/CD.

Cons

I think for its purpose and uses, I don't have anything that I didn't like about it.

Pros

I used Bitbucked as a version control system. This was used with ArgoCD for continuous deployment. The environment is so easy to use and commiting changes was seemless

Cons

Nothing on this for now. Maybe I'll have some after I explore other capabilities of the application

Pros

It makes it very easy to see the entirety of a project source code at a glance.

Cons

Nothing to speak of, it is easy to use and manage.

Pros

Easy access, easy implement in Visual Studio Code

Cons

Every pull request from Visual Studio Code need authentication

Pros

I have seamlessly integrated it with Snyk and Github, experiencing a remarkably smooth integration process, coupled with its user-friendly nature.

Cons

There are no changes we faced using the tool.

Pros

Bit Bucket integrates almost seamlessly with Jira. It should be on the same bill and invoice but it's not.

Cons

It should be better integrated with Jira from a billing and management point of view. I'm not a dev but our developers prefer to use Git.

Pros

I enjoyed working with bitbucket and Google Cloud platform

Cons

I hope the documentation on bitkucket will be more extensive

Pros

Its ability to organize code and provide access to many different developers in different branches of development.

Cons

Sometimes confusing, but the readme files help explain it in a basic simple way. It is best if you have an experienced bitbucket user on your staff to answer some of the hard questions or use the help area online.

Pros

It is possible to add hooks and link specific actions through various add-ons. Jenkins is an add-on that allows you to set up a continuous integration system and participate in a Devops initiative. Bitbucket connects to HipChat. Pull requests can trigger warnings in HipChat rooms. It is possible to create a new subject line from a JIRA issue. This makes it easier for people accessing the JIRA issue to find the code.

Cons

The search engine function is reduced. It is believed to crawl repository names and descriptions, but does not search the code. It is necessary to set up a search engine from another site. When you try to log into a project or repository that you do not have access to, Bitbucket just gives you an error, but does not provide any way to notify the project/repository owner that you want access or know the owners name.

Pros

A Git-based source code repository hosting service with a friendly user interface and a clear layout

Cons

Hard to find the details of a closed pull request that is not very recent. The recent ones are displayed on dashboard.

Pros

Easy to version source codes.
We can ensure maximum protection for our valuable source codes.
Can set access permissions for repositories.
We can easily review source codes

Cons

When the service is down, it will remain down for more than 1 or 2 hours.
Unable to archive repositories.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

What I liked the most about using Bitbucket was the possibility of interconnecting everything from JIRA and Confluence directly and seamlessly to my repositories. This helped my team not only to save time but also to keep track of everything happening around our development cycle in a way that felt natural.

Cons

The interface tries to differentiate from GitHub a lot, and sometimes it feels it is not something you need to innovate into; some things are just the way they are. I found the project->repository structure confusing, and navigating through them wasn't easy.

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

Reasons for Switching to Bitbucket

Pros

I am using this version control tool last from 2 tears and easily manage code using this. you can work with many peoples for one project.

Cons

code revert process is so complicated if there is any bug in code and you want to do code revert then the process is complex but when you are new with this tool.

Pros

User friendly Git system. Integrates well with Jira and
Confluence for issue tracking/knowledge sharing.

Cons

Stopped licensing the self-hosted server version and forced everyone only cloud or Data Centre. Also while still good, Github is starting to edge BitBucket in features.

Pros

It works as a code repository. I am using it because it was grandfathered in. I do like the integration with Jira. I do like the integrations that are called "pipes".

Cons

Bitbucket is too slow on the feature requests. I have been waiting for ARM support for years. I wish I could add an approval step to the pipeline. There seems to be an outage every month.

Pros

I think it’s great for the integration with Jira, so it’s really useful to integrate in an agile team

Cons

I think the only con that I can see is that there is not so many community out there as in other platforms as github and that they don’t have the dark mode

Pros

Great Interface for Version Control and and Project Management.

Cons

The cost gets high when scaling users. The downtimes are also an severe issue.

Pros

Whenever we push some changes into a repository and when we click the create pull request button, it automatically selects the source branch as the latest pushed branch and the destination branch as the develop branch.

Cons

When we are trying to add comment in a PR, there are two options, one is review and other is resolved. The review button is highlighted with blue color, which makes it attractive, but mostly people try to resolve the comments.

Pros

Bitbucket is a Git-based source code repository hosting service that offers several standout features likes Built-in CI/CD with Bitbucket Pipelines and others.

Cons

Bitbucket is not as widely adopted for open-source projects compared to GitHub or GitLab, which can limit collaboration opportunities for open-source-focused developers.

Pros

It is very simple to use, you simply create your repositories and then can push your code to them.

It has great security features such as 2 factor authentication.

I think you can create unlimited repositories

Cons

The process for reviewing merge requests was more complex than on GitHub.

Pros

Bitbucket is awesome for developers and teams alike! One big plus is its support for Git repositories, making it super easy to manage code changes and collaborate effectively. With Bitbucket, you can branch out and experiment without worrying about messing up the main code, thanks to its nifty branching and merging features. Plus, it plays well with other tools like Jira and Trello, making project management a breeze. And hey, security is important too, and Bitbucket's got you covered with customizable access controls. It's basically a go-to platform for keeping your code organized, your team on track, and your projects running smoothly.

Cons

The Atlassian suite can be expensive if you aren't using the free versions.

Pros

Private repos with free pipelines. No cost for small teams.

Cons

I cannot say any cons for private repos and pipelines.

Pros

Probably the integration with the complete Atlassian suite is what attracts me the most, working with Jira, Trello, Confluence and being able to solve problems from a support or customer service common to all these applications, greatly influences the decision to work with Bitbucket.

Cons

Well, there are two clear competitors that take the majority of the repositories, but they are not mutually exclusive, you can use another of them, perhaps better in some aspects, while still taking advantage of the integration with the other applications.

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

Reasons for Switching to Bitbucket

Pros

Relative to other competitors, they use to offer more customisability options that might be necessary for enterprise.

Cons

Generally poor reliability and worse developer experience.

Pros

The integration with Jira is one of our favourite BitBucket features.
The UI is always clear and allows for full configuration of rules in order to approve the PR.
The branching model configuration is also easy and very user friendly.

Cons

When managing more workspaces the UI gives by default the latest viewed workspace, except for the personal workspaces.
This could be confusing at first but it's a minor issue an user can get used to.

Pros

It's part of the Atlassian ecosystem and therefore the entry was very seamless.

Cons

It lacks granular security controls and policies that we might require.

Pros

I like how Bitbucket works with Jira. For example, making a new branch in Bitbucket creates a task in Jira. It helps us work smoother and stay organized.

Cons

I find Bitbucket can be slow at times, especially with large repositories. Also, some features could be more user-friendly.

Pros

It makes managing code repositories easy, like when we merged our latest feature branch with no issues.

Cons

When managing multiple repositories, finding specific settings or options can be a bit of a hassle.

Pros

Built-in CI/CD, tight integrations with the rest of the Atlassian suite, seamless collaboration features, and clean UI.

Cons

Vendor lock-in, occasional complexity in setting up advanced workflows and a steep learning curve for beginners.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

It completes all the DEVOPS Atlassian ecosystem, you have a option for server or sas version and you also have a API in order to implement a lot of extensions or inderactions with the repository.

Cons

It must implement stuff like Github and Gitlab in order to be more competitive.

Pros

The most liked feature of Bitbucket is its integration with JIRA projects. It's easy for project managers to track the process of deployment, and for change management to check in with security on Pull requests.

Cons

The pipeline aspect of Bibtbucket is the least of my team's favorites. We believe that CurcleCI does a better job. It would be preferred if it's free like its counterpart, GitHub.

Pros

It's a great tool for VCS management, allowing peer code review before merging any branch

Cons

Repository increases too high and it is not easy to wipe out old data to free some space

Pros

It is similar to Jira Attlasian, however better in terms of ticket management.

Cons

Two similar products from the same product company.
I use Jira, Bitbucket and Fisheye.
They all look similar.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

- can allow access over VPN- integration with Jira- source controll- pipeline

Cons

- slow load- no cross pipeline- no code highlights on pr review