Bitbucket Reviews & Product Details

I have been using this tool for the last 1 and 1/2 years, and there are numerous things that I like very much—mainly confluence pages with pre-defined tips. We can also have the option for snippets of code change in the repository. It has the cleanest UI, which anyone efficiently manages.

I don't have anything to dislike, But I can say in the future if there is any development in the application. But one thing I need to mention is that CI/CD pipelines are not much feature-rich.

Mainly I am using it for code management between my teams. Also, It is used to slove version control hosting for our source code. It has easy integration with Slack and Jira.

There are a lot, some of the being : - Awesome integration with Jira. - User friendly pull request interface and an option to review PRs using VSCode - A very intuitive interface for creating pipelines, with very useful starter templates.

Nothing to dislike, just a feature request : - Please bring Dark Mode. - An option to allow opening JIRA cards compactly as a dialog in Bitbucket itself without redirecting.

I am using it in our organization for managing our codebase. It has improved our productivity a lot. The seamless integration it provides with JIRA makes tracking the progress of our tasks very easy.

I am using this tool from past 3 years. It works well for me. I like the UI because it is very modern, fast and responsive. It very useful tool for our team. It helps us to maintain the project version. All team members access the same code without any issue. Take pull and push the code very easily. Our team can upload multiple project on bit bucket very easily.

There is no as such issue for me and our team. sometimes conflicts occur and bit bucket lags when internet bandwidth is poor.

It is very useful tool for our team. Team member can use the same code and push his changes to the bit bucket very easily that maintain our project progress and version control. It saves lots of time for our team.

I have been using the bitbucket for the last 4 years and there are numerous things that I like about it. There is not one feature that I can name here that I don't really use in my daily life ( at my personal or professional level). Here are the few things that I can list of - Confluence pages with hundreds of pre-defined tips - git commit storage - The ability of the Jira is amazing - Branching can be improved with the help of bitbucket.

I would not call myself here and mention something I hate about bitbucket. But I can name the feature that I would see getting more attention in future if the devs think to improve. which is Confluence pages. This feature is super complex right now to understand for a beginner. This is complex, we know because it has to have all the needful info there and it's obvious the UI will get complex when you have to show all the things on the same page.

One issue with other third-party software with tags and searching for commits. In y professional life, sometimes I have to look for old commit, let's say a year old, and its hard to find them. Bitbucket has actually helped me solve that issue. It's easy to search tags, old and new commit numbers, also many other filters to search about some particular commits. This helped me to solve the branch merges issue. This was the best one which I could name of.

One of the best git repository management solution to maintain your code. It gives the feature to manage your repository centrally. It gives you the option to fork the repository which is a very good feature. Cloning and Raising the PR in the Bitbucket repository is also very simple and understanding features. We can integrate it with JIRA also for directly managing the tasks. We can implement the CI/CD which will automate your continuous integration, development, testing, and deployment. You get the cleanest UI to manage all your repositories. We also have the option to look for the snippets of the code change in the repository. The most important feature is that the bitbucket free account also provides a private repository. Bitbucket Repository can be accessed by the SSH keys and tokens so if we can always refresh it then it will also reduce the chance of the repo getting hacked as keys and tokens change after every refresh.

There is a limit on creating the private repository and the number of members with whom we can share the private repository.

1. I am using it for code management between my teams. 2. Implementing the CI/CD 3. Added security in security.md file. 4. Also added security testing for PRs.

Bitbucket is one of the best version control systems having capabilities to automate the deployment process as well. We can also integrate Bitbucket with other tools such as JIRA, Slack, etc.

The naming conventions of branch restrictions while connecting BitBucket with Jira ticket. All other features seem good for me and the project I am currently working on.

We have integrated Mulesoft with BitBucket and using it as a centralized repository. We have created CI/CD pipeline using bitbucket to automate the deployment.

Bitbucket is best choice if you want to have version control system with automation. Bitbucket has functionality of both git and Jenkins. It's UI is very easy to understand.

Well, I feel it's a best tool. Although when we integrated the branch with jira, we received the updation in jira ticket for every commit and push but not as a new comment.

We are using bitbucket as a centralized repository for version controlling also the automation features to automate deployment and testing the code. We have also integrated it with slack channel to receive our repo related updates

1: Ease in setup in any environment. 2: easy to remember commands. 3: very good version controling.

1: when header conflict will happen, it's very hard to solve them.

1: I am using version control, code management for my teammates.

It is very popular with great support. Developer-friendly tool easy integration with Atlassian Jira tool.It also has CI-CD feature for automating the development process. Also easily integrated with other build tools like TeamCity. It also provided free repositories for some limit.

Did not found any cons so far using this.

Code repositories, version controlling, managing histories, commits, raising PRS, integration with TeamCity and Jira, Code reviews.

Does the basic work delightfully. This includes basic Version control system, Pull requests, sync with target branch. The pull request section is definitely helpful as you get multiple options such as merge conflicts and the ability to ask the developer for any kind of changes which otherwise would is a very tedious task.

The main idea for dislike is the inability for the purpose of CICD pipelines as they are not feature-rich. One of the main points of disapproval will be that I cannot replicate what I think in the CICD pipelines. An example would be that the first step in the pipeline cannot be a manual step so this is a limitation for the Advocate side and which was a negative impact on my case.

The problem that we solve is the VCS system in our organization. Bitbucket maintains all our code, and Bitbucket also supports all the necessary CICD pipelines. Also, Atlassian is brilliant to include bitbucket as a discounted product if you buy Jira and Confluence. So it helps us in the cost-effective case too. Benefits will be cost effective ness, single solution for all the code, CICD needs.

It is very useful in moving the bug fixes in production as early as possible using hotfix branch. Review easily review the component changes and then approve the pool request and merge the changes either in uat or production easily.

There is nothing about this tool which I dislike. You can easily create a separate branch for your changes and then assign it to developer for making code changes using that branch.

Bit bucket really helps me in promoting the urgent changes in production the very same day the issue came after testing. Multiple reviewers validation helps in reducing the risk of moving inappropriate changes.

Provides the best cloud-based repository to manage our source code, and developers can collaboratively work on the project. It can be integrated with the Jira tool and automatically create branches. We can easily automate the build pipeline in bitbucket.

I dont see any dislikes and any issues in the bitbucket. It is the best git-based source code repository management tool available. So go for it, excellent product.

We keep our source code of all the projects in the bit bucket. Whenever a new developer comes, he clones the project and starts working on that branch. We have an automated bitbucket pipeline, so whenever a developer pushes the code, it will automatically build the code and run the test cases on it.

Easy to pull the components for promotion from personal library to user test or in production environment. Easy to merge the components. Easy to create branches to separate your component changes.

I think there is nothing which I dislike about this app. I would recommend every organization to try this software once as a versioning tool.

It is very easy to identify your component changes by viewing your branch. Anyone can make a change on same component by pulling the latest changes done. Also, there is a feature of hotfix which can be used for urgent fixes in the batch.

Code Reviews and the overview of your repositories and Pull Requests make this tool realy valuable

There could be really more features for CI/CD. The server version lacks some good features from the cloud version.

- Code Storage and repositories - Code Access Control for several teams

Great UI. And easy navigation. Also easy for new people to learn

Sometimes merging branches creat trouble

Maintaining versions or codes

Startups can opt to go with Bitbucket as most of the basic features like private repositories, pipeline minutes for free. UI is better compared to Github and Gitlab. 2 Click Revert of any merged pull request.

Merging changes take ages to complete the merging, if we refresh in between we lose the request we sent. We see downtime very frequently partially, as a few areas of the application go down, mostly merge request service. Multiple pipelines for single repo for multiple use cases may help isolate yml configuration based on use case.

I used this for the Version controlling system, a git cloud server. Bitbucket CICD pipeline for docker and Java package checks and building the Java app. Use the bitbucket to store the code configuration.

This tool helps a lot in our development tasks as a team. Some advantages which I would like to list are: 1. Version control 2. synchronization among developers when they work on different subtasks in the same project. 3. Review option for other developers during merge request. 4. version history. 5. development history in each push. 6. compatibility with many softwares.

To this date, with my experience of using bitbucket, I have not experienced anything which created an issue in my work. I have a good experience with it altogether.

Overall, Bitbucket has proved to be a very useful tool, there are some features which i have used to my benefit: 1. synchronization with fellow developers when they work on different subtasks in the same project. 2. Version control of our tasks 3. organized structure of our projects 4. peer-reviewing tasks and adding improvements using the comment feature and 'nees work' option.

Bit bucket is one of the best tools for working with the CI /CD (Continuous Integrations & Continuous Development). Bit bucket provides the enhanced version of Github. It is easy to use a bit bucket with a simple point and click the tool and Under the Bit bucket, we can assign the projects and divide them into multiple teams and handle multiple projects under the bit bucket.

It more than a year I have been using the bit bucket. But according to me, bit bucket can make some changes in the license for the students. Bit bucket can give the trial version to students so they can do the hands-on practice and It will grab their market as well.

I am a software engineer and using Bitbucket for more than a year. Working with the bit bucket is fun because we are creating the PRs, managing the work done by the team members, and also we have the benefit of the CI / CD (Continuous Integration / Continuous Development) with Rollback services. In the bit bucket, we have the backup of each and everyone changes so sometimes due to some bugs we are in locked situations, in that case, we can roll back to the old release in the production environment. Bit bucket is also a version control system that I really like.

Its ability to merge two branches. One can do it quickly via UI.

I don't dislike anything about this product. By far, I'm most comfortable with this.

- Code maintenance with multiple team members - Code can be shared easily - Code can be easily managed for releases - Git is easily used with this.

The version control and the ability to backtrack on component changes being done is truly remarkable. It's a must to have across projects across geographies in all universe!

Nothing to dislike about it ! It's a blessing to have in one's project. It makes life easy for the release managers and the developers involved. Working on the same class/component was never easier!

We are using Bitbucket for version control and deploying the code via Jenkins with the help of it. It's a great thing to have in the project! It enables flawless/seamless code movement across environments