Bitbucket Reviews

We use Bitbucket to store the company's proprietary code and open-source projects and share them internally. 

Bitbucket works, and it's reliable 

I have used Bitbucket for five years.

I rate Bitbucket nine out of 10 for stability. We haven't had major issues.

I rate Bitbucket 10 out of 10 for scalability. 

I called Bitbucket support once with a question. I was pleased with their response. 

I use GitHub, which is also fine. We chose Bitbucket because it was a smooth transition from on-prem to cloud. We were already using the on-prem solution, so it was smooth and easy.

One of our guys deployed it, but I think it was pretty straightforward. 

I rate Bitbucket five out of 10 for affordability. It isn't cheap, but I think it's reasonable. The free tiers don't include everything I needed. I like to keep things simple. There shouldn't be all these features that you need to pay more to get. For example, some Atlassian tools have separate licenses, but others belong to a single Atlassian account. It's a little confusing. 

I rate Bitbucket eight out of 10. 

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.

It's a source control system. We have lots of source code and we wanted to move to Git and there are a lot of different Git solutions out there, including free stuff. But we liked the features of Bitbucket, because it takes off some of the sharp edges, so to speak. It's a more professional version than the free open source Git that's widely available.

We have a couple of different tools that allow us to tie source code changes to report bugs. It's integrated with our bug tracking system and also integrated with our requirement tracking system. So we have better facilities. We could integrate these solutions using command line "hooks", but when we do it all manually, it's not likely to happen.

Even with the automation, we've had some situations where we've had mistakes. Developers have integrated code into the wrong place by mistake, so there's a fairly steep learning curve.

Being in the cloud and using large repositories can be slow. They should improve synchronizing very large repositories.

I have been using Bitbucket for six months. 

It's pretty stable. We just had one incident where one of our developers somehow got access to somebody else's code using his own credentials.  He logged in like he normally does but could not see our source code; all he could see was somebody else's source code instead. That's a security problem. They cleaned it up somehow and the next time he logged in, there was no issue.   

We don't have any issues with scalability. And no issues with availability today. It's on the cloud that you look for is, it's accessible worldwide, it's always working and you don't have to rely on your IT to keep it running.

There are around 100 users in our company. Their roles are Developers, DevOps, and QA.

We use several different source control systems and it's a big deal to change.  All the groups that were interested have now made the jump. 

I haven't contacted customer support. When we had the incident with the employee logging in with his credentials, we called support and told them this one guy had a problem. Other than that incident it's been stable and available. No real complaints.

The setup was kind of complex. We started out with some simple examples and that was easy enough. But then when we went to migrate real code repositories, we had to get into what they call large file storage, which was complex to set up.

The deployment took about a month with a small focus group and I would say it probably took two or three months to get everybody comfortable using it.

We use it on the cloud. It's the latest and greatest. You don't have to pay for maintenance and you get automatic updates and hardware and backups and all that nice stuff. I paid a little premium for it, but you get a lot of benefits.

Licensing is on a monthly basis, it's available on their website. They have a free version, a pro version and then they have an enterprise version.  The Pro version is kind of the middle of the road for about $7 per user per month.

I would advise getting some Git training.  Something like 85% of all developers use Git. So it's like the defacto standard for source control.  Bitbucket is a brand of Git that has some nice features on top of the core functionality.

The biggest lesson learned was, we should've done a little bit more training for the developers. It was very informal and should've probably been more formal, not necessarily sending everybody to university or a class, but a little more hand-holding.

I would rate it an eight out of ten. I give it this rating because there was the integration with the other tools.

We use Bitbucket for version controlling our source code, and also CI/CD was utilizing Bitbucket pipelines. We have automated build pipelines, daily master build pipelines, and daily releases.

It nicely integrates with Atlassian Jira, making it easy to find relevant branches and PRs. We also have Teams integration for Atlassian products like Confluence.

It has a nice user experience to review PRs and provides great pipeline features, integrating well with other Atlassian products.

Bitbucket pipelines could be enhanced by adding scalability and caching for images. If we could get the cloud-native benefits to Bitbucket pipeline like in Tekton, it would be great.

I have used the solution for about two years.

The solution is stable.

Our main repository gets around 200 PRs per day, and this load has limited Bitbucket pipelines due to steep limitations.

Customer service is actually done by the R&D and Deployment team. I'm not really aware of those details.

Positive

We moved from Bitbucket to Tekton because our main repository gets two hundred PRs per day, which presented a load on Bitbucket pipelines with step limitations. Moreover, we do not have local image caching, resulting in frequent pulls from Azure Container Registry, leading to Azure's rate limits.

We compared Bitbucket with Tekton, noting the benefits and limitations of each.

I'd rate the solution eight out of ten.

We use the solution in every project as a source control management software to control the versioning of the code.

The tool's UI is better. 

I would like to see the tool's desktop version. 

The solution is stable. 

I would rate the product's scalability a nine out of ten. 

I have used GitLab and GitHub before and I find the solution to be more user-friendly. 

The tool's deployment is simple and we use the cloud version. 

I would rate the solution a nine out of ten since its an awesome tool for source control and versioning. 

We use Bitbucket as our code repository and base it on our DevOps process.

This technology is quite common in our company. It is very important for our development process.

The version control feature for our code and the security aspect is valuable to us. It is also related to automation, DevOps, and our desktop environment.

There is room for improvement in the workflow. Other similar tools offer automation and more streamlined workflows, which Bitbucket currently lacks.

In additional features, I would like to see more low-code options for certain tasks. When we compare it to another solution like GitHub, in my opinion, Bitbucket could offer us more automation and actions in the future. This would be a valuable feature for improving our projects.

I have been using Bitbucket for around seven years. I use the latest version. 

It is a stable solution.

It is a scalable solution.

The customer service and support team is good. 

Bitbucket is worth the investment. Overall, I would rate the solution a nine out of ten. I recommend using the solution.

My company uses Bitbucket for version control and codes that we use for transforming data.

I haven't gone deep into all of the features of Bitbucket. I use Bitbucket as a basic repository in my company, so I don't use it to deal with the CI/CD pipeline.

I haven't encountered any issues with the solution since I am familiar with the basic Git workflows. Most of my criticisms are directed towards Git and not Bitbucket specifically, so I can say that it can be a challenge to onboard new people who need to learn how to use the commit code in Bitbucket. In general, the aforementioned flaw is not a fault related to Bitbucket but more of a problem caused by Git and the knowledge gap that new users experience. Bitbucket can be made more user-friendly for new users.

Every solution nowadays makes use of AI to make their workflows easier for its users. Bitbucket doesn't currently offer AI functionalities. Though I am unsure how AI features can be incorporated into Bitbucket, I would like to see Bitbucket with AI functionalities.

I have been using Bitbucket for a year. My company is a customer of Bitbucket.

I have not faced any stability problems with the solution.

Scalability-wise, I rate the solution a ten out of ten.

There are around ten people in my company who use Bitbucket.

Apart from Bitbucket, I have experience with GitHub. GitHub and Bitbucket are almost the same. I don't have any preference between GitHub and Bitbucket since I don't use the tools to their fullest capabilities. I use the aforementioned tools as a basic repository in my company.

The initial setup of Bitbucket is simple.

The solution is deployed on the cloud. The development part of the solution is done on an on-premises model.

I recommend the solution to those who plan to use it.

I haven't explored the entire solution yet, so it would be best for me to rate the solution a ten out of ten after I do a deep dive into the product's capabilities. I rate the overall solution an eight to nine out of ten.

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.