Bitbucket

Puntos a favor

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.

Puntos en contra

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.

Bitbucket is a very useful version control tool, easy to master and with many useful tools that will help you speed up your work, of course it has certain shortcomings that could be improved over time, but at the end of the day it is a tool very useful.
From the most basic to the most complex options, you will find them extremely useful in your day to day work to get ahead.

Puntos a favor

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.

Puntos en contra

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.

Overall, BitBucket has served us really well as we use it daily for Git version control, Pull Requests and Code Review. It's integration with Jira makes our workflow very easy and transparent, which reduces expenses in doing discoveries.

Puntos a favor

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.

Puntos en contra

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.

Only able to work with basic version control but would like to see more improvements in the future.

Puntos a favor

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.

Puntos en contra

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.

With Bitbucket you will have your SQ repositories managed in a great cloud service which offers you the chance to easily track everything that you and your team are working on. Integration with JIRA is key feature and a decision making factor.

Puntos a favor

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.

Puntos en contra

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.