Bitbucket Reviews

Bitbucket is our source code repository. We use it as our source code reaction control system and for pool requests and engineer builds. It is integrated with Bamboo, which uses a CI CD pipeline to release our code to different environments.

Bitbucket has improved our organization because it has simplified and streamlined our developer communication code and review process. It is also much more visual. 

We have also integrated it with Slack. Whenever we do a full request, we get information comments in a pool request through Slack on our team channels. It's much easier to go to Bamboo and see if this code was released. This is particularly important if the code troubleshoots production-related issues. 

Bitbucket's traceability is great. Being able to see pool requests is just a great thing for collaboration.

Sometimes we struggle with searching on repositories. It is a bit challenging sometimes to pinpoint the code or repositories when just filtering by repositories. That search capability could be improved to become more intuitive. It should allow for, for example, searching for specific source files or repositories or searching the code inside the source files. That kind of flexibility would be helpful.

Of course, making the tool free would be great as well. Its cost is probably why it is not used very much in smaller companies.

I have been using Bitbucket for a year and a half.

Bitbucket is great when it comes to stability. However, we do see some challenges with Bamboo on that front. Sometimes Bamboo agents get stuck and take longer to process and build requests and releases.

I haven't experienced any issues with scalability. For five to 10 applications, it works great.

In our organization, some 200 people are using this solution. Most of them are developers. The product is being extensively used in the organization at the moment.

I have not had any contact with Bitbucket's technical support.

We are using Bamboo and Bitbucket simultaneously right now. Before Bitbucket, we were using CVS.

We made the switch over to Bitbucket as part of a company-wide migration to the cloud. CVS can only be deployed on-premise while Bitbucket is on the cloud. Also, the code review process for request concepts and the team collaboration Bitbucket facilitates makes it much more friendly and modern.

I was not part of the initial implementation team. We have a DevOps team in our company, so they set it up and once it was ready, it was rolled out to the development teams with a ready-to-use config. What we did, as far as deployment goes, is move our code from a legacy version control system to a new version control system. That experience was straightforward for me as a developer.

The initial setup was relatively fast. It took us about three days to migrate a small-to-medium-sized application from the legacy version control system to Bitbucket, for example.

Unfortunately, I'm not privy to this information. 

Bitbucket is definitely a tool to consider if somebody is still on CVS. It is a great tool and well integrated with Bamboo. Both Bitbucket and Bamboo are made by the same company, and the latter is there to connect the dots between the code and releases in production.

We have a Bitbucket server internally, that we manage with our own IT team. We use the solution as a software control repository.

Bitbucket could improve search and indexing capabilities. There is only basic searching available. There is only the ability to index the main branch but not the subbranches. The search capabilities are dodgy.

In a future release, the way they manage the permission of the records in the solution could be better. They fit well if you're only running one or two projects. If you have a lot of projects and records, the current permission model is not flexible. You have a challenge if you want to provide permissions across all the projects to be the same. Additionally, if you want to have specific permission there are limitations. There requires a lot of redundant work to accomplish what we want.

I have been using Bitbucket for approximately six years.

Bitbucket has some initial stability issues because of our large team using the solution. However, this was later resolved.

I rate the stability of Bitbucket an eight out of ten.

We have approximately 300 to 400 users using this solution. Our whole organization uses it.

I rate the scalability of Bitbucket an eight out of ten.

I have not used the support from Bitbucket. However, my team has used the support. The support has been fine, they have not had any downtime.

I have used GitHub and it has more features than Bitbucket. Additionally, I have used GitLab.

GitHub is a more mature solution compared to Bitbucket. The search capability has improved in GitHub since they are integrated with Opensoft. You can create your workflow and actions and it becomes easier to do things. GitHub can help a lot. The only season why our organization didn't adopt it is because of the high pricing.

The initial setup of Bitbucket is straightforward. 

The initial setup was in-house. However, it is possible they had some assistance.

Bitbucket is a cost-effective solution. It is the cheapest in the market. It is lower than GitLab and GitHub.

For general company usage, Bitbucket should fit the purpose. If you have a larger team you better look for other options. For a more complete solution for your CICD, I would recommend GitHub.

I rate Bitbucket a seven out of ten.

We are using Bitbucket for the code checking and tracking of our project depositories which we have locally. This includes code changes in software development. 

Bitbucket has helped our company stay current with our updated code daily.

The solution is easy to use. If I need to check out my latest code or I need to send my local code to the depositories it is simple. Overall it is has been a good experience from my side using this solution.

One of the areas the solution could improve on is when there is a merging conflict it is quite confusing. When I am having a merging conflict I get stuck on the page, then I need to search how to handle the particular problem. For example, finding what the commands are which can be used. 

I might not have the proper knowledge of it. However, the merging processes can be difficult and could be made easier. Overall there should be better documentation available. When I first started out it would have been very helpful because I had to search to find out how to use the solution.

In an upcoming release, the solution could improve the collaboration. Additionally, there should be some startup tool or features for whenever we have local changes or updates it will prevent us from submitting any change unless they have been removed locally. For example, 
there should be some sort of command tool that can remove my local code first and then checking it by taking code from the latest one to resolve it.

I have been using Bitbucket within the last 12 months.

The stability of the solution is good. However, there have been times I had to close the program down and restart it.

The solution is scalable and it is not very difficult to do.

We have approximately 10 people using this solution in my organization which includes various teams, such as the automation department.

We use this solution every day and frequently, we plan to continue using it in the future.

I have used a previous version that was not user-friendly. Additionally, I have used GitHub.

We have one technician that does the maintenance of the solution.

I rate Bitbucket a seven out of ten.

Our primary use case is version control, integration with Jenkins for build management, and integration to Jira so that there is traceability to any issues from the build. We also work with code review and pull requests.

The most valuable feature is the bundle itself because we use them all. However, code reviews and the ability to support DevSecOps are very important.

The mandatory move to the cloud model is the biggest complaint. There are some minor things like customization, configuration, pricing, and limitations in general. I think the configuration can be improved because it is getting more complicated and not very well organized.

I have been working with Bitbucket ever since it was released ten years ago.

Bitbucket is definitely stable.

We were using GitHub before switching to Bitbucket. We do not trust corporations, because we do not want to make our private code available to these corporations. We do not want to just put it on a public site and therefore we switched to Bitbucket.

In the initial setup, you definitely need to be a developer or system administrator. I do not think it is for the faint of heart. You have to set up the reverse proxy and the DNS, so it is accessible from the outside world and make sure all the JVM settings are correct. 

We stay within the ten-user limit and it is affordable and we pay around one hundred dollars. However when you increase from ten people to anything higher the price increase to one thousand five hundred. That is unsatisfactory and they should have a gradual price slope.

I would rate Bitbucket a nine out of ten.

We use Bitbucket as a repository for our sensitive data, like source code and any other sensitive information that requires change and version tracking. We have eight to 10 users currently accessing Bitbucket.

Bitbucket is a standard source code repository with all the features you would expect. It supports Git and SVN. It's an extensive tool that provides us with merging, branching, and change management capabilities. You can compare the changes with the current and previous versions.

We have been using Bitbucket for four or five years.

Bitbucket is highly stable.

You can scale Bitbucket vertically or horizontally.

I rate Bitbucket support eight out of 10.

Positive

We used Team Foundation Server and Microsoft SourceSafe.

Bitbucket's Initial setup is a little complicated because you need to install  and configure the solution. It can take one or two days to deploy Bitbucket. If you have a high workload, you can deploy it on multiple server farms as needed.

The vendor is maintaining Bitbucket. We have one staff member responsible for the configuration, but we consult the vendor for patching and upgrades.

I rate BitBucket eight out of 10. Bitbucket is an excellent product. Atlassian will move to the cloud, so the on-prem version may be phased out. You have to be careful when choosing this product. There will be a cloud version available, so it's better if you go with the cloud version of Bitbucket.

Bitbucket can be deployed on the cloud or on-premise.

We use Bitbucket to set up an end-to-end integration system.

We use Bitbucket for Jira, Confluence, and Jenkins and we have an automation pipeline. Whenever the coaching is done in Bitbucket we run an automation pipeline from the build, create installations, and tests all in one pipeline. It is done automatically. 

Bitbucket could improve its security. For example, the user access security could improve.

I have been using Bitbucket for approximately six years.

Bitbucket is stable. However, every one or two months it crashes, it depends on the usage. When Jira is down after a long weekend Bitbucket might not be working. There could be other reasons it is not working and not necessarily the solution's fault.

The scalability of Bitbucket is good.

We have a lot of developers working and we are moving the solution locally to the cloud next year. We plan to increase the usage of the solution.

I rate the support from Bitbucket a four out of five.

Positive

I have used CVS previously.

The initial setup of Bitbucket can be complex. It depends on what you are using it for. For example, when I was using Jenkins I had to set up a lot of scripts to link all the tasks together for it to run automatically.

I would recommend this solution to others.

I rate Bitbucket an eight out of ten.

We're using Bitbucket for version control and deployment.

What I like best about Bitbucket is that you can use it for deployment, primarily if your IP addresses do not work well with your deployment scripts. You can use the tool to whitelist IP addresses during deployment.

Currently, what's lacking in Bitbucket is the assignment feature or the feature of giving permissions to other users.

I've been working with Bitbucket since 2014.

The scalability of Bitbucket is ten out of ten. Bitbucket has documentation on how to scale, and you can also communicate with the Bitbucket team for any scalability-related questions.

I have yet to contact the technical support team for Bitbucket.

Currently, we are moving from Bitbucket to GitLab for convenience, but at the moment, we're still using both solutions.

Setting up Bitbucket is simple because you can log in with your email account.

My team uses scripts developed on Ruby to do Bitbucket deployments.

Bitbucket is a low-priced tool.

My company evaluated GitLab.

I'm working as a software engineer.

My company has four Bitbucket users.

My rating for Bitbucket is nine out of ten.

I recommend the tool to others. One company even consulted with me, and I told that company to focus on Bitbucket.

My company is a Bitbucket user. There's no partnership currently.

I'm mainly using Bitbucket as a code repository for storing the configurations and templates of my monitoring tools. We have them stored locally, and Bitbucket manages changes and builds, so we have a means of rolling back if there are any issues. 

There are about 10 to 15 users in the company at the moment. They want to expand usage, but there's still little uptake. It's an old-fashioned, traditional IT  place that they work in.

Bitbucket works fine for what I'm doing. It's slightly different from GitHub, but it's a good tool for storing code. 

Bitbucket's usability and integration with other tools could be improved somewhat. My other issue is that Bitbucket, GitHub, GitLab, and all the other ones use slightly different jargon for the same things. They should come up with a standard language for all these tools.

I have been using Bitbucket off and on for about five or six years.

BitBucket is stable. 

BitBucket seems scalable, but we haven't used it at scale, so I wouldn't know. 

Setting up BitBucket is fairly straightforward. It has its own APIs, and it's easy to access. Everything is in the cloud. 

I believe it's a monthly license subscription, but you get a discount for paying by the year, so I'd recommend that.

I rate BitBucket seven out of 10. If you're considering BitBucket, do your research and make sure it's the product for you. There are several options out there.