Bitbucket Reviews: 4.4/5 — Solid Choice

For instance, one of the most remarkable qualities of BitBucket is that you can have your free private git repository for small teams, five users, whereas other repos don't offer you this option for free. Apart from that, integration with JIRA cloud is available which is a highly valuable feature.

Sometimes it can be quite hard to understand how to setup authentication with SSH keys due to the confusing way in which the settings are distributed across the UI.

I am using bitbucket as a centralized remote repository for my JAVA projects. Both, personal and work projects. I am also integrating bitbucket with JIRA Cloud.

Version Controlling. Easy to use. Easy to pull ,push and clone. Provide multiple options for cloning.

Sometimes it is not working when we change our ID password.So it becomes difficult to push new changes .

Majorly version Controlling and working with team on same project.

Bitbucket majorly comes up with the below benefits: 1) Simple user interface that lets you have ease in navigation 2) Its integration with JIRA lets you have multiple advantages like maintaining branches and committing to tickets with fewer efforts 3) Sharing and creating a repository in minimum clicks and allowing to create a branch from JIRA software too 4) Compared to other tools, it stands first in the part of security ( as it allows private repositories and its access role wise) 5) IT allows different permissions for individual users to track even the slightest modifications and look at who performed what actions. 6) It provides you notifications for every tagged activity 7) It is straightforward to manage a large team on a single project 8) CI/CD integration

1) Initially, peer-reviewing code seemed difficult as it did not allow multiple comments but now allows for the same. 2) The search feature has minor limitations as you need to mention the exact name of the component. It does provide private repo, but it has limitations till 5 for free. 3) It is a little tricky from a user interface point of view to roll back to previous versions. 4) There should be ways to identify and archieve unused repositories and branches. Currently, it is done manually 5) Lastly, the cost of it is high when compared, but it's fair enough too on the part of features and security it provides.

1 ) Introducing this system to a new user is very easy and takes less time as its UI and navigation design is simple. 2) Creating a global space for all the users in the repository and managing it access level-wise makes our effortless and saves time. 3) It provides a room where all users can work simultaneously without being dependent. 4) It has the auto-tagging feature for JIRA issues with code commits in PR, which saves tracking time. 5) Ease of use with confluence and JRa for issue tracking and documentation. 6) As multiline commenting is now enabled, it allows reviewers to add in detail views in the PR

its integrity, bitbucket is integrated with all kinds of IDEs, how it handles PRs, how it displays the commit history

sometimes it became slow, takes time to reflect the changes.

Its a platform used for version control where a group of developers decided to collaborate in a software development project and they need to manage their changes and updates so they need a platform like that.

First of all its secured with the credentials and each user is performing any action then we can come to know very easily that who had done this thing. Its organise the all files with its versions , if we update that any of the file then also its showing us that what was the last thing in the file, who had updated this file, when user has updated, is there any complexity or is there any issues with that updation or not? , And many more things like this.

Some time its taking more time to load the latest files, also sometimes its having connection issues. To use this tool somewhat knowledge/training is required. Merge functionality can be made more smooth. Some times it takes the all files in the commit instead of selected and at that time its totally very much difficult to remove extra files from the commit or committed code.

Its organise the all files with its versions , if we update that any of the file then also its showing us that what was the last thing in the file, who had updated this file, when user has updated, is there any complexity or is there any issues with that updation or not? , And many more things like this. Its keeping the versions of the file that is main benefit of it. Generally development team has many members so its easy to manage files and files related versions and who updates the files at what time, everything. Each and every team can have different folder to manage their own things in single company. There can be multiple branches and folders fo managing different orgs that is most helpful thing because we don't need to migrate the code manually. It just migrate the code very easily and quickly to make the Production org ready.

Best thing about bitbucket is its web user interface, it is very user friendly and understandable. I see multiple teams can pull code from it and can work parallelly and push that without any conflicts. One more interesting is it can be easily integrated with other attlassian products like Jira so our work can be get easier.

Some times I faced conflicts while pushing the code and took time to resolve it.

Mainly I used this to host my code and maintain it consistently . Used it to deploy my code to higher environments.Merged my code with team members code with ease.

I love that Bitbucket is easy to use, reliable, has a great user experience and it just works. I love that it's free and works well with other Atlassian products.

Compared to Github, the user experience and user interface are not as polished, and less open source projects are hosted on it, but that's not a serious deal breaker.

We use it to store all the code for the different projects in our company. We've realized simple, cheap and reliable backup for all of our projects and codebase.

We've started issuing pull requests earlier in the process, rather than waiting for a whole new, prominent feature to finish before pushing it, because the Bitbucket code review process prioritizes minor changes. Everything becomes much easier to review, faster to receive feedback, and safer to launch each change as a result.

Bitbucket Pipelines is a well-designed yet limited tool. It can be a useful tool for quickly introducing a small team to CI/CD, but if you require more complex features, you will quickly reach the platform's boundaries.

It provides a central location where you can manage git repositories, collaborates on source code, and be guided through the development process. It has a lot of cool features, such as access control, which allows you to limit who can see your source code.

Bitbucket has one of the best prices and integrates with Jira, which helps a lot in tasks and team management. It can also be integrated with Trello. The code search is very assertive as well.

I wouldn't say I liked that bitbucket has no integration with the google cloud platform as Github has. This integration helps a lot in CI/CD issues. Otherwise, you will not have PR's, for instance.

We organize our data science, data engineering and product projects over there. It helps a lot in developing new features and merge's easily. The CI/CD tool also helps a lot in deploying applications.

Easy to clone the project,initialise the project and push it in most efficient way.Its the most secured and easy way to keep your projects and share and give access the projects to the team members.

persons using other tools like github and gitlab might find this little time consuming,may be they could be newer with source tree but what i believe and have using this is really a great tool.

My almost projects are kept in bitbucket and used with source tree.Its easy to make changes in the projects give access to certain person and keep it in secure way.