Bitbucket

Pros

This is a great service that handles my teams code changes. We've been using it for years. I've never had a problem with it.

Cons

There are no cons that I've run into. Getting to know GIT is the biggest issue. Also learning what BitBucket even is can be a hurdle.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

It integrates seemlessly with other Attlasian products such as Jira and Confluence. It also has variety of built in CI/CD tools.

Cons

It has a different way of cloning repositories when comparing to other git servers (it generates git url per user)

Pros

We started implementing version control using Mercurial about 7 years ago (in my own company). On the advice of a colleague at the time we used Mercurial as opposed to Git. Bitbucket worked perfectly with Mercurial when we needed it at the time and really helped our business. It was fast easy to use and understand and the online UI kept getting better and better.

Cons

In the last 3 years, pushing and pulling and doing any kind of actions became tediously slow. I copied some of the repos to GitHub and converted to Git to check it was not a problem with my repo, with my computer, or with the software I was using (SourceTree). In all cases the only difference was using a Mercurial versus Git repo on BitBucket. I got no response to my support query, and no response to a forum post as to the issue and when it would be fixed. I then made a decision for our entire company to move all of it's repos to GitHub and stop using BitBucket - we are doing this right now. Approx 1 year after the decision was made, BitBucket emailed all it's customers to say they would be discontinuing support for Mercurial as not enough of their customer base used it. However there was no suggestion of helping migrate all repos to Git, no support docs on how to do this and honestly this was too little too late for us. We had become so annoyed with BitBucket that we would have migrated regardless.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

We use this service to maintain a mercurial repository of our in-development game files. Since we work remotely, this keeps everyone up-to-date with progress of the development and provides us with version control we desperately need.

Cons

Atlassian has recently announced they are dropping Mercurial repository support next year. This will force us to change our workflow and/or find another service to accommodate our current needs. Other than this issue, this service has been great, especially if you want it for a Git repository instead.

Pros

This is the easy to use version control system with both GUI as well as command line facilities to maintain the versions of the code.

Cons

Rollbacking of the code to previous versions via GUI Interface needs to be improved.

Pros

A number of integration points with Jira, Trello and especially Slack. Integrations is a must have for me in Code versioning systems and this does it quite adequately.

Cons

Github has more free options including unlimited private repositories unlike bitbucket's 5 private limit. However that's where the cons end. Not many to speak of

Pros

The best thing about Bitbucket is the team features to develop and split the work.

Cons

Bitbucket is based on the Mercurial version control tool, it is a little different from git, the most know tool and my favorite.

Pros

It is very simple and packed with many features for version control. I like its autogenerated codes for cloning and branching. Its GUI is also very attractive and makes the work in Bitbucket even more interesting.

Cons

There was nothing like that about this software. It was quite good.

Pros

Bitbucket is similar to github but you get free private repositories and you won't have to spend money if you are just starting out with making projects and their deployment

Cons

It is very difficult to configure on a windows system without using the command line.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

It has a self-hosted version free for use up to 5 users. Bitbucket offer the major functionalities as others, like repositories, pull requests, git support, issues, access control, teams, etc. It also comes with great integration with other atlassian products. In cloud version all repositories are private unless you turn it public.

Cons

About self-hosted version: it's made in java and requires a huge hardware to run. Install not so trivial in linux servers. About cloud version: only 1GB of space.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

Bitbucket is a an easy git remote repository. The best part I would say is its integration with JIRA cloud.
When you use Bitbucket as your remote repo, you can simply put the JIRA issue (e.g. [SWL-746]) in your commit comments and then , when you push your code you will automatically see that the commit has been associated with the JIRA ticket and within JIRA you will be able to see that your ticket is automatically linked yo a Bitbucket branch. This way you can easily keep track of the new features that you are developing.

Cons

I would say that with almost all Atlassian products, the main issue is that their products can be very costly. Specially if your team has more than 10 members.

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

Reasons for Switching to Bitbucket

Pros

Bitbucket has very attractive pricing compared to the rivals. Other than cheaply priced and its integration with other atlassian products, it has very granular level access control defined which becomes very useful as the number of developers within the organisation grows and read/write, creating release branches, merging to master etc. becomes very critical to the workflows.

Cons

Bitbucket web experience could have much better in my opinion. The web pages load times are very high and a takes lot of time load pages. Also merging a PR in the bitbucket web is slow. Overall the web ui responsiveness can be improved a lot.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

The features we love most about Bitbucket is it's intgeration with other tools especially Atlassian tools. We use other Atlassian tools and the tight integration just makes it easy for us track projects. Another feature we like is the CI/CD feature. It eliminated the need for use to deploy a seperate system for our CI/CD needs. This has reduced the amount of work need to setup and maintain a seperate tool.

Cons

Bitbucket has very great features that makes our job easy. However, the user interface for pull requests can be greatly improved upon. We also have issues when editing a YAML file for CI/CD using the online editor.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

One of the most prominent points that you answered me about is that it is easy to use, its interface (reception) is simple and it offers multiple options for entering and registering email facebook or number phone ...other
It also supports many operating systems, whether mac or windows, and is available for android and ios

Cons

- The application does not support the Arabic language, I am sure that adding the Arabic language will provide many users in the Arab world
Having a clock showing the time on the front of the site. I think it is advisable to add a reminder of today’s date directly below it. This will be excellent, especially since the pressure of work leads many users to forget dates and make mistakes in appointments.

Pros

With Bitbucket I can have many private projects and all Git features. I can create project teams by assigning different permissions to each one. The ability to view code in the web interface itself allows for quick checks. You can also check the differences of each commit. Integration with SourceTree is a breeze.

Cons

If you use the tool with the default flow, you will have no problems. However, in some situations it is a little difficult to correct. I already had problems that the tool claimed problems in login while all the information was correct.

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

Reasons for Switching to Bitbucket

Pros

- Simple to setup
- JIRA integration: this could be really useful if you use JIRA as project management software. You can enable hooks between both projects, can easily access pull requests within cards, can post commentaries on issues using Bitbucket...
- It has default reviewers for repositories, which help code quality
- It had bit bucket pipelines as a pioneer on the industry and worked really well

Cons

- UI not so intuitive and sometimes not so simple
- Kind of laggy sometimes
- Lack of a better review process with more collaborative tools
- Lack of a bigger community

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

Intuitively and ease for settings and tweaking. When we have a new team member, 15 seconds are needed to add it and voila he's good to go. The projects itself are enough complicated so we don't need more complications from our tools.

Cons

Keep things and menus as simple and clean as possible. Power users will find a ways for their needs even if their menu are a little beep hidden / deeper than expected.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

There is a lot of thing we love about Bitbucket. First one, the possibility to create any private repository you want. I know this a common feature today, but back in the time only Bitbucket allowed to create unlimited private repositories.

Also the pipeline integration for deploys is a great thing and finally you can integrate it with a project managment software like Trello.

Cons

I would like to have a better UX, mostly because it feels a little bit old today. Almost everything works awesome, but they need to update the UX definitely.

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

Reasons for Switching to Bitbucket

Pros

Bitbucket is backed by Git a powerful tool to manage different versions of code. I love the shared way in which we can work with our colleagues using Bitbucket. Here one person can work on a particular component and other people on the same component and they both can push the code and merge all the changes seamlessly.

Cons

Bitbucket has a small learning curve people can't directly start using it without knowledge of git tho various code editors like vs code are trying to make it easier with custom buttons instead of codes but it still requires some knowledge.

Alternatives Considered

Switched From

Pros

It is easy to use and very intuitive.
It has an issue tracker and ton of other features
It is free for small teams

Cons

Although Bitbucket works together with Jira (that has an amazing set of features on its own), perhaps I would like to see the issue tracker little more advanced.

Not enough freedom when choosing the status of an issue, and not a good dashboard for tracking, for example, a milestone, or a project stage in a timeline. Yet I believe these are features that better suit some other type of product like Jira (again).

Pros

Works well with other Atlassian products with add value for all stakeholders

Cons

There is nothing specific, some of the UI and features can be improved

Alternatives Considered

Pros

Atlassian Bitbucket has a clean, user friendly interface. You can store full code, team projects, as well as code snippets, and search your code. There is support for large files. Bitbucket has easily accessible links with tutorials and tricks to get started, even at the very basic beginner level. It is fully collaborative for development teams with variable needs. The best advantage of this platform over GitHub is it allows for private code repositories in the free model. You can control access to your code with public or private repos, and even fine tune access control with additional rules and extensions on the premium mode. There are tons of excellent integrations, including AWS, Microsoft Azure, Python, Visual Studio, Circle CI. and more. New beta features seem to be added regularly. The free model is great and the upgrades are reasonably priced. This is a well-rounded, excellently performing, continuously expanding code hosting platform that is well-suited to support your individual or team projects.

Cons

Previously, there was a slight learning curve in the processes, but this has been smoothed out. There are no real cons that I can think of, except that the open-source social celebrity aspects of GitHub are not a prominent feature here. However, if you are not looking for these aspects, you will likely be very happy with all of the features which are included to support your building endeavors.

Pros

It gains power from the ability to integrate with other tools like Jenkins, Jira, and CodeSonar. If we encounter an issue with Bitbucket, we may quickly solve it by consulting its manual or the internet. Additionally, it contains helpful documentation that beginners may access and learn from. By limiting the number of users and granting certain user groups access to the repository, Bitbucket offers security by preventing unauthorized people from approving pull requests. Pull requests are easily produced and display the changes between two versions, making it easier to see what has been changed. The deployment of processes and the completion of user stories and tasks are both greatly aided by the connectors to project management platforms like Jira.

Cons

The fact that Bitbucket is less well-known than GitHub and lacks an open table displaying how frequently my repository is pushed are two things I don't like about it. On GitHub, a rectangle with squares in various hues of green is used to symbolize the frequency of commits. The comments in a pull request must be properly arranged. Bitbucket receives less community assistance. Additionally, it would be beneficial if they enhanced their diff tool to make the disputes more obvious.

Pros

Atlassian Bitbucket is one of the most popular web based version control repository. Managing code and project are simple with the help of it. We also use Git repository for some projects. Pull requests for facilitate code review also help in improving the coding and help in knowledge sharing with in the team. Code search is also an excellent feature which save time and help us to reach the right code in short time. The Bitbucket pipelines cares for your code from coding to till release. Storing the large media file is also easy with help of Git LFS. Diff views improved in the latest version and we don't need any third party tools for review the side-by-side code changes. Third party tool integrations is also improving day by day.

Cons

Bitbucket self hosted is complex to deploy and need assistant from experts as bad practices in branching can end up with the a lot of troubles. Managing different collaboration is complex so I prefer working on same branch. The free version is good to practice the things but they should also remove some limitation from it.

Pros

Whenever a colleague creates a PR, we can manage and debate it among ourselves. The team can design the policies depending on their developer workflow with the assistance of options like branching models and constraints. Its remarkable features and version control capabilities make it the most useful. Users may monitor and handle bugs, feature requests, and other activities directly from the code repository thanks to its integrated issue-tracking system.

Cons

Because the search possibilities are limited and you must separately search for repos and code in repos, finding items can be time-consuming. We haven't noticed the Codeowners file feature on the roadmap, which is still under development.

Pros

Bitbucket is excellent when integration with JIRA - it gives the team the ability to easily view status and get updates across systems. It also allows integration with the JIRA release and workflow tools

Cons

While Bitbucket is steadily being improved, it does lack a few features that it's main rival Github does. The Pull Release view is probably the main thing here - while it has many of the capabilities of Github, it just lacks some of the polish and ease of use features.

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

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

there are several aspects of Bitbucket that I found particularly impressive and impactful. Firstly, what I liked most about Bitbucket was its seamless integration with our development workflow. The ability to create and manage repositories, branches, and pull requests directly within Bitbucket simplified our code collaboration process significantly.One of the most impactful features of Bitbucket was its robust version control system. The ability to track changes, revert to previous versions, and compare different branches made it easy for us to manage our codebase effectivelyThe integration of Bitbucket with our existing business infrastructure was relatively straightforward. Overall, Bitbucket proved to be an invaluable tool for our web development projects.

Cons

While Bitbucket has been an invaluable tool for our web development projects, there were a few aspects that could be improved uponwe occasionally encountered difficulties when configuring complex CI/CD pipelines within Bitbucket. While the basic configuration was straightforward, more intricate setups or customizations required additional effort and expertiseOne aspect I found limiting was the lack of customization options for the user interface. Bitbucket's interface is functional, but it would be beneficial to have more flexibility in customizing the layout, color schemes, or overall visual appearance to suit individual preferences or align with specific branding requirementsIt's important to note that while these were the aspects we liked least about Bitbucket, they did not significantly hinder our overall experience with the platform

Pros

The GUI is pretty easy to use and most features are easy to find through the multiple menubars and dashboards.

Cons

There are janky moments were the GUI has issues or just dies completely. This happens much less regularly recently. But it is worth noting. I also am not a fan of the pipelines, as compared to the other features its a bit behind other companies

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

Pros

Bitbucket is a good version control system, one can easily create branches, delete branches, commit code, merge code and many more. For a beginner it's a good tool to learn about git and to do practice. The advantage of Bitbucket is you can integrate it with project management tools such as JIRA, also you integrate Bitbucket with CI/CD tools such as Jenkins that is the most likeable feature of Bitbucket. Bitbucket is free for single user, so one can do practice easily during learning phase.

Cons

Prices are bit high for paid version, Bitbucket provide free version to only <=5 employees, for companies with more than five employees Bitbucket does not provide free service. Also Bitbucket features are outdated as compare to GitHub, GitHub provides lot of extra features as compare to Bitbucket. Sometimes while switching from one section to other Bitbucket was slow.

Pros

Simple to utilize when integrating CI/CD with automation pipeline technologies like Jenkins. The issue tracker and branch comparison views are both great. Project labels and milestones may also be created. Jira integration allows you to monitor the pull request from that platform. It also offers some nice third-party software integrations. You may import from SourceForge, SVN, Git, and more. Additionally, if you need to search for a certain item in the repository, I enjoy the search possibilities. Additionally, you may build your own wiki. To commit my code, I use this together with SourceTree (another Atlassian product). Excellent compatibility with other Atlassian applications.One of Bitbucket's biggest advantages is how well it integrates with all of Atlassian's other products, including Jira and Confluence.

Cons

The hook system needs an extra plugin to be controllable and easy. Additionally, I had hoped to find methods to quickly download diff patches and a simple method for obtaining LOC information from pull requests, both of which are currently lacking. In addition to this, a few other reporting tools for executives may be used to assess the productivity of developers, etc.

Alternatives Considered

Pros

The product is quite easy to use, tough user and project management on different projects can be a little confusing. Widely used and integrated with a lot of external services. I especially liked the seamless integration with Vercel to publish NexstJs projects without any problem - usually quite hard to configure. Free tier gives you a lot of space and options, nobody else does.

Cons

Account management could be improved. The border between free tier and payment version is not always easy to understand.

Alternatives Considered

Switched From

Reasons for Switching to Bitbucket

Pros

I love Bitbucket because it is a solution with a clean and friendly interface, that is, its interface is intuitive so that any user can use it without problems. Bitbucket facilitates the administration of the repositories, since it allows its centralization, it also makes it possible to fork it or create branches, creating branches gives us the advantage of being able to make changes to our project without the need to affect the original code, it even makes it possible to code merge, so different team members can work on different parts and then the team can come together once compatibility has been verified and of course if changes or bug fixes are required so that the final result be a clean code. This tool is not only ideal for version control but also gives us the advantage of having a space where it is possible to plan projects, create them, collaborate on them through a number of members that adjust to our needs through public or private repositories and even test and implement, so it contains all the necessary functions for the development of software or applications efficiently. It also makes it possible to assign projects and divide them into several teams, thus being able to manage different projects from one place.

Cons

One of the things that we like about this efficient software is that its number of members is somewhat limited, that is, it allows access to 5 members, but if the number of members necessary to carry out a project is greater, it will be necessary to pay for the rest, this can make access for students or small businesses a bit limited due to its costs, another drawback that I have noticed is that during a code review there is no quick visualization of the project and this can make this process take longer than expected, it would be ideal if this function could be optimized and speed up.

Pros

Bitbucket is a great git code management software. I use Bitbucket to store my code, collaborate with my team who are working on the same project as me, test my code either in developer mode or production mode, test and deploy my code in a different format or by importing using git batch. Bitbucket has great extensive features that enable me to own a private code repository free of charge if my team is less than five and upgraded version for team greater than five between a price range of 3 -6 dollars per month which is cheaper compared to what you can achieve with Bitbucket. Its ability to accommodate different programming languages is superb. It also has a great feature for a quality purpose known as version control and continuous integration which helps me to update my code at my convenience without loss or issues arising from my computer clash, thereby making it the best cloud solution. It is easy to use though requires a lot of expertise in the field of software development. I also use Bitbucket to host my project after pushing to my repository. It is very faster and updated regularly by their developers.

Cons

From what I can observe while using this Bitbucket software as compared with other code repository software, is that sometimes I find it difficult to use as regards its user interface and the way it is structured though every company has its unique selling point. I said this because if am using software of the same type before and then decide to migrate to bitbucket, I might find the user interface interaction difficult unless I started with bitbucket first.

Pros

BitBucket's integration with Jira is spectacular. I can go to BitBucket commit and see what problem it was solving since it has a Jira link. BitBucket branches can be created right from Jira as well. Jira also shows all commits. This makes information gathering easy and code review pleasant.

Cons

BitBucket has more downtimes that I like. In 2020, there were 2 downtimes within a gap of a month. This is the only thing that bothered us about BitBucket.

Alternatives Considered

Reasons for Choosing Bitbucket

Reasons for Switching to Bitbucket

Pros

Bitbucket has a very friendly interface that is easy to understand and understand, it allows you to maintain control and order of all your elements and keep track of each modification that was made and by whom said modification was made.
It allows you to establish different types of permissions as necessary to have a better control of who can perform what actions within the repositories that are created in bitbucket.
Once you get familiar with the tool, everything is easy to do and locate any option you are looking for to carry out your tasks.

Cons

Sometimes the way it provides you to search within each repository can be somewhat cumbersome, requiring you to write the exact name of the component you may be looking for in order to show you a result, making the searches more strenuous since you must know the exact name of the component or it will be very difficult to find it.
In some cases, when versioning certain changes, Bitbucket interprets them as a total change within the component and shows as if the file was being completely modified even if you are only modifying some lines of code.

Pros

First thing to note is there's two versions of the software - self hosted and cloud hosted on bitbucket.com. Make sure you know what you're buying as those two vary sometimes significantly in features (e.g. lack of automerge branches in cloud hosted version, which might be a showstopper for you). However, they're constantly putting out updates, so make sure to check the latest version comparisons. In general, the cloud version is the 'skinny one'.
Reviewing changes has always been a breeze and the major strong point of bitbucket - it's very easy to start comments, reply, assign tasks, require min number of approvals before merging, etc.
The support for git-flow is seamless - the versioning is working always as expected, with auto-merge down to the correct branch detected correctly.
We have setup a build engine to it so you can't merge a branch that's failing builds, which works great.
The overview of code, branches, PRs is working great, the full-text search throughout entire codebase is amazingly fast (although, it's lacking some basic filters).

Cons

Some pull requests are limited to review only the 1000 files - this is unfortunate, because if you have very large projects and with some refactoring you're easily over that number, this doesn't give you ability to see that-very-specific project files you want to check upon. It's annoying as there doesn't seem to be any good reason for the limit.
If you have large teams (e.g. imagine 160 people, split into 15 teams), you can't group people which would be useful to see ("PR's of my team" for example would be a nice feature to have).
Also missing is what's seen nowadays in github - a recognition for the language that's shown.

Pros

Bitbucket has a good UI and is very good for most of the repository related tasks. It has JIRA integration, so if you put your JIRA ticket numbers in the commit message, Bitbucket will link the pull requests into JIRA. This makes it very easy to access commits and the associated JIRA tickets from bitbucket itself, and vice versa.

It has good branch visualization tools. It lets you select branches from a drop down and compare them with other source barnches. The diff visualizer is pretty good too. It even has good graphical icons to show which branches have been merged/rebased where.

You can use command line git to manage repos as well. With their REST APIs it is possible to create repositories from the command line, which is very useful in cases where you have to do the tedious task of creating hundreds of repositories very similar to one another.

Cons

I was unable to find documentation on their APIs to set group and permissions access restrictions from the command line. This was required because we needed to create 100s of repos and allow our users to access them. Because we could not find API documentation easily and were in a time crunch, we had to have developers spend several days manually granting permissions using the web-console. Bitbucket should have these APIs clearly visible and documented.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

I think the biggest pro with using Bitbucket is that it integrates extremely well with JIRA. This allows you to track your tickets with the branches you're working on and to easily see its progress during each sprint. It's intuitive and straightforward to use. It's also quick and almost rarely did we have any technical issues. Whenever we did have some issue, it was just with some expiring licenses which was easy to resolve. Permissions are additionally easy to manage. Overall, it's just an amazing tool that is 100% essential for our software team as it manages our repositories and allows to share, review, and manage our code across all teams.

Cons

The only downside I can think of is the scaling costs associated with it for the paid plans. Bitbucket charges per user. We have around 100 software engineers so it adds up a lot. Also, our engineers are quite experienced so working in Bitbucket hasn't been that much of a challenge. I've heard that engineers will lesser experience in repository management find Github to be easier to learn and implement but again, with greater experience comes a more expansive toolset.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

The web-based app is fantastic. It has a great UX, its easy to use, and it just looks nice. My favorite feature is the side-by-side comparison for diff comparisons. Whenever you have code with particularly long lines, the traditional word wrap comparison becomes virtually unusable. But Bitbucket has a really nice side-by-side comparison that allows you to scroll horizontally. It is indispensable. It also integrates with Jira really nicely. Whenever you name a branch after a Jira issue, you get a really handly link in Bitbucket that will display the Jira issue card in modal.
Lastly, Bitbucket has better prices for private repos (especially for smaller teams).

Cons

Not a strong mobile presence (albeit, there are few cases where you really need to be able to interact with yoru code repos from a mobile device, but it does come up from time to time)

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

A better integration with other Atlassian products as well as other products like Slack, the very useful pipeline feature that automates the building process, the simplest interface, private repositories even for free users.

Cons

To get the most and complete experience for this product is only if you have the Atlassian ecosystem,
not so stable as GitHub, but this problem is not common, unable to archive repositories, the search needs a little bit improvement.

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

Reasons for Switching to Bitbucket

Pros

First of all it is free for small team. For bigger teams it has really reasonable prize. I personally love and prefer Atlassian's products such as Bitbucket, Trello. The Atlassian team behind the product continuously improves their products. Since I started using Bitbucket 5 years ago, they added many features. It has no limitation and pretty good integration with trello, jira and other project management products.

Cons

Fortunately, during the last 5 years we didn't face any difficulties using Bitbucket. It works pretty well with my team. But keep-in mind that free version is only for 5 developers for a team.

Pros

Version control has a big learning curve, some people pick it up straight away, others don't - and this is where BitBucket shines, it's a fantastic user interface, especially for those that struggle with working with version control.

Cons

It is lacking a few features, which we've been promised are coming, so hoping these features arrive soon.

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

Pros

I have been using Bitbucket (personally and commercially) for couple of years and I'm really satisfied with the services and features that they offer. Letting free users create unlimited repos and allowing up to five users is a good way to go, which attracts more users. Pull requests helps to get code reviewed by experts and get them approve before it available for others and helps to maintain quality code leading to quality software. More useful features like Pipeline lets user to deploy/release more often.

Cons

As a market leader, pricing plans can be adjusted to attract more

Alternatives Considered

Reasons for Choosing Bitbucket

Switched From

Reasons for Switching to Bitbucket

Pros

Overall very good product. All features of GIT are nicely implemented, haven't had much issues with it. Also, the pricing is based on users, not based on repository count like Github. So the prices are very fair, especially when you have a lot of repositories (for web design agencies like us).

Cons

One thing I'm not too happy about is its inability to reopen a declined Pull Request. I do not see any reason it cannot do that. An issue was raised and discussed (Bitbucket Issue #4954), and was not resolved.

Another thing I didn't like was that there was once Bitbucket was hacked, and one of our repositories (lucky it wasn't a very important one) was hacked and I had to speak with a Bitbucket rep to restore our data. Took a day or two on that.

Alternatives Considered

Reasons for Switching to Bitbucket

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

Bitbucket is an incredible version control system that makes it incredibly easy to collaborate on code and manage projects. It allows me to easily track changes, store files, and work with others on the same project. The user interface is intuitive and I appreciate the ability to customize my workspace to fit my needs.

Cons

The pricing for Bitbucket can be a bit expensive for smaller projects. Additionally, some of the features can be a bit confusing to use at first.

Pros

I like the auto-tagging of JIRA issues with code commits on PR. The bare minimum requirement for a functional version-control system is fulfilled.

Cons

Github has started supporting multi-line commenting on PRs. I don't think I can find any dev who won't like this feature.
It also has a colorful README rendering along with build and test coverage tags. I don't care much about README renders but am out-of-the-box CI integration with Jenkins can help in outputting data about many useful tags like code test coverage, code standards, reference available or even licensing.
There are many extensions built around Github to augment the experience, one in particular that I like, called OctoLinker, has the ability to link the imports with original source code repository. This could be a useful feature in source code view.

Alternatives Considered

Reasons for Switching to Bitbucket

Pros

I like how robust their website is on terms of pull requests and integrations with JIRA and other atlassian products. You can store private repo's and manage it. The pull Request feature is the strongest in my opinion, with reviews and linking to JIRA. So it automatically can close tickets once you merge/accept a pull request. If you link the commits with a JIRA issue it also updates with them. They recently simplified the UI and their own home made SourceTree Visual App has received some substantial upgrades over the years and it's one of the best tree-based git history apps out there. In all honesty, it's a simple git control hosting website you can use online or host by yourself. It's really good.

Cons

The UI used to change a lot but now they've settled. Sometimes, compared to github, processing big pull requests (loading the changes/previewing) can be a little slow. Sometimes the integrations with JIRA, can feel like a miss if you don't use it, because Github has a lot of those features that Github might miss.

Alternatives Considered

Reasons for Switching to Bitbucket